DevTo MCP server — AI work management for Claude Code
DevTo MCP server — AI work management for Claude Code
DevTo lives inside Claude Code as an MCP server. It manages your sprint, your tickets, and your project tracker — without you ever leaving your terminal. Status updates, ambient comments on transitions, plan generation from natural language, semantic ticket matching. All from your editor.
Compare MCP servers by category, or browse hosted MCP servers if you prefer an endpoint over a local process.
Check the linked publisher documentation and your connected client's tool list. Names and availability can vary with the server version and account permissions.
| Tool | What it does |
|---|---|
| get_project_summary | lightweight snapshot of active work + epic progress (called at session start) |
| get_status | aggregate project metrics |
| list_epics | epic progress bars |
| get_epic | deep dive into a single epic |
| create_plan | AI-generated epic + stories + subtasks (preview only) |
| confirm_plan | execute a previously-previewed plan |
| delete_issue | destructive, asks for confirmation |
| get_tasks | list open tasks, optionally filter by epic |
| search_issues | full JQL support |
{
"mcpServers": {
"devto-1": {
"command": "npx",
"args": ["-y", "devto-mcp"]
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
Read, search and edit files inside allowed directories with the Model Context Protocol reference Filesystem server.
Retrieve version-aware library documentation and code examples with Context7 MCP, using resolve-library-id and query-docs.
Local-first shared memory layer for AI coding agents across MCP clients, Git history, reasoning context, and project sessions.
French real-estate intelligence from official open data: DVF, valuations, rents, tax, DPE, risks.
Offline agentic memory: remember/recall/relate/forget/why over a fused vector+graph+columnar engine
Ten x402-paid tools for JSON, YAML, cron, diff, text, DNS, WHOIS, GitHub, crypto, and email.