Dev.to Blog Publisher MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DEVTO_API_KEY | Yes | Your Dev.to API key |
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 |
|---|---|
| publish_blog_to_devtoA | |
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 1 tool
Only one tool exists, so there is no possibility of confusing it with others. The tool's purpose is clear from its name and description.
The single tool uses a clear verb_noun pattern (publish_blog_to_devto), consistent with common MCP naming conventions, though there is no other tool to compare.
Having exactly one tool for a blogging platform is very thin; a typical integration would need at least listing, updating, and deleting articles. This falls on the borderline of being too few.
The server only supports publishing posts; there are no operations for reading, updating, deleting, or listing existing articles. This is a significant gap that would prevent an agent from managing a blog lifecycle.