Turn release notes into launch posts and schedule them through Postly.
Try: “Use this changelog to create release posts and schedule them for our connected channels.”
Windsurf + Postly
Manage social media with Windsurf.
Bring Postly AI Agents into Windsurf so technical teams, growth engineers, and automation builders can connect social publishing, analytics, media uploads, and validation to agentic development workflows.
Custom MCP configuration. Requires Postly API access and an eligible client account.
Setup reviewed October 25, 2026 · Postly Team
Connect Windsurf to Postly
- Connect publishing channels in Postly and select the workspace for your assistant. Check API access in your plan.
- Add Postly in your editor’s MCP settings. Follow the provider instructions for your installed editor and agent version.
- Use
https://mcp.postly.ai/windsurf. When OAuth is offered, enter your key only on the Postly authorization page. For API-key clients, useAuthorization: Bearer <your-api-key>in connection settings. - Start a fresh session, enable Postly tools, and verify your workspace and channels with the read-only task below.
Confirm your first successful connection
List my Postly workspaces and connected publishing channels. Show the workspace and destination names. Do not create, schedule, or publish anything.
Match the result to your intended brand. Check API activity for a successful request, then try a publishing workflow.
Copy a launch, weekly-plan, or content-reuse brief →
Publishing workflows for Windsurf
Windsurf is built around Cascade and tool-using workflows. Postly extends that environment with marketing execution so product launches, docs updates, changelog posts, and campaign reports can move from code context into publishing.
Generate developer-focused LinkedIn, X, and newsletter content from code or docs context.
Try: “Summarize our publishing activity for the launch week and highlight missed channels.”
Ask Cascade to inspect publishing activity and summarize what shipped.
Try: “Create a reusable workflow for promoting docs updates across social and newsletter.”
Before a write action, confirm content, media, workspace, destinations, date, time, and timezone. Use team approvals where required. Keep the returned post ID and inspect its destination status; accepted or scheduled does not mean published.
Scheduled agent runs depend on your assistant’s orchestration. For recurring source-based publishing, use Auto Post. Your editor and calendar remain available throughout.
Connection and publishing help
No Postly tools appear
Check the endpoint and connection method, enable the tools, and start a fresh session. Client plans and administrator settings can affect custom MCP access.
The workspace or channel is missing
Check the allowed workspace named in the error. Use its workspace ID, switch to the correct API key, or edit Workspace access in API keys. Reconnect a channel if its provider authorization expired.
An accepted request has not published
Retrieve the Postly post ID and inspect the schedule, approval state, and destination results. Resolve the specific validation or provider error before retrying.
How do I stop the connection?
Disable the client connection and revoke its API key in Postly. Review scheduled posts separately; revoking a key does not cancel already accepted publishing work.