MCP 7e9e55a8

MCP数据服务

提供方 未标注

数据服务 stdio · 本地进程 未标注 社区 / 第三方
查看接入方式

全面解析MCP Server ElasticsearchMCP Server的核心功能、安装配置和实用案例。作为顶级Model Context Protocol服务器,MCP Server Elasticsearch能让AI助手访问实时数据、执行操作,为您提供更智能的工作体验和自动化解决方案。

一句话选型结论

按资料字段整理

MCP 7e9e55a8 属于数据服务类 MCP 服务器,stdio · 本地进程,鉴权方式未标注,有可直接执行的安装命令。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类数据服务 传输方式stdio · 本地进程 鉴权未标注 部署方式本地部署
GitHub 星标 未标注 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

数据服务
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

安装与配置

stdio · 本地进程 未标注
客户端在本机拉起子进程,数据不出本机
npx @elastic/mcp-server-elasticsearch --ES_URL=\u003Cyour-elasticsearch-url> --ES_API_KEY=\u003Cyour-api-key>\"

这条命令只是入口,具体启动参数请按官方文档补齐,不要直接照搬到别的服务器。

  1. 1
    准备运行环境

    stdio 服务在本地起进程,需要先装好 Node.js,再按安装命令拉取依赖。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
数据库查询

用自然语言查库、取数,不用手写 SQL。

数据同步与清洗

把多来源数据拉到一处做整理。

报表取数

按口径快速拉出统计结果。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 有现成的安装命令,不用自己找入口,照着跑就能起服务。

先想清楚的地方

  • stdio 方式要求本地装好运行时(如 Node.js),换机器要重新装一遍。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在数据服务场景里让模型直接调用外部能力的人。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 完全不想在本地装环境的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
MCP 7e9e55a8当前 未标注 stdio · 本地进程 本地部署 有 2026-05-17
Memory 9d25f64e 9 未标注 未标注 无 2026-05-17
Getzep MCP 9 stdio · 本地进程 本地部署 有 2026-05-17
anything-llm 未标注 stdio · 本地进程 本地部署 有 2026-04-11
Prisma MCP Server 未标注 stdio · 本地进程 本地部署 有 2026-05-17
Astr Bot 未标注 stdio · 本地进程 本地部署 有 2026-05-17

服务器档案

数据服务
字段来自项目仓库与公开索引,中文说明由本站标注
提供方未标注上游标注的维护方 未标注
分类数据服务本站按上游分类展示
连接方式stdio · 本地进程客户端在本机拉起子进程,数据不出本机
鉴权方式未标注远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · Node.js本地安装时用到的包标识与运行时
部署类型本地部署上游给出的部署形态
最近核验2026-05-17上游最后核验时间

详细介绍

9.4 KB
来自项目仓库与上游目录的原文,未做删改

Elasticsearch MCP Server

> [!CAUTION]
> This MCP server is deprecated and will only receive critical security updates going forward.
> It has been superseded by the Elastic Agent Builder MCP endpoint, which is available in Elastic 9.2.0+ and Elasticsearch Serverless projects.

Use the Elasticsearch MCP Server for AI Agents

The Elasticsearch MCP Server connects your AI agents to Elasticsearch data using the Model Context Protocol (MCP).
It enables natural language interactions with your Elasticsearch indices, allowing agents to query, analyze, and retrieve data without custom APIs.

Follow these steps to deploy and configure the Elasticsearch MCP Server container image from AWS Marketplace.

Before you begin

Before you start, ensure you have:

  • An Elasticsearch cluster (version 8.x or 9.x) accessible from your AWS environment
  • Elasticsearch authentication credentials:
  • An API key, or
  • A username and password pair
  • Docker installed and running in your AWS environment (for example, on an EC2 instance or in a container service)
  • An MCP client configured (such as Claude Desktop, Cursor, VS Code, or another MCP-compatible tool)
  • Network connectivity between your deployment environment and your Elasticsearch cluster

> [!NOTE]
>
> These instructions apply to Elasticsearch MCP Server 0.4.0 and later.
> For versions 0.3.1 and earlier, refer to the README for v0.3.1.

Deploy the Elasticsearch MCP Server

The Elasticsearch MCP Server is provided as a Docker container image available from AWS Marketplace. You can run it using either the stdio protocol (for direct client connections) or the streamable-HTTP protocol (for web-based integrations).

Choose a protocol

The server supports two protocols:

  • stdio: Direct communication between the MCP client and server. Use this when your client supports stdio and runs in the same environment.
  • streamable-HTTP: HTTP-based protocol recommended for web integrations, stateful sessions, and concurrent clients.

> Note: Server-Sent Events (SSE) is deprecated. Use streamable-HTTP instead.

Configure the stdio protocol

Use the stdio protocol when your MCP client connects directly to the server process.

Set environment variables for stdio mode

Set the following environment variables:

  • ES_URL: The URL of your Elasticsearch cluster (for example, https://your-cluster.es.amazonaws.com:9200)
  • For authentication, use one of these options:
  • API key: Set ES_API_KEY to your Elasticsearch API key
  • Basic authentication: Set ES_USERNAME and ES_PASSWORD to your Elasticsearch credentials
  • (Optional) ES_SSL_SKIP_VERIFY: Set to true to skip SSL/TLS certificate verification when connecting to Elasticsearch. Only use this for development or testing environments.

Run the container in stdio mode

Start the MCP server in stdio mode:```bash
docker run -i --rm \
-e ES_URL \
-e ES_API_KEY \
docker.elastic.co/mcp/elasticsearch \
stdio


#### Configure Claude Desktop

Add this configuration to your Claude Desktop configuration file:```json
{
  "mcpServers": {
    "elasticsearch-mcp-server": {
      "command": "docker",
      "args": [
        "run", "-i", "--rm",
        "-e", "ES_URL",
        "-e", "ES_API_KEY",
        "docker.elastic.co/mcp/elasticsearch",
        "stdio"
      ],
      "env": {
        "ES_URL": "<elasticsearch-cluster-url>",
        "ES_API_KEY": "<elasticsearch-API-key>"
      }
    }
  }
}

Replace with your Elasticsearch cluster URL and with your API key.

Configure the streamable-HTTP protocol

Use the streamable-HTTP protocol for web-based integrations or when you need to support multiple concurrent clients.

Set environment variables for HTTP mode

Set the same environment variables as the stdio protocol:

  • ES_URL: The URL of your Elasticsearch cluster
  • For authentication, use one of these options:
  • API key: Set ES_API_KEY to your Elasticsearch API key
  • Basic authentication: Set ES_USERNAME and ES_PASSWORD to your Elasticsearch credentials
  • (Optional) ES_SSL_SKIP_VERIFY: Set to true to skip SSL/TLS certificate verification

Run the container in HTTP mode

Start the MCP server in HTTP mode:```bash
docker run --rm \
-e ES_URL \
-e ES_API_KEY \
-p 8080:8080 \
docker.elastic.co/mcp/elasticsearch \
http


The streamable-HTTP endpoint is available at `http://:8080/mcp`. A health check endpoint is available at `http://:8080/ping`.

#### Configure Claude Desktop with HTTP proxy

If you're using Claude Desktop (free edition) which only supports the stdio protocol, use `mcp-proxy` to bridge stdio to streamable-HTTP:

1. Install `mcp-proxy`:```bash
   uv tool install mcp-proxy
   ```
   For alternative installation options, refer to mcp-proxy/README.md.

2. Add this configuration to Claude Desktop:```json
   {
     "mcpServers": {
       "elasticsearch-mcp-server": {
         "command": "/<home-directory>/.local/bin/mcp-proxy",
         "args": [
           "--transport=streamablehttp",
           "--header", "Authorization", "ApiKey <elasticsearch-API-key>",
           "http://<mcp-server-host>:<mcp-server-port>/mcp"
         ]
       }
     }
   }
   ```

   Replace ``, ``, ``, and `` with your values.

### Verify the connection

After configuring your MCP client, verify the connection works:

1. Start your MCP client (for example, Claude Desktop or Cursor).
2. Check that the Elasticsearch MCP Server appears in your available MCP servers.
3. Test a simple query through your agent interface to confirm it can access your Elasticsearch indices.

If the connection fails, verify:

- Your Elasticsearch cluster URL is correct and accessible from your AWS environment
- Your authentication credentials are valid and have the necessary permissions
- Network connectivity exists between the container and your Elasticsearch cluster (check security groups and network ACLs)
- Docker is running and the container started successfully (check container logs with `docker logs `)

### Monitor health and status

Monitor the health and proper function of the Elasticsearch MCP Server using these methods:

#### Check container status

Verify the container is running:```bash
docker ps | grep elasticsearch-mcp-server

The container should appear in the list with a status of Up.

Test the health endpoint (HTTP mode)

If you're using the streamable-HTTP protocol, test the health check endpoint:```bash
curl http://<host>:8080/ping


A successful response returns `pong`, indicating the server is running and healthy.

#### Check container logs

View container logs to identify any issues:```bash
docker logs &lt;container-id&gt;

Look for error messages related to:

  • Elasticsearch connection failures
  • Authentication errors
  • Network connectivity issues

Verify Elasticsearch connectivity

Test connectivity to your Elasticsearch cluster from the container:```bash
docker exec <container-id> curl -k -u <username>:<password> <ES_URL>


Or with an API key:```bash
docker exec &lt;container-id&gt; curl -k -H &quot;Authorization: ApiKey &lt;api-key&gt;&quot; &lt;ES_URL&gt;

A successful response indicates the container can reach your Elasticsearch cluster.

Security and sensitive information

The Elasticsearch MCP Server handles authentication credentials securely:

Credential storage

  • API keys and passwords: Stored only in environment variables passed to the container. They are not persisted to disk or logged.
  • Environment variables: Set when you run the container. Use AWS Secrets Manager or AWS Systems Manager Parameter Store to manage credentials securely in production environments.

Data encryption

  • In transit: The MCP server communicates with Elasticsearch over HTTPS when your ES_URL uses the https:// protocol. Ensure your Elasticsearch cluster has SSL/TLS enabled.
  • At rest: The container does not store data locally. All data remains in your Elasticsearch cluster, which uses your cluster's encryption settings.

Best practices

  • Rotate API keys regularly (every 30-90 days for production environments)
  • Use API keys with minimal required permissions (read-only access to specific indices when possible)
  • Never commit credentials to version control or share them in logs
  • Use AWS Secrets Manager or Parameter Store to inject credentials at runtime instead of hardcoding them

AWS service quotas

The Elasticsearch MCP Server runs as a container in your AWS environment. Consider these AWS service quotas:

  • EC2 instance limits: If running on EC2, ensure your instance type supports your expected workload
  • Elastic Container Service (ECS): If using ECS, review ECS service quotas
  • Elastic Kubernetes Service (EKS): If using EKS, review EKS service quotas
  • Network bandwidth: Ensure sufficient network bandwidth between your container and Elasticsearch cluster

To request quota increases, use the AWS Service Quotas console or refer to the AWS General Reference Guide.

Available tools

Once connected, the MCP server provides these tools to your agent:

  • list_indices: List all available Elasticsearch indices
  • get_mappings: Get field mappings for a specific Elasticsearch index
  • search: Perform an Elasticsearch search using query DSL
  • esql: Execute an ES|QL query
  • get_shards: Get shard information for all or specific indices

Your agent can use these tools to interact with your Elasticsearch data through natural language conversations.

Next steps

  • Learn about AI-powered features available in the Elastic platform
  • Explore Agent Builder for building custom AI agents with Elasticsearch

常见问题

7 问
答案由本站依据条目字段整理,不引用上游原文
MCP 7e9e55a8 怎么安装?

在客户端按下面的安装命令接入:npx @elastic/mcp-server-elasticsearch --ES_URL=\u003Cyour-elasticsearch-url> --ES_API_KEY=\u003Cyour-api-key>\"。装完在客户端配置里引用同一个包或端点。

MCP 7e9e55a8 怎么在客户端里配置?

它的传输方式未标注,在客户端 MCP 配置里按官方文档填写启动命令和参数,保存后重启客户端生效。

MCP 7e9e55a8 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

MCP 7e9e55a8 需要 API Key 吗?

资料没有标注鉴权方式,是否需要密钥取决于服务本身,接入前按官方文档确认。

MCP 7e9e55a8 能提供哪些能力?

资料显示能力标签包括 数据分析、自然语言、JavaScript、STDIO。具体工具清单以官方文档为准。

MCP 7e9e55a8 需要什么运行环境?

运行时为 Node.js;属于本地进程,需要在本机装好运行环境。

MCP 7e9e55a8 是本地还是远程?

它是本地进程(stdio),由客户端在本机拉起。传输方式为stdio · 本地进程。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 2026-05-17。