How to Use the Dev.to (Forem) MCP in Windsurf
Chain Dev.to publishing tasks autonomously with Windsurf and Cascade.
Works with every AI agent you already use
…and any MCP-compatible client
Connect Dev.to (Forem) MCP to Windsurf
Create your Vinkius account to connect Dev.to (Forem) to Windsurf and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.
Automate drafts directly inside Windsurf
Cascade can plan and execute your entire publication pipeline without you needing to prompt every single step. It reads your local markdown files, drafts the post using `create_article`, and checks the output immediately. If there is an issue with the layout, your agent runs `update_article` to fix typos or tags. You just give it the goal, and it handles the back-and-forth API calls.
Audit Dev.to metrics via this MCP Server
Run a quick audit on your published work by letting your agent pull your profile data. It uses `get_me` to verify your account status and then runs `list_my_articles` to pull down your recent posts. Because Windsurf chains tools, Cascade can take that list, identify low-performing posts, and pull their full details with `get_article_by_id` to suggest edits in your editor.
Manage team content inside your IDE
Keep track of what your organization is publishing without leaving your workspace. The agent calls `list_org_articles` to pull the latest team posts and matches them against your local project roadmap. If you need to check who wrote what, the agent queries `list_org_users` to map Dev.to accounts to your internal team directory.
Set up Dev.to (Forem) MCP in Windsurf
Prerequisites
- Windsurf IDE installed (macOS, Windows, or Linux)
- Active Vinkius subscription with a valid endpoint token
- 1
Open MCP configuration
Click the Cascade assistant icon in the sidebar, then click the hammer icon (🔨) at the top of the panel. Select "Configure" to open
~/.codeium/windsurf/mcp_config.json. - 2
Add the Dev.to (Forem) MCP
Paste the JSON snippet shown on the right into the
mcpServersobject. Replace[YOUR_TOKEN_HERE]with your endpoint token from cloud.vinkius.com. - 3
Refresh MCPs
Go back to the hammer icon (🔨) in Cascade and click "Refresh". Windsurf will detect the new server. No full restart is needed — the connection is hot-reloaded.
- 4
Verify in Cascade
Start a new Cascade conversation and ask something like "Show my Dev.to (Forem) payment history." If connected, Cascade will call the Dev.to (Forem) tools directly. You will see a green dot next to the server name in the MCP panel.
{
"mcpServers": {
"devto-forem-mcp": {
"url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
}
}
} Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Dev.to (Forem). All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
Why Choose Vinkius
Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.
Real-time monitoring
Live
visibility into every interaction
Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.
Built-in savings
60%
lower AI costs
Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.
Single dashboard
One
place for every integration
Every tool your AI connects to, managed from a single screen. One account, complete control.
Common questions about Dev.to (Forem) MCP in Windsurf
Use it with your favorite AI tools
Connect this server to Cursor, Claude, VS Code, and more.
Start using the Dev.to (Forem) MCP today
We host it, we monitor it, we maintain it. You just paste one token.