service · inferred from evidence
elastic/mcp-server-elasticsearch
A specific MCP server implementation for Elasticsearch, mentioned in compatibility context.
- Elasticsearch MCP: 403 action is unauthorized (API key lacks privileges)
Fixes the Elasticsearch MCP server failing with 403 action unauthorized even though authentication succeeded. The API key or user lacks the privileges for the requested operation. The fix is recreating the key with the needed role descripto
- Elasticsearch MCP: index_not_found_exception (the index name is wrong)
Fixes the Elasticsearch MCP server failing searches with index_not_found_exception. The index name in the query does not exist on the cluster. The fix is listing indices and correcting the name. Use when the cluster connects fine but a spec
- Elasticsearch MCP: plaintext http on an https channel (ES_URL must use the https scheme)
Fixes the Elasticsearch MCP server failing with received plaintext http traffic on an https channel. The cluster speaks HTTPS but the server is configured with an http:// URL. The fix is changing ES_URL to use the https scheme. Use when the
- Elasticsearch MCP: self-signed certificate verify failed (trust the cluster CA)
Fixes the Elasticsearch MCP server failing with SSL certificate verify errors against clusters using self-signed certificates. The fix is pointing the server at the cluster CA certificate or enabling the insecure-skip option for testing. Us
- Elasticsearch MCP: 401 missing authentication credentials (set ES_API_KEY)
Fixes the Elasticsearch MCP server failing with 401 missing authentication credentials for REST request. The server is reaching Elasticsearch but sending no credentials. The fix is setting ES_API_KEY (or username/password) in the server con