esa-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ESA_ACCESS_TOKEN | Yes | esa access token with read scope, required to authenticate to the esa API. The server reads it from the environment at startup. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| esa_list_teamsA | List all teams accessible to the current esa user, following all pages. Cached for 60 seconds. |
| esa_search_postsA | Search esa posts using esa search syntax. Returns one page per team, newest updated first, with excerpts and per-team next_page. team/teams omitted searches all teams. team and teams cannot be combined. |
| esa_get_postA | Read the full Markdown body of an esa post. Post numbers are only unique within a team. |
| esa_list_recent_postsA | List recently updated posts per team, newest first. Returns one page per team with next_page. Omit team/teams for all teams. |
| esa_list_commentsA | Read a page of comments on a post, with Markdown bodies and next_page. Comments are ordered by update time descending. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.