A
licenseNot graded
qualityD
maintenanceA Model Context Protocol server that enables AI assistants to programmatically interact with the Hashnode API for creating, updating, searching, and retrieving blog content.
7
MIT
hashnode-mcp-server
by kieksme
Related Servers
Alternatives to hashnode-mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceMCP server for Substack that lets Claude Code create drafts, upload images, set cover thumbnails, schedule, and publish posts on your Substack publication.1116MIT
- AlicenseNot gradedqualityDmaintenanceA generic MCP server that converts .graphql query files into tools for Claude, enabling interaction with any GraphQL API without coding.MIT
- AlicenseAqualityBmaintenanceA generic MCP (Model Context Protocol) server that bridges any GraphQL API to Claude Code. It introspects your GraphQL schema and exposes each query and mutation as an individual tool, letting Claude interact with your API directly.250 npm1MIT
- AlicenseNot gradedqualityDmaintenanceMCP server for Ghost CMS that lets Claude manage posts, pages, members, tags, and newsletters via the Ghost Admin API.25 npmMIT
- FlicenseAqualityDmaintenanceMCP server for blog admin API enabling preview, publish, list, and delete blog posts from Claude Code via stdio transport.5-
TDQS
A3.9/5.0
Scored across 11 tools
Disambiguation4/5
Each tool maps to a distinct resource (publication, draft, post) plus action, so most selections are unambiguous. The only real overlap is the two publishing paths — hashnode_publish_post versus hashnode_create_draft + hashnode_publish_draft — though the descriptions explicitly recommend the latter for safety.
Naming Consistency5/5
Every tool uses the same hashnode_ prefix with a verb_noun structure (list_drafts, create_draft, publish_draft, update_post, delete_post). The lone outlier, hashnode_get_me, is still readable and consistent in style.
Tool Count5/5
At 11 tools the surface is well-scoped: two discovery/read tools, a full draft lifecycle, and full post CRUD. No tool looks redundant enough to remove, and nothing feels padded.
Completeness4/5
Posts have full lifecycle coverage (list, get, publish, update, delete) and drafts cover list/create/update/publish. The notable gap is the absence of a delete_draft (and any comment operations), which agents can work around but leaves drafts unmanageable once created.
Maintenance
ActivityMaintained
ResponsivenessNo recent community issues