Bring Blogging
to VS Code Copilot
Learn how to connect Dev.to (Forem) to VS Code Copilot 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 VS Code Copilot?
GitHub Copilot Agent mode brings Dev.to (Forem) data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 12 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.
- —
VS Code is used by over 70% of developers. adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor
- —
Project-scoped MCP configs (
.vscode/mcp.json) let you commit server configurations to your repository, ensuring the entire team shares the same tool access - —
Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop
- —
GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services
Dev.to (Forem) in VS Code Copilot
Dev.to (Forem) and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Dev.to (Forem) to VS Code Copilot 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 VS Code Copilot
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 VS Code Copilot 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 VS Code Copilot
Every tool call from VS Code Copilot 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.
Which VS Code version supports MCP?
MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.
How do I switch to Agent mode?
Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.
Can I restrict which MCP tools Copilot can access?
Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.
Does MCP work in VS Code Remote or Codespaces?
Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.
MCP tools not available
Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.
Explore More MCP Servers
View all →
Cypress Cloud
10 toolsAudit E2E testing via Cypress — monitor test runs, inspect spec instances, track flaky tests, and generate enterprise reports directly from any AI agent.
CallFire
10 toolsRun voice broadcasts, send bulk text messages, and manage call tracking campaigns for high-volume outreach at scale.
Upstash
23 toolsManage serverless Redis via Upstash REST API — execute commands, manage data structures and monitor your database from any AI agent.
Azure Functions Invoke
1 toolsThis MCP does exactly one thing: it invokes a single Azure Function. That's its only function, and nothing else. Incredible for letting your AI execute secure serverless compute.