ESA

Provides MCP endpoints to search and read esa.io posts using the MCP interface.
  • typescript

0

GitHub Stars

typescript

Language

7 months ago

First Indexed

3 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs
{
  "mcpServers": {
    "mcp-mirror-d-kimuson_esa-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "esa-mcp-server@latest"
      ],
      "env": {
        "ESA_API_KEY": "YOUR_API_KEY",
        "DEFAULT_ESA_TEAM": "YOUR_DEFAULT_TEAM"
      }
    }
  }
}

You can run a dedicated MCP server that exposes esa.io’s articles via the MCP interface. This server lets you search for posts and fetch post details while keeping responses optimized for MCP clients.

How to use

Set up the server as an MCP provider so your client can perform actions like searching esa.io posts and reading single or multiple posts. You will connect via the MCP protocol, call the available endpoints, and handle the results in your application. The server focuses on returning only the necessary data for MCP clients and avoids including full post bodies in search responses to save tokens.

How to install

Prerequisites you need before installing: you must have Node.js and npm (or a compatible environment) installed on your machine.

  1. Verify Node.js and npm are installed.

  2. Prepare your MCP configuration. Create a configuration that enables the esa MCP server using the command and environment keys shown below.

  3. Run the MCP server using the provided command. You will typically execute a package runner to start the server as an MCP endpoint.

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

Additional setup notes

The server config uses an inline MCP setup where you specify the command and arguments to launch the MCP server. Include your API key and default team in the environment so the server can authenticate with esa.io and resolve the team context for requests.

Available tools

search_esa_posts

Search esa.io articles. Returns matching posts, excluding full bodies in MCP responses to optimize token usage.

read_esa_post

Fetch a single esa.io post by post number. Returns the post metadata and related data within MCP constraints.

read_esa_multiple_posts

Fetch multiple esa.io posts in a single call by providing an array of post numbers.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational