esa-mcp
Related Servers
Alternatives to esa-mcp
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.727 npm37MIT
- AlicenseNot gradedqualityFmaintenanceEnables interaction with esa.io team documentation including creating, reading, updating, and deleting posts, managing tags, and handling comments through natural language.24 npm2MIT

esa MCP Serverofficial
AlicenseAqualityAmaintenanceEnables AI assistants to interact with esa.io teams, including reading, creating, updating, and managing articles, comments, categories, and more.282,249 npm62MIT- FlicenseAqualityDmaintenanceEnables searching and browsing Qiita articles, including filtering by tags and users, retrieving comments, and accessing bookmarked articles. Supports both public Qiita and private Qiita Team instances.7-
- AlicenseNot gradedqualityAmaintenanceEnables searching local OpenAI Codex conversation history by keywords, project, date, or role, listing sessions, and retrieving exact supporting messages through MCP tools.1MIT
- FlicenseAqualityCmaintenanceEnables Codex to interact with the Atera REST API, including reading customers, agents, tickets, and alerts, checking health, and listing capabilities, with optional write operations when explicitly enabled.10-
TDQS
Scored across 5 tools
Each tool targets a distinct resource and action: listing teams, searching posts, getting a post, listing recent posts, and listing comments. There is no overlap in purpose, so an agent can easily select the correct tool.
All tool names follow a consistent pattern: the 'esa_' prefix followed by a snake_case verb_noun combination (list_teams, search_posts, get_post, list_recent_posts, list_comments). This is predictable and easy to parse.
Five tools is a well-scoped set for a focused read-only client of the esa API. Each tool covers a meaningful operation, and there are no redundant or filler tools.
The surface covers core read operations (teams, posts, comments, search) but has notable gaps: no way to list all posts in a team (only recent or search), no single comment retrieval, and no create/update/delete operations that are typical for managing esa content. These omissions could cause agent failures for common workflows.