devto-article-mcp
Allows validation of local Markdown articles and creation of unpublished drafts on Dev.to through the Forem API.
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
Dev.to Article MCP
An offline-first Model Context Protocol server that lets Kiro validate repository-native Dev.to Markdown, preview/apply conservative frontmatter fixes, and create a real unpublished Dev.to draft through the official Forem API.
Why this MCP exists
Kiro can edit files, but it does not inherently know this repository's article tree, publishing constraints, changed-file set, or safe draft workflow. This server adds deterministic diagnostics and a guarded bridge from local content to Dev.to without exposing publish, update, delete, browse, or community-API tools.
Related MCP server: Dev.to Blog Publisher MCP Server
Requirements
Node.js 24+
npm
Git (for
validate_changed_articles)A Dev.to API key only for live draft creation
Setup
npm ci
npm run buildConfigure the built stdio server in your MCP host. Prefer loading secrets from a
gitignored .env via Node's --env-file (do not put the real key in mcp.json):
{
"mcpServers": {
"devto-article-mcp": {
"command": "node",
"args": [
"--env-file=/absolute/path/devto-article-mcp/.env",
"/absolute/path/devto-article-mcp/dist/src/index.js"
],
"env": {
"WORKSPACE_ROOT": "/absolute/path/to/your/repository",
"ARTICLES_ROOT": "articles"
}
}
}
}Create .env from .env.example and set DEVTO_API_KEY there. Never commit .env.
Tools
validate_article(file)— validate one workspace-relative Markdown file.validate_articles(directory?)— recursively validate Markdown (defaults toARTICLES_ROOT).validate_changed_articles(base?)— validate staged, unstaged, untracked, or base-relative articles.fix_article(file, mode, hashes, decisions?)— preview or atomically apply the exact reviewed fix plan.create_devto_draft(file)— validate, then create an unpublished draft withpublished: false.
All tools remain registered without DEVTO_API_KEY; only draft creation returns API_KEY_MISSING. The default test suite and all validation/fixing work fully offline.
Typical Kiro flow
“Validate
articles/demo.md.”Review the path, line, stable rule ID, and suggested correction.
“Preview fixes for that article.”
Explicitly confirm ambiguous changes such as replacing
dev-towithdevto, then apply.Revalidate.
“Create an unpublished Dev.to draft from
articles/demo.md.”Open the returned real Dev.to draft URL and verify it remains unpublished.
The request builder strips local frontmatter from body_markdown, maps supported metadata into JSON, and always forces published: false. Local IDs and dates are never used for remote updates.
Configuration
Variable | Default | Purpose |
| process cwd | Trusted repository root |
|
| Relative article directory |
| unset | Forem credential for draft creation |
|
| Forem API endpoint |
|
|
|
|
| Bounded article read size |
|
| Enable optional Liquid diagnostics |
Verification
npm test
npm run typecheck
npm run build
npm run test:coverageThe offline suite uses deterministic property-test seeds and is designed to complete in under 30 seconds. A manual command creates one real side-effecting draft:
DEVTO_API_KEY=... npm run smoke:live-draft -- articles/demo.mdThis command is intentionally excluded from CI. See docs/runbook.md for troubleshooting and docs/demo/README.md for the recording checklist.
Safety and limitations
Workspace containment rejects traversal, outside absolute paths, and symlink escapes.
Reads are bounded and require valid UTF-8.
Validation and draft creation never modify local files.
Fix apply uses dual hashes and same-directory atomic replacement.
API keys are never emitted in tool output or logs.
The remote surface creates drafts only; it cannot publish or mutate existing posts.
HTML
<img>validation and Liquid detection are outside the default MVP rule set.
Architecture
The stdio MCP layer calls isolated tool handlers over a core pipeline: path safety → bounded read → YAML/Markdown parsing → pure rule evaluation → deterministic result aggregation. Git detection, fixing, and the Forem client are separate adapters with structured operational errors.
Demo video: https://youtu.be/Mm0uAhi0jcs
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
Create, edit and publish micropage.sh landing pages and blog posts from markup.
Render markdown into email-safe HTML, lint drafts for deliverability problems, and preview emails.
Lint and diff DESIGN.md files with the official Google linter, or write one from a web page.
Draft, update and publish changelog releases in your Onset workspace.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceAutomates posting articles to Dev.to and sharing posts on LinkedIn via command-line, cron jobs, or Copilot sessions.MIT
- AlicenseAqualityDmaintenanceEnables publishing markdown blog posts directly to Dev.to as drafts or live articles through a single MCP tool, with support for tags, series, canonical URL, and cover image.1MIT
- AlicenseAqualityCmaintenanceEnables managing a Dev.to account from Claude or any MCP client, including browsing articles, creating/editing posts, and reading comments. Uses the official Forem API with a personal API key.7MIT
- AlicenseNot gradedqualityCmaintenanceEnables publishing, drafting, listing, and backing up local Markdown posts to Velog, with automatic local image upload and CDN link rewriting.MIT