A
licenseNot graded
qualityF
maintenanceEnables interaction with esa.io team documentation including creating, reading, updating, and deleting posts, managing tags, and handling comments through natural language.
27 npm
2
MIT
esa MCP Server
Officialby esaio
Related Servers
Alternatives to esa MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseBqualityCmaintenanceEnables interaction with esa.io's API through the Model Context Protocol, supporting article search and retrieval with a compliant MCP interface.723 npm37MIT
- AlicenseAqualityCmaintenanceEnables read-only cross-workspace search and browsing of esa.io teams, posts, and comments from Codex CLI, including pagination and recent-post listing via the official API v1.5MIT
- AlicenseBqualityDmaintenanceEnables interaction with Qiita, a Japanese developer community platform, through its API v2. Supports comprehensive operations including article management, user interactions, tag following, and commenting with Japanese language support.307 npm1MIT
- AlicenseBqualityBmaintenanceEnables integration with Kibela API for searching and retrieving notes, allowing LLMs to interact with Kibela content seamlessly.1210 npm7MIT
- AlicenseBqualityCmaintenanceEnables interaction with note.com through API to search and read articles, manage posts and drafts, handle comments and likes, retrieve analytics, and access membership information.3330 npm30ISC
TDQS
A3.5/5.0
Scored across 28 tools
Disambiguation4/5
Most tools target distinct resources/actions, and descriptions explicitly cross-reference alternatives (e.g., esa_get_post vs esa_get_post_backlinks and esa_get_post_comments). Minor overlap exists between esa_update_post and esa_ship_post for shipping, and among the three category-retrieval tools, but guidance reduces confusion.
Naming Consistency5/5
All tools use the esa_ prefix with a consistent snake_case verb_noun structure (get_, create_, update_, delete_, search_, archive_, ship_, etc.). Help tools add a _help suffix but remain predictable and readable.
Tool Count3/5
28 tools is on the heavy side for the rubric's 3-15 ideal, though the breadth covers many esa entities. Some consolidation could reduce overlap, such as merging esa_ship_post into esa_update_post or combining category-retrieval tools.
Completeness4/5
Core post lifecycle (create, get, update, archive, ship, duplicate, rollback) and full comment CRUD are covered. Missing hard delete_post, revision listing, and attachment upload/delete are minor gaps that agents can mostly work around.
Maintenance
ActivityActive
ResponsivenessWithin a week