esa MCP Server
OfficialRelated Servers
Alternatives to esa MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityFmaintenanceEnables interaction with esa.io team documentation including creating, reading, updating, and deleting posts, managing tags, and handling comments through natural language.46 npm2MIT
- AlicenseBqualityCmaintenanceEnables interaction with esa.io's API through the Model Context Protocol, supporting article search and retrieval with a compliant MCP interface.730 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.303 npm1MIT
- AlicenseBqualityBmaintenanceEnables integration with Kibela API for searching and retrieving notes, allowing LLMs to interact with Kibela content seamlessly.129 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.3381 npm29ISC
TDQS
Scored across 28 tools
Most tools target a distinct resource-action pair, but the category trio (get_categories, get_top_categories, get_all_category_paths) and the ship_post vs update_post overlap could cause initial confusion. The descriptions do a good job clarifying boundaries, so misselection is unlikely with careful reading.
All tools follow the esa_ prefix with snake_case and mostly verb_noun structure (get_post, create_comment, delete_comment, ship_post). The few plural/singular variations (posts vs post) are minor and do not disrupt the consistent pattern.
28 tools is on the heavier side and includes three separate documentation/help tools plus fine-grained append/prepend operations that add bulk. However, given esa's broad scope (posts, comments, categories, teams, attachments), the count is still within a defensible range.
The core lifecycle is well covered: posts have create/get/update/append/prepend/archive/duplicate/rollback, comments have full CRUD, and teams, search, categories, and attachments are represented. Obvious gaps like no delete_post (archive serves that purpose) and no category creation/upload tool are minor or aligned with esa's model.