How to Use the Dev.to (Forem) MCP in VS Code Copilot

Q: How do we set up the Dev.to (Forem) MCP Server for our team in VS Code Copilot?

Create a .vscode/mcp.json file in your repository root and add the server configuration. Once pushed, anyone on your team with VS Code 1.96+ can use the tools.

Q: Does VS Code Copilot update our company's Dev.to (Forem) posts?

Yes, updatearticle allows the agent to push changes from your local git branch directly to Forem. This keeps your published docs in sync with your codebase.

Q: How do we check who authored a post using VS Code Copilot?

Run getuser with the author's username inside the chat window. The agent will fetch their profile details and display them directly in your editor.

Manage team-wide Dev.to documentation and Forem posts directly from VS Code Copilot.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Dev.to (Forem) MCP to VS Code Copilot

Create your Vinkius account to connect Dev.to (Forem) to VS Code Copilot and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup Dev.to (Forem) with VS Code Copilot

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Share Forem tools across teams using this MCP Server

`list_org_articles` pulls your team's shared Forem publication history directly into VS Code Copilot. Committing the Forem MCP Server configuration to your repository allows every team member to use the same Dev.to tools in VS Code. It ensures uniform Forem formatting and publishing standards across the organization.

Track dev advocacy metrics from VS Code Copilot

`list_org_users` pulls your organization's author list directly into your VS Code Copilot workspace. Combining this with `list_videos` lets your VS Code Copilot team audit which Forem tutorials have video content. It makes Dev.to content planning much easier during sprint reviews.

Securely draft new articles from your codebase

`create_article` lets you convert technical documentation in your repository into draft Forem posts using VS Code Copilot. Because VS Code Copilot works within your secure workspace, your Forem drafts remain private until you decide to publish. This prevents accidental leaks of unreleased features on Dev.to.

Setup guide

Set up Dev.to (Forem) MCP in VS Code Copilot

Prerequisites

VS Code 1.99 or later with GitHub Copilot extension
Active Vinkius subscription with a valid endpoint token

1

Open MCP configuration

Open the Command Palette (Cmd+Shift+P / Ctrl+Shift+P) and run "MCP: Add Server". Select HTTP (Streamable) as the server type. VS Code will create .vscode/mcp.json in your workspace.
2

Add the Dev.to (Forem) MCP

Paste the JSON snippet shown on the right into your .vscode/mcp.json. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com.
3

Switch to Agent mode

Open Copilot Chat (Cmd+Shift+I / Ctrl+Shift+I) and switch to Agent mode using the dropdown. MCP tools are only available in Agent mode — they do not appear in Edit or Ask modes.
4

Verify the connection

In the Copilot Chat input, type # to list available tools. You should see the Dev.to (Forem) tools listed. Try asking: "List my recent Dev.to (Forem) transactions" and Copilot will invoke them automatically.

.vscode/mcp.json

{
  "mcpServers": {
    "devto-forem-mcp": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Get your connection token →

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.

Connect Dev.to (Forem) now

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 VS Code Copilot

Create a `.vscode/mcp.json` file in your repository root and add the server configuration. Once pushed, anyone on your team with VS Code 1.96+ can use the tools.

Yes, `update_article` allows the agent to push changes from your local git branch directly to Forem. This keeps your published docs in sync with your codebase.

Yes, the server runs within the secure Vinkius sandbox or your local machine. It adheres to your organization's outbound network rules and handles authentication via secure environment variables.

Run `get_user` with the author's username inside the chat window. The agent will fetch their profile details and display them directly in your editor.

The integration only accesses organization articles and user directories when explicitly requested. Your Forem API tokens are never saved in the repository or exposed to public logs.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript