Skip to main content
Glama
ESA MCP Server

ESA MCP Server

by d-kimuson

esa-mcp-server

Smithery badge

esa-mcp-server is a server that makes esa.io 's API available via the Model Context Protocol (MCP) .

function

  • get_search_query_document: Provides documentation to search articles on esa.io

  • search_esa_posts: Search for esa.io articles

  • read_esa_post, read_esa_multiple_posts: Get details of posts (single/multiple)

  • create_esa_post: Create an article

  • update_esa_post: Update an article

  • delete_esa_post: Delete an article

Related MCP server: CODING DevOps MCP Server

Usage

Please prepare a configuration file as follows according to the tool you will use.

{
  "mcpServers": {
    "esa-mcp-server": {
      "command": "npx",
      "args": ["-y", "esa-mcp-server@latest"],
      "env": {
        "ESA_API_KEY": "your api key here",
        "DEFAULT_ESA_TEAM": "your default esa team"
      }
    }
  }
}

Example prompt

## Using esa tools

esa の情報を検索するために esa 以下のツールを利用できます。

- 記事の検索には search_esa_posts ツールを利用します。複雑なクエリを利用する場合は get_search_query_document ツールで正確なクエリの記述方法を理解してから利用します。
- 記事本文を取得するには read_esa_post, read_esa_multiple_posts ツールを利用します。複数の記事を取得する必要がある場合は read_esa_multiple_posts でまとめて取得することを推奨します。
- 記事を作成/更新/削除するにはそれぞれ create_esa_post, update_esa_post, delete_esa_post ツールを利用します。

Available Tools

Check out src/server.ts .

Contribution

You are welcome.

Available Tools

7 tools
create_esa_postC

Create a new post in esa.io. Required parameters: name. Optional parameters: body_md, tags, category, wip (default: true), message.

Inputs: name (required), teamName, body_md, tags, +3 more.

delete_esa_postC

Delete a post in esa.io. Required parameters: postNumber.

Inputs: postNumber (required), teamName.

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.

Inputs: no named parameters.

read_esa_multiple_postsC

Read multiple posts in esa.io.

Inputs: postNumbers (required), teamName.

read_esa_postC

Read a post in esa.io.

Inputs: postNumber (required), teamName.

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.

Inputs: query (required), teamName, order, sort, +2 more.

update_esa_postC

Update an existing post in esa.io. Required parameters: postNumber. Optional parameters: name, body_md, tags, category, wip, message.

Inputs: postNumber (required), teamName, name, body_md, +4 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.4/5.0

    Scored across 7 tools

    Disambiguation4/5

    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.

    Naming Consistency4/5

    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.

    Tool Count5/5

    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.

    Completeness5/5

    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.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers