esa MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ESA_TEAM | Yes | Your esa team name | |
| ESA_ACCESS_TOKEN | Yes | Your esa API access token |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| esa_list_postsC | Get a list of posts in the team (with pagination support) |
| esa_get_postC | Get detailed information about a specific post |
| esa_create_postC | Create a new post |
| esa_update_postC | Update an existing post |
| esa_list_commentsC | Get a list of comments for a post |
| esa_get_commentC | Get a specific comment |
| esa_create_commentC | Post a comment to an article |
| esa_get_membersC | Get a list of team members |
| esa_get_memberC | Get information about a specific team member |
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 9 tools
Every tool has a clearly distinct purpose targeting specific resources and actions, with no ambiguity. For example, esa_get_post retrieves a single post, esa_list_posts lists multiple posts, and esa_update_post modifies a post, all clearly differentiated.
All tools follow a consistent verb_noun pattern with the 'esa_' prefix, using clear action verbs like create, get, list, and update paired with specific nouns like post, comment, and member. There are no deviations in naming style.
With 9 tools, this server is well-scoped for managing posts, comments, and members in a team context. Each tool serves a distinct and necessary function, with no redundancy or missing core operations, making the count appropriate for the domain.
The tool surface provides strong coverage for posts and comments with full CRUD operations (create, get, list, update) and includes member management. A minor gap exists with no delete operations for posts or comments, but agents can work around this limitation for most workflows.