A
licenseNot graded
qualityD
maintenanceEnables publishing blog posts directly to Dev.to through the Model Context Protocol, allowing seamless content creation and publication via natural language interactions.
MIT
@dayby/mcp-server
by ja-roque
Related Servers
Alternatives to @dayby/mcp-server
No user-submitted related servers found.
Related Servers
- FlicenseAqualityDmaintenanceEnables AI assistants to publish blog posts directly to Dev.to via the Model Context Protocol.11-
- AlicenseNot gradedqualityDmaintenanceScans Git repositories, identifies interesting engineering work, and generates LinkedIn post drafts with built-in confidentiality sanitisation.MIT
- FlicenseNot gradedqualityCmaintenanceAutomates posting articles to Dev.to and sharing posts on LinkedIn via command-line, cron jobs, or Copilot sessions.-
- AlicenseNot gradedqualityAmaintenanceCaptures AI conversation summaries, converts them to Markdown posts, and manages local or remote publishing with metrics tracking.MIT
- AlicenseBqualityDmaintenanceEnables sharing coding progress on Twitter by analyzing sessions and generating tweet suggestions, with tools for posting tweets, threads, and OAuth authentication.84 npm9MIT
TDQS
A3.6/5.0
Scored across 9 tools
Disambiguation4/5
Most tools map cleanly to distinct lifecycle stages: draft, edit, publish, update, delete. The main potential confusion is between update_post and update_article, since both modify an existing post, though their descriptions differentiate general content updates from HTML article replacement.
Naming Consistency4/5
Tool names mostly follow a clear verb_noun snake_case pattern: list_posts, get_post, publish_post, update_post, delete_post, check_content. Minor deviations exist with edit_draft and update_article, which use different object nouns, and draft_post could be read as a noun phrase, but the overall convention is still predictable.
Tool Count5/5
Nine tools is a well-scoped size for a focused post-management server. Each tool covers a meaningful part of the drafting, publishing, updating, and deletion workflow without redundancy or excessive surface area.
Completeness4/5
The core lifecycle is covered well: draft, edit draft, publish, list, get, update, delete, and content checking. The main gap is that once a draft is created, there is no explicit way to list or retrieve saved drafts, which could make the edit_draft workflow harder to use.
Maintenance
ActivityInactive
ResponsivenessNo issues