Dev.to (Forem) MCP Server for VS Code CopilotGive VS Code Copilot instant access to 12 tools to Create Article, Get Article By Id, Get Article By Path, and more

Name: Dev.to (Forem)
Price: 29 USD
Availability: InStock
Rating: 5.0 (1 reviews)
Author: Vinkius

GDPR Free for Subscribers

GitHub Copilot in VS Code is the most widely adopted AI coding assistant, embedded directly into the world's most popular code editor. With MCP support in Agent mode, Copilot can access external data and APIs to generate context-aware code grounded in real-time information.

Ask AI about this MCP Server for VS Code Copilot

Open in ChatGPT Open in Claude Open in Perplexity

The Dev.to (Forem) MCP Server for VS Code Copilot is a standout in the Developer Tools category — giving your AI agent 12 tools to work with, ready to go from day one.

Built for AI Agents by Vinkius

Vinkius delivers Streamable HTTP and SSE to any MCP client

Claude

ChatGPT

Cursor

Gemini

Windsurf

VS Code

JetBrains

Vercel

+ other MCP clients

Classic Setup·json

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

RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install Dev.to (Forem) and 4,000+ MCP Servers from a single visual interface.

Download Free Open SourceNo signup required

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* 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

About 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.

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.

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_articles and get_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).

The Dev.to (Forem) MCP Server exposes 12 tools through the Vinkius. Connect it to VS Code Copilot in under two minutes — credentials fully managed, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

All 12 Dev.to (Forem) tools available for VS Code Copilot

When VS Code Copilot connects to Dev.to (Forem) through Vinkius, your AI agent gets direct access to every tool listed below — spanning blogging, forem, dev-to, and more. Every call runs in a secure, isolated environment with full audit visibility. Beyond a simple connection, you get real-time monitoring of agent activity, enterprise governance, and optimized token usage.

create

Create article on Dev.to (Forem)

to/Forem. Requires API key. Create a new article

get

Get article by id on Dev.to (Forem)

Get a single article by ID

get

Get article by path on Dev.to (Forem)

Get a single article by username and slug

get

Get me on Dev.to (Forem)

Get authenticated user details

get

Get user on Dev.to (Forem)

Get a user by ID or username

list

List articles on Dev.to (Forem)

List published articles

list

List my articles on Dev.to (Forem)

Requires API key. List authenticated user's articles

list

List org articles on Dev.to (Forem)

List organization's articles

list

List org users on Dev.to (Forem)

List organization's users

list

List videos on Dev.to (Forem)

List articles with videos

unpublish

Unpublish article on Dev.to (Forem)

Unpublishes a specific article. Unpublish an article

update

Update article on Dev.to (Forem)

Requires API key. Update an existing article

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

Follow these steps to wire Dev.to (Forem) into VS Code Copilot. The entire setup takes under two minutes — your credentials stay safe behind Vinkius.

Create MCP config

Create a .vscode/mcp.json file in your project root

Add the server config

Paste the JSON configuration above

Enable Agent mode

Open GitHub Copilot Chat and switch to Agent mode using the dropdown

Start using Dev.to (Forem)

Ask Copilot: "Using Dev.to (Forem), help me...". 12 tools available

Why Use VS Code Copilot with the Dev.to (Forem) MCP Server

GitHub Copilot for Visual Studio Code provides unique advantages when paired with Dev.to (Forem) through the Model Context Protocol.

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) + VS Code Copilot Use Cases

Practical scenarios where VS Code Copilot combined with the Dev.to (Forem) MCP Server delivers measurable value.

Live API integration: Copilot can query an MCP server, inspect the response schema, and generate typed API client code in the same step

DevSecOps workflows: security teams can give developers access to domain intelligence tools directly in their editor for real-time vulnerability assessment during code review

Data pipeline development: Copilot fetches sample data via MCP and generates transformation scripts, validators, and test fixtures from actual API responses

Documentation generation: Copilot queries available tools and auto-generates README sections, API reference docs, and usage examples

Example Prompts for Dev.to (Forem) in VS Code Copilot

Ready-to-use prompts you can give your VS Code Copilot agent to start working with Dev.to (Forem) immediately.

"List the top 5 articles about 'javascript' on Dev.to."

"Create a new draft article titled 'My MCP Guide' with the content 'This is a test'."

"Show me my account details and API status."

Troubleshooting Dev.to (Forem) MCP Server with VS Code Copilot

Common issues when connecting Dev.to (Forem) to VS Code Copilot through Vinkius, and how to resolve them.

MCP tools not available

Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.

Dev.to (Forem) + VS Code Copilot FAQ

Common questions about integrating Dev.to (Forem) MCP Server with VS Code Copilot.

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.