Skip to main content
Glama
Arindam200

Dev.to MCP Server

by Arindam200
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Server capabilities have not been inspected yet.

Tools

Functions exposed to the LLM to take actions

NameDescription
get_latest_articlesB

Get the latest articles from Dev.to

get_top_articlesB

Get the top articles from Dev.to

get_articles_by_tagC

Get articles by tag from Dev.to

get_article_by_idC

Get a specific article by ID from Dev.to

search_articlesB
Search for articles on Dev.to

Args:
    query: Search term to find articles
    page: Page number for pagination (default: 1)
get_article_detailsC
Get detailed information about a specific article

Args:
    article_id: The ID of the article to retrieve
get_articles_by_usernameC
Get articles written by a specific user

Args:
    username: The username of the author
get_user_infoC
Get information about a Dev.to user

Args:
    username: The username of the user
create_articleB
Create and publish a new article on Dev.to

Args:
    title: The title of the article
    body_markdown: The content of the article in markdown format
    tags: Comma-separated list of tags (e.g., "python,tutorial,webdev")
    published: Whether to publish immediately (True) or save as draft (False)
update_articleB
Update an existing article on Dev.to

Args:
    article_id: The ID of the article to update
    title: New title for the article (optional)
    body_markdown: New content in markdown format (optional)
    tags: New comma-separated list of tags (optional)
    published: Change publish status (optional)

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

B3.4/5.0

Scored across 10 tools

Disambiguation4/5

Most tools have distinct purposes targeting different operations (create, get, update, search), but there is some ambiguity between get_article_by_id and get_article_details which appear to serve similar retrieval functions. The other tools are clearly differentiated by their target data or action.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern with snake_case throughout (e.g., create_article, get_articles_by_tag, update_article). The naming is predictable and follows a clear convention without any deviations in style or structure.

Tool Count5/5

With 10 tools, this server is well-scoped for managing Dev.to content, covering core operations like CRUD for articles, user info retrieval, and various query methods. Each tool serves a specific purpose without bloat, making the count appropriate for the domain.

Completeness4/5

The toolset provides comprehensive coverage for article management (create, read, update, search) and user information, but lacks delete functionality for articles, which is a minor gap. Core workflows are supported, and agents can likely work around the missing delete operation.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources