ESA MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ESA_API_KEY | Yes | Your esa.io API key | |
| DEFAULT_ESA_TEAM | Yes | Your default esa team |
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 |
|---|---|
| get_search_query_documentA | Retrieves comprehensive documentation about esa.io search queries. Provides detailed information about available query syntax, operators, and search parameters to effectively search through esa posts. |
| search_esa_postsA | Search posts in esa.io. Response is paginated. For efficient search, you can use customized queries like the following: keyword for partial match, "keyword" for exact match, keyword1 keyword2 for AND match, keyword1 OR keyword2 for OR match, -keyword for excluding keywords, title:keyword for title match, wip:true or wip:false for WIP posts, kind:stock or kind:flow for kind match, category:category_name for partial match with category name, in:category_name for prefix match with category name, on:category_name for exact match with category name, body:keyword for body match, tag:tag_name or tag:tag_name case_sensitive:true for tag match, user:screen_name for post author's screen name, updated_by:screen_name for post updater's screen name, comment:keyword for partial match with comments, starred:true or starred:false for starred posts, watched:true or watched:false for watched posts, watched_by:screen_name for screen name of members watching the post, sharing:true or sharing:false for shared posts, stars:>3 for posts with more than 3 stars, watches:>3 for posts with more than 3 watches, comments:>3 for posts with more than 3 comments, done:>=3 for posts with 3 or more done items, undone:>=3 for posts with 3 or more undone items, created:>YYYY-MM-DD for filtering by creation date, updated:>YYYY-MM-DD for filtering by update date.Strongly recommend see get_search_query_document for complete query usage. |
| read_esa_postC | Read a post in esa.io. |
| read_esa_multiple_postsC | Read multiple posts in esa.io. |
| create_esa_postC | Create a new post in esa.io. Required parameters: name. Optional parameters: body_md, tags, category, wip (default: true), message. |
| update_esa_postC | Update an existing post in esa.io. Required parameters: postNumber. Optional parameters: name, body_md, tags, category, wip, message. |
| delete_esa_postC | Delete a post in esa.io. Required parameters: postNumber. |
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 7 tools
Most tools have distinct purposes: create, read, update, delete, search, and get documentation. However, read_esa_post and read_esa_multiple_posts could cause confusion as they overlap in reading functionality, though the descriptions clarify single vs. multiple posts. No other significant ambiguities exist.
Tools follow a consistent verb_noun pattern with snake_case throughout, such as create_esa_post and update_esa_post. The only minor deviation is get_search_query_document, which uses 'get' instead of 'read' like other retrieval tools, but this is still clear and follows the same naming style.
With 7 tools, the count is well-scoped for managing posts in esa.io. It covers core CRUD operations (create, read, update, delete), search functionality, and documentation retrieval, which is appropriate for the domain without being overly sparse or bloated.
The tool set provides complete CRUD coverage for posts (create, read, update, delete), along with search capabilities and detailed query documentation. This covers the essential lifecycle and operations for managing posts in esa.io, with no obvious gaps that would hinder agent workflows.