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
Zenn MCP Server
Related Servers
Alternatives to Zenn MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceA Model Context Protocol (MCP) compliant server that allows Large Language Models (LLMs) to search and retrieve content from microCMS APIs.2MIT
- AlicenseAqualityCmaintenanceA Model Context Protocol server that enables AI agents to interact with Qiita, allowing for creating, reading, and updating articles through standardized MCP tools.513 npm9MIT
- FlicenseNot gradedqualityBmaintenanceA Model Context Protocol (MCP) server for DEV.to (Forem API) built with Python and FastMCP.-
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that provides a standardized interface for AI models to access, query, and modify content in Notion workspaces.2,433 npm4MIT
- FlicenseNot gradedqualityDmaintenanceA Model Context Protocol server implementation using Node.js, TypeScript, and Bun, designed for serverless and edge deployments on Vercel and Cloudflare.1-
TDQS
B3.1/5.0
Scored across 2 tools
Disambiguation5/5
The two tools have clearly distinct purposes: one fetches articles and the other fetches books from Zenn.dev. There is no overlap in functionality, and an agent can easily differentiate between them based on the resource type (articles vs. books).
Naming Consistency5/5
Both tools follow a consistent naming pattern using simple, descriptive nouns (article and book) that directly indicate the resource being fetched. There are no deviations in style or convention, making the naming straightforward and predictable.
Tool Count2/5
With only two tools, the server feels thin for a content platform like Zenn.dev. While fetching articles and books covers core read operations, the lack of tools for creating, updating, or managing content (e.g., publishing, searching, or user interactions) makes the set under-scoped for typical agent workflows.
Completeness2/5
The tool set is severely incomplete for a Zenn.dev server. It only supports fetching articles and books, missing essential operations such as creating or updating content, searching, managing user profiles, or handling interactions (e.g., likes, comments). This will likely cause agent failures when trying to perform common tasks beyond basic retrieval.
Maintenance
ActivityInactive
ResponsivenessNo issues