4,000+ servers built on vurb.ts
Vinkius

Dev.to (Forem) MCP Server for ClineGive Cline instant access to 12 tools to Create Article, Get Article By Id, Get Article By Path, and more

MCP Inspector GDPR Free for Subscribers

Cline is an autonomous AI coding agent inside VS Code that plans, executes, and iterates on tasks. Wire Dev.to (Forem) through Vinkius and Cline gains direct access to every tool. from data retrieval to workflow automation. without leaving the terminal.

Ask AI about this MCP Server for Cline

The Dev.to (Forem) MCP Server for Cline 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

ClaudeClaude
ChatGPTChatGPT
CursorCursor
GeminiGemini
WindsurfWindsurf
VS CodeVS Code
JetBrainsJetBrains
VercelVercel
+ 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.

Vinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop Interface
Download Free Open SourceNo signup required
Dev.to (Forem)
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.

Cline operates autonomously inside VS Code. it reads your codebase, plans a strategy, and executes multi-step tasks including Dev.to (Forem) tool calls without waiting for prompts between steps. Connect 12 tools through Vinkius and Cline can fetch data, generate code, and commit changes in a single autonomous run.

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 Cline 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 Cline

When Cline 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 Cline via MCP

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

01

Open Cline MCP Settings

Click the MCP Servers icon in the Cline sidebar panel
02

Add remote server

Click "Add MCP Server" and paste the configuration above
03

Enable the server

Toggle the server switch to ON
04

Start using Dev.to (Forem)

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

Why Use Cline with the Dev.to (Forem) MCP Server

Cline provides unique advantages when paired with Dev.to (Forem) through the Model Context Protocol.

01

Cline operates autonomously. it reads your codebase, plans a strategy, and executes multi-step tasks including MCP tool calls without step-by-step prompts

02

Runs inside VS Code, so you get MCP tool access alongside your existing extensions, terminal, and version control in a single window

03

Cline can create, edit, and delete files based on MCP tool responses, enabling end-to-end automation from data retrieval to code generation

04

Transparent execution: every tool call and file change is shown in Cline's activity log for full visibility and approval before committing

Dev.to (Forem) + Cline Use Cases

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

01

Autonomous feature building: tell Cline to fetch data from Dev.to (Forem) and scaffold a complete module with types, handlers, and tests

02

Codebase refactoring: use Dev.to (Forem) tools to validate live data while Cline restructures your code to match updated schemas

03

Automated testing: Cline fetches real responses from Dev.to (Forem) and generates snapshot tests or mocks based on actual payloads

04

Incident response: query Dev.to (Forem) for real-time status and let Cline generate hotfix patches based on the findings

Example Prompts for Dev.to (Forem) in Cline

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

01

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

02

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

03

"Show me my account details and API status."

Troubleshooting Dev.to (Forem) MCP Server with Cline

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

01

Server shows error in sidebar

Click the server name to see logs. Verify the URL and token are correct.

Dev.to (Forem) + Cline FAQ

Common questions about integrating Dev.to (Forem) MCP Server with Cline.

01

How does Cline connect to MCP servers?

Cline reads MCP server configurations from its settings panel in VS Code. Add the server URL and Cline discovers all available tools on initialization.
02

Can Cline run MCP tools without approval?

By default, Cline asks for confirmation before executing tool calls. You can configure auto-approval rules for trusted servers in the settings.
03

Does Cline support multiple MCP servers at once?

Yes. Configure as many servers as needed. Cline can use tools from different servers within the same autonomous task execution.

Explore More MCP Servers

View all →