Bring Blogging
to Cursor
Learn how to connect Dev.to (Forem) to Cursor and start using 12 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
GDPR Free for SubscribersCompatible with every major AI agent and IDE
Gemini
What is the Dev.to (Forem) MCP Server?
Connect your Dev.to or Forem account to any AI agent and manage your technical writing and community presence through natural conversation.
What you can do
- Article Management — List published articles, search by tags, and fetch specific posts by ID or path.
- Content Creation — Create new articles or update existing ones with full markdown support directly from your chat.
- Personal Dashboard — Access your own articles (published or drafts) and retrieve your authenticated user profile using
list_my_articlesandget_me. - Community Insights — Look up other users with
get_user, explore organization-specific content, and list organization members. - Moderation Tools — Unpublish articles when necessary using
unpublish_article(requires appropriate permissions).
How it works
- Subscribe to this server
- Enter your Dev.to/Forem API Key
- Start managing your blog posts and community interactions from Claude, Cursor, or any MCP client
Who is this for?
- Technical Writers — draft and update articles without leaving your markdown editor or IDE.
- Community Managers — monitor organization posts and user profiles efficiently.
- Developers — automate the distribution of technical content and query community data via API.
Built-in capabilities (12)
to/Forem. Requires API key. Create a new article
Get a single article by ID
Get a single article by username and slug
Get authenticated user details
Get a user by ID or username
List published articles
Requires API key. List authenticated user's articles
List organization's articles
List organization's users
List articles with videos
Unpublishes a specific article. Unpublish an article
Requires API key. Update an existing article
Why Cursor?
Cursor's Agent mode turns Dev.to (Forem) into an in-editor superpower. Ask Cursor to generate code using live data from Dev.to (Forem) and it fetches, processes, and writes. all in a single agentic loop. 12 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.
- —
Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context
- —
Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards
- —
MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment
- —
VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools
Dev.to (Forem) in Cursor
Dev.to (Forem) and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Dev.to (Forem) to Cursor through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 4,000+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Dev.to (Forem) in Cursor
The Dev.to (Forem) MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 12 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in Cursor only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.
* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
Dev.to (Forem) for Cursor
Every tool call from Cursor to the Dev.to (Forem) MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I publish a new post directly from the chat?
Yes! Use the create_article tool by providing a title and the markdown content. You can also set the published status to true or false for drafts.
How do I see my own drafts and published posts?
You can use the list_my_articles tool. It allows you to filter by type, such as 'all', 'published', or 'unpublished' (drafts).
Can I look up another user's profile information?
Yes, use the get_user tool with either their unique User ID or their username to retrieve their public profile details.
What is Agent mode and why does it matter for MCP?
Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.
Where does Cursor store MCP configuration?
Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.
Can Cursor use MCP tools in inline edits?
No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.
How do I verify MCP tools are loaded?
Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.
Tools not appearing in Cursor
Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.
Server shows as disconnected
Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.
Explore More MCP Servers
View all →
Chili Piper
10 toolsAutomate demand conversion via Chili Piper — manage concierge routes, distribution queues, and generate instant booking links directly from any AI agent.
Silhouette Score Engine
1 toolsEvaluate the quality and cohesion of clustering algorithms (like K-Means) with mathematically perfect Silhouette scores computed local.
Fireblocks
40 toolsSecurely manage digital assets, vault accounts, and blockchain transactions via the Fireblocks Digital Asset Platform directly from your AI agent.
Tomorrow.io Alternative
10 toolsAccess hyperlocal weather intelligence — real-time conditions, forecasts, historical archives, severe alerts and route weather from the Tomorrow.io API.