Search and data
Elasticsearch for AI agents.
Managed auth, ready-made tools.
Search indices, read and write documents and check mappings in Elasticsearch on behalf of each of your users.
About Elasticsearch
With the Elasticsearch connector, your agent works with each user’s own Elasticsearch deployment. It can list indices, check their mappings, run searches, read documents, and add or delete documents, using only the tools your project allows.
Elasticsearch is a search and analytics engine for storing and querying large amounts of data.
Tools
What your agent can do in Elasticsearch.
Each tool is a capability the model can call. You decide which ones a project allows, and every call runs with the end user's own Elasticsearch connection.
-
List indices
Readelasticsearch_list_indicesList the indices in the cluster with their size and health.
-
Get a mapping
Readelasticsearch_get_mappingGet the field mapping of an index.
-
Search
Readelasticsearch_searchRun a search query against an index.
-
Get a document
Readelasticsearch_get_documentGet a document by its ID.
-
Index a document
Writeelasticsearch_index_documentAdd or replace a document in an index.
-
Delete a document
Writeelasticsearch_delete_documentDelete a document by its ID.
No tool matches that search.
Control
Limits you can set.
You decide what your agent may do in Elasticsearch, and Agent200 runs every call within those limits.
-
Turn single tools on or off
Let the agent search and add documents, and switch off
elasticsearch_delete_documentso it can never remove one. -
Restrict what the agent reaches
Choose the endpoints and scopes a project may use, for example search but not writes. A call outside them is refused.
Get started
Connect Elasticsearch
in three steps.
-
1
Set up the SDK
Add the Agent200 SDK to the codebase you already have and authenticate with your API key. The key covers every connector enabled for the project.
agent.jsConceptual exampleSet up the SDK with the Agent200 API key // One Agent200 API key covers every connector enabled for the project. const agent200 = new Agent200({ apiKey: process.env.AGENT200_API_KEY, }); -
2
Let your user connect Elasticsearch
Each end user authorizes their own Elasticsearch account once. Agent200 runs the OAuth flow, handles the callback, stores the tokens and refreshes them.
connect.jsConceptual exampleLet an end user connect their account (managed OAuth) // Each end user authorizes their own Elasticsearch account, once. const connection = await agent200 .user("user_123") .connect("elasticsearch"); if (connection.authorizationUrl) { // Show this link to your user; Agent200 handles the rest. console.log(connection.authorizationUrl); } -
3
Run with the Elasticsearch tools
Name the user, the model and the tools. The model decides which Elasticsearch tools to call, and Agent200 executes them with that user's connection.
run.jsConceptual exampleRun a request with the connector's tools const result = await agent200 .user("user_123") .run({ model: "openai/gpt-5.6-sol", input: "Search the logs index for errors from the checkout service today", tools: ["elasticsearch"], }); console.log(result.output);
Access
Sign-in and permissions.
-
Who signs in
Each of your users, once, by connecting their own Elasticsearch deployment. Each connection is their own.
-
What access is requested
The connection acts with the privileges of the credentials the user connects with, such as reading an index or writing documents. Users can revoke the connection later from their Elasticsearch or Elastic Cloud settings.
For agents
Instructions for AI agents.
Using a coding agent? Paste this brief into it, or give it the address of this page. It describes the Elasticsearch connector and how to use it.
Connector: Elasticsearch, through Agent200. In code: "elasticsearch". What it does: Search indices, read and write documents and check mappings in Elasticsearch on behalf of each of your users. Page: https://www.agent200.com/connectors/elasticsearch/ 1. Get an Agent200 API key. If the developer has none, send them to https://agent200.com/platform/apikeys/ and ask them to choose "Create an API key". Read the key from the AGENT200_API_KEY environment variable. Never ask for it in chat, and never write it into code, prompts or logs. 2. Sign-in is managed OAuth. Each end user approves access once, on Elasticsearch's own page, through the authorization link Agent200 returns. Never ask a user for a Elasticsearch password or token in chat. 3. Give every request a stable id for the end user. Agent200 uses only that user's own connection. 4. Read tools: elasticsearch_list_indices, elasticsearch_get_mapping, elasticsearch_search, elasticsearch_get_document. Write tools: elasticsearch_index_document, elasticsearch_delete_document. Name "elasticsearch" in the tools of a request; the model decides which tool to call. 5. Stay within the project's settings. If a tool is turned off or a call is refused, tell the user. Do not work around it. 6. Before a write, confirm with the user, unless they asked for that exact change. 7. For setup with a specific framework, follow its guide: https://www.agent200.com/connectors/elasticsearch/framework/claude/ https://www.agent200.com/connectors/elasticsearch/framework/chatgpt/ https://www.agent200.com/connectors/elasticsearch/framework/claude-code/ https://www.agent200.com/connectors/elasticsearch/framework/muse/ https://www.agent200.com/connectors/elasticsearch/framework/grok-bot/ https://www.agent200.com/connectors/elasticsearch/framework/openai-dots/ https://www.agent200.com/connectors/elasticsearch/framework/claude-duet/ https://www.agent200.com/connectors/elasticsearch/framework/hermes-agent/ https://www.agent200.com/connectors/elasticsearch/framework/openclaw/ The code on the connector page is a conceptual example of the SDK. SDK reference: https://docs.igpt.ai/
This page is also available as Markdown, for agents and LLMs: /connectors/elasticsearch.md
Guides
Use Elasticsearch with the AI you build on.
Step-by-step setup for Elasticsearch with a specific model, assistant or agent framework.
-
Elasticsearch + Claude
How to connect Elasticsearch to Claude
-
Elasticsearch + ChatGPT
How to connect Elasticsearch to ChatGPT
-
Elasticsearch + Claude Code
How to connect Elasticsearch to Claude Code
-
Elasticsearch + Muse
How to connect Elasticsearch to Muse
-
Elasticsearch + Grok Bot
How to connect Elasticsearch to Grok Bot
-
Elasticsearch + OpenAI Dots
How to connect Elasticsearch to OpenAI Dots
-
Elasticsearch + Claude Duet
How to connect Elasticsearch to Claude Duet
-
Elasticsearch + Hermes Agent
How to connect Elasticsearch to Hermes Agent
-
Elasticsearch + OpenClaw
How to connect Elasticsearch to OpenClaw
FAQ
Elasticsearch and Agent200, answered.
Who handles the Elasticsearch OAuth flow and the tokens?
Agent200. It runs the authorization, handles the callback on its own domain, stores the tokens and refreshes them. You do not build or maintain an OAuth integration for Elasticsearch.
Does my agent act as the end user?
Within what that user authorized, yes. Every request names an end user, and Agent200 uses only that user's Elasticsearch connection, never another user's. It cannot reach anything the user or Elasticsearch has not authorized.
Can I limit what my agent can do in Elasticsearch?
Yes. You choose which services, endpoints and authorization scopes are allowed in your Agent200 configuration, and the agent works only within them.