devto-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_devto_postsA | Search dev.to articles. Args: query: Search term (searches title, body, tags, user). tag: Optional tag filter (e.g. 'python', 'ai'). per_page: Number of results (max 30). page: Pagination page. top: If set (e.g. 7 for past week), returns top articles instead of search. Returns: List of article summaries with id, title, url, tags, etc. |
| get_devto_articleA | Retrieve a full dev.to article by its ID. Args: article_id: The numeric ID of the article. Returns: Full article object including body_markdown, tags, reactions, etc. |
| search_by_techA | Search articles by technology/tag. Convenience wrapper around search. Args: tech: Technology or tag (e.g. 'python', 'fastapi', 'mcp', 'ai'). per_page: Number of results. top_days: Return top articles from last N days (7, 30, etc.). If None, does text search on tag. Returns: List of matching articles. |
| create_devto_articleA | Create a dev.to article or draft using the authenticated DEV API. Args: title: Article title. body_markdown: Article body in markdown. published: Publish immediately when true. Defaults to false for safety. tags: Comma-separated tags, e.g. "python,ai,mcp". description: Short article description. canonical_url: Original/canonical URL when cross-posting. series: Optional DEV series name. main_image: Optional main image URL. organization_id: Optional DEV organization id. api_key: Optional DEV API key. If omitted, DEVTO_API_KEY is used. Returns: The created article object from dev.to. |
| update_devto_articleA | Update an existing dev.to article by numeric article id. Only fields provided as non-null arguments are sent. Pass api_key or set DEVTO_API_KEY. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Tools `search_devto_posts` and `search_by_tech` both search articles with overlapping functionality (tag filtering, top results), causing ambiguity. An agent may struggle to choose the appropriate one.
Most tools follow a `verb_noun` pattern (`search_devto_posts`, `get_devto_article`, etc.), but `search_by_tech` breaks the pattern with a preposition, and inconsistent pluralization (`posts` vs `article`).
With 5 tools covering search, retrieval, creation, and update, the count is well-scoped for a dev.to article management server, neither too sparse nor too heavy.
Basic CRUD operations are present except deletion, and search covers multiple query patterns. Minor gap in missing delete or listing all user articles, but core workflows are covered.