Elasticsearch

Elasticsearch is the search and analytics engine where a lot of teams keep their logs, product catalogs, orders and events. The official connector, published by Elastic, connects the agent to your Elasticsearch data using the Model Context Protocol so you can — in the README's words — "interact with your Elasticsearch indices through natural language conversations."

The agent can see which indices you have, look at how a given index is structured, and run searches across your data — then read the results back to you in plain language. A heads-up worth being clear about: Elastic states that this repository "contains experimental features intended for research and evaluation and are not production-ready." Treat it as an evaluation tool, not something to point at a critical production system.

What you can ask

• "What indices do I have in my Elasticsearch cluster?"
• "Show me the field mappings for the 'products' index."
• "Find all orders over $500 from last month."

What token you need

This connector needs two things: the URL of your Elasticsearch instance, and a way to authenticate. Elastic notes you must provide either an API key or a username and password — this connector uses an API key.

• ES_URL — your Elasticsearch instance URL (required). This is the address where your cluster lives.
• ES_API_KEY — an Elasticsearch API key that lets the agent authenticate (required for this setup).

To create an API key:

1. Open Kibana and go to Stack Management → Security → API keys (see Elastic's API keys guide).
2. Click Create API key, give it a name, and — following Elastic's own security advice — grant it only the permissions the agent needs (read plus view metadata on the specific indices), not cluster-admin.
3. Copy the key value and paste it when the Lab asks for ES_API_KEY, and paste your cluster address into ES_URL. Both are stored encrypted in your Keychain.

Elastic warns against cluster-admin privileges: create a dedicated key with limited scope and apply access control at the index level, so the agent only ever sees the data you meant it to.