Watchlist tracking
Reviewed for relevance and future tracking value.
MCP100 Assessment
Watchlist / Tracking
Why we’re tracking it
The repository marks the server deprecated and points users to Elastic Agent Builder while retaining critical-security-update value; a follow-up can verify the migration and any remaining supported security-maintenance path.
Reviewed · Documentation review; complete setup workflow not independently tested
Best fit
Legacy MCP access to Elasticsearch data and ES|QL queries
What we know
Elastic's deprecated MCP server for querying Elasticsearch indices, mappings, ES|QL and shard information.
Maintenance / activity evidence
- Observed (UTC)chore: upgrade fetch-github-token to v1.5.3 ( 263)
Tracking evidence observed Oct 5, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: high.
Verification gaps / watch-outs
- Installation and comprehensive security have not been independently audited.
- Configured Elasticsearch account privileges. Writes: Primarily query/read operations in the legacy server.
- Elasticsearch credentials.
- Sensitive access: Elasticsearch indices, Credentials
- The successor/deprecation status is the key decision signal; migrate to Agent Builder MCP where supported.
Full authority, access and evidence limits are available in Review context and Access & risk.
Popularity
718 repository stars
Stars observed Sep 25, 2026.
Preserve any already-reviewed adoption metrics in MCP100. Batch 4 did not refresh package downloads because the package-stats provider had insufficient credits.
Preserve any already-reviewed adoption metrics in MCP100. Batch 4 did not refresh package downloads because the package-stats provider had insufficient credits.
All limitations / Review context
Is the deprecated endpoint still receiving the stated critical security updates, and when should users complete migration to Agent Builder?
The bounded assessment reviewed the official README, repository notices, security policy path, and security page for known material public-tracking blockers. No such blocker was identified. This is a public-tracking assessment, not an installation safety certification.
- The successor/deprecation status is the key decision signal; migrate to Agent Builder MCP where supported.
- Configured Elasticsearch account privileges.
- Elasticsearch credentials.
- Queries/results may include sensitive indexed data.
- Reviewed write actions: Primarily query/read operations in the legacy server
- Sensitive access: Elasticsearch indices, Credentials
- Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
- The official README announces supersession by Agent Builder; this review records the migration state without certifying either installation.
- A project-specific SECURITY.md policy was not available at the fetched official path; the review remains limited to published repository notices.
- Explicitly deprecated; publisher retains critical security updates only. Any tracking entry must preserve this limited support status and distinguish the Agent Builder successor.
- No installation, runtime, client matrix, or complete tool-contract audit was performed in this review.
- The fetched official SECURITY.md path returned HTTP 404; it was not treated as positive evidence.
- Deprecated and limited to critical security updates.
- Superseded by Elastic Agent Builder MCP endpoint for Elastic 9.2+/Serverless.
Original activity observations
- 2026-06-23T14:16:12Z: chore: upgrade fetch-github-token to v1.5.3 ( 263)
Technical identity
github.com/elastic/mcp-server-elasticsearch- Exact implementation source
- https://github.com/elastic/mcp-server-elasticsearch ↗
- Reviewed resource type
- MCP Server
- Repository identity
- elastic/mcp-server-elasticsearch
Evidence & Sources
- Evidence basis
- Recorded source evidence
- Setup runtime verification
- Not independently runtime-tested by MCP100 for this setup workflow.
Reviewed · Latest source observation
- GitHub repository ↗
elastic/mcp-server-elasticsearch
Recorded repository material and project history.
Setup · Watchlist
Install & Agents
Publisher instructions.
Source evidence observed .
Additional setup details required — see the specific gaps below.
Install / connect
Publisher instructionsPublisher-specific setup path. Follow prerequisites, then register or connect to your MCP host.
publisher documented install or connect · Publisher instructions
docker run -i --rm -e ES_URL -e ES_API_KEY docker.elastic.co/mcp/elasticsearch stdioConfigure / authenticate
Publisher instructionsOfficial Elastic >=0.4.0 uses Docker; set ES_URL and ES_API_KEY in the host process environment, or ES_USERNAME/ES_PASSWORD. For HTTP `docker run --rm -e ES_URL -e ES_API_KEY -p 8080:8080 docker.elastic.co/mcp/elasticsearch http` serves /mcp.
Check connection
Suggested checkFor HTTP mode `curl http://localhost:8080/ping` only checks service health; then inspect Elasticsearch tools and run read-only query to prove downstream auth.
Remove / uninstall / revoke
MCP100 setup guideRemove `elasticsearch-mcp-server` from the MCP client and stop the dedicated container. Do not delete Elasticsearch databases.
MCP100 client-scope guidance: each CLI removal example targets only its named client and exact registered entry. Package names, Desktop/Cursor configuration keys and Codex/Claude registration names may differ; use the entry you actually registered. Client removal does not revoke provider credentials.
claude mcp remove elasticsearch-mcp-server
What it does
Elastic's deprecated MCP server for querying Elasticsearch indices, mappings, ES|QL and shard information.
- Capability
- Data & Databases
- Resource type
- MCP Server
- Best fit
- Legacy MCP access to Elasticsearch data and ES|QL queries
Representative uses
- Search Elasticsearch
- Inspect mappings
- Run ES|QL
- Inspect shards
Limitations
- Deprecated and limited to critical security updates.
- Superseded by Elastic Agent Builder MCP endpoint for Elastic 9.2+/Serverless.
Reviewed access
Access & risk
Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.
- Authentication
- Elasticsearch credentials.
- Permissions
- Configured Elasticsearch account privileges.
- Data handling
- Queries/results may include sensitive indexed data.
- Cost
- unknown
- Risk and cautions
- The successor/deprecation status is the key decision signal; migrate to Agent Builder MCP where supported.
Access scope and cautions
- Write actions
- Primarily query/read operations in the legacy server
- Sensitive access
- Elasticsearch indices Credentials
- Risk level
- moderate
FAQ
Based on reviewed evidence as of 2026-10-06. Watchlist tracking is not a recommendation or a security certification.
Which implementation does this page cover?
What authentication is documented?
Can it modify data or perform write operations?
What data-handling boundary should I consider?
What limitations and risks should I check before use?
Is this an official MCP?
Elastic is listed as First-party MCP in MCP100’s current evidence.