dev-to

This MCP server provides a remote interface to the public dev.to API, exposing a set of endpoints that do not require authentication. Clients can connect via MCP to fetch articles, specific articles, user information, popular tags, and comments, or to perform article searches. The server runs as an HTTP service on a configurable port (default 3000) and can be integrated with any MCP-compatible client to build tooling, dashboards, or automation workflows that consume dev.to data without handling API keys.

To use the server, start it in your environment. Once running, connect to the MCP endpoint over HTTP (for example, http://localhost:3000/mcp). The available MCP endpoints are: get_articles for filtered article lists, get_article for a single article, get_user for user data, get_tags for popular tags, get_comments for article comments, and search_articles for query-based searches. Each endpoint accepts query parameters described in the README, such as username, tag, id, path, page, per_page, and so forth. The server forwards requests to dev.to’s public API and returns the results to the MCP client.

Prerequisites:

• Node.js and npm installed on your system
• Access to the project repository (clone or download the source)

Installation steps:

1. Install dependencies npm install

2. Build the project (if a build step exists in this project) npm run build

3. Run the MCP server npm start

4. Verify the server is running (default port 3000 or as configured via PORT) curl -fsS http://localhost:3000/mcp

Notes:

• If you deploy with Docker, you can configure PORT via environment variables and expose 3000 or the chosen port.
• The server will listen on the PORT environment variable, defaulting to 3000 if not set.

Tips and common considerations:

• Environment variables: PORT controls the listening port; NODE_ENV can be set to production or development for different logging and behavior.
• Health check: Use a simple HTTP GET to /mcp to verify the service is responding.
• Endpoints mirror dev.to public API capabilities: get_articles (with username, tag, state, pagination), get_article (id or path), get_user (id or username), get_tags (page, per_page), get_comments (article_id), and search_articles (q, page, per_page, search_fields).
• Network: If running behind a reverse proxy or firewall, ensure the chosen port is exposed and allowed.
• If building from source, ensure the build artifacts (e.g., dist/index.js) exist and the node command path matches your deployment layout.