Dev Blog 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 | Publishes a blog post to dev.to. Args: title (str): The title of the blog post. body_markdown (str): The content of the blog post in Markdown format. tags (Optional[List[str]]): A list of tags for the blog post (e.g., ["python", "webdev"]). published (bool): Set to True to publish immediately, False to save as a draft. series (Optional[str]): The name of the series this article belongs to. canonical_url (Optional[str]): The canonical URL of the article if it's cross-posted. cover_image (Optional[str]): URL of the cover image for the article. Returns: str: A message indicating the success or failure of the publishing operation, including the article URL if successful. |
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
With only one tool, there is no possibility of ambiguity or misselection. The tool's purpose is clear from its name and description.
The single tool name 'publish_blog_to_devto' is descriptive and follows a verb-object pattern, though it's somewhat verbose. Since there is only one tool, consistency is trivially maintained.
A single tool for a blog publishing server is extremely thin. Typical blog workflows require listing, editing, and deleting posts, so one tool is insufficient for the apparent scope.
The tool only supports publishing, with no ability to retrieve, update, or delete existing posts. This leaves significant gaps in the content lifecycle and would force agents to use external APIs.