Dev.to

This MCP server lets you interact with dev.to public data through a remote Model Context Protocol interface, enabling you to fetch articles, users, tags, and comments without handling authentication directly. It exposes a stable HTTP endpoint you can connect to from any MCP-compatible client, making it easy to build tools, dashboards, or automations on top of dev.to data.

How to use

Connect to the MCP server from your MCP client using the provided HTTP URL or run the local server on your machine. You can retrieve articles, a specific article, user data, popular tags, article comments, and perform searches through the exposed endpoints. For typical usage, point your client to the server URL and invoke the available endpoints by name, supplying the required filters or identifiers as described in each endpoint.

How to install

Prerequisites you need on your machine: Node.js and npm are recommended for local setup. Ensure you have a supported runtime and network access to reach the server once it starts.

Install dependencies and build the project when you have access to the source. Use the following commands in sequence to prepare and start the MCP server locally.

npm install
npm run build

Run locally

Start the MCP server so it listens on the default port 3000, or specify a custom port using the PORT environment variable.

npm start

Run with Docker

You can run a pre-built image to quickly deploy the MCP server. The container exposes the MCP endpoint at /mcp and uses port 3000 by default.

docker pull docker.io/nickytonline/dev-to-mcp:latest

# Run the container
docker run -d \
  --name dev-to-mcp \
  -e NODE_ENV=production \
  -e PORT=3000 \
  -p 3000:3000 \
  --restart unless-stopped \
  docker.io/nickytonline/dev-to-mcp:latest

Configuration and health

The server exposes an MCP endpoint at http://localhost:3000/mcp by default. If you run in a container, ensure the host port 3000 is mapped to the container port 3000. You can set PORT to a different value if needed.

Endpoints and capabilities

All endpoints align with the dev.to public data scope and do not require authentication. Available capabilities include retrieving articles, specific articles, user data, popular tags, article comments, and article search.

Available tools

get_articles

Retrieve articles with optional filters such as username, tag, state, and pagination to browse dev.to content.

get_article

Fetch a specific article by its ID or path for quick viewing or processing.

get_user

Obtain user information by ID or username to profile or analyze a creator.

get_tags

List popular tags from dev.to to discover trending topics.

get_comments

Get discussion comments for a particular article to analyze engagement.

search_articles

Search across articles using a query and optional fields to refine results.