Elasticsearch (local)
BetaQueries Elasticsearch indices in natural language, so whatever the indices hold becomes readable by the agent.
- Developer Tools
- Local
- Runs
- On the developer's Mac
- Launched with
- Docker
- Platform
- macOS
- Publisher
- Docker
How it works
Every agent request passes through Ferentin policy before it reaches Elasticsearch (local).
It runs on the developer's Mac and talks to the AI client over stdio, so no network gateway sees it. Developers launch it with docker run -i --rm mcp/elasticsearch.
Ferentin's endpoint agent finds Elasticsearch (local) in the MCP configuration of AI clients on managed Macs. An administrator adds it once from the local MCP catalog for every managed Mac that launches it this way. Each of its tools starts unvetted until it is approved. Ferentin records every tool call.
- AI agentAsks for something
- Ferentin policies
- Elasticsearch (local) MCP serverRuns on the developer's Mac
- Governed resultChecked, logged, returned
About Elasticsearch (local)
Queries Elasticsearch indices in natural language, so whatever the indices hold becomes readable by the agent.
Frequently asked about Elasticsearch (local)
- How do I connect Elasticsearch (local) to Ferentin?
- Enroll your Macs with the Ferentin endpoint agent, then add Elasticsearch (local) from the local MCP catalog in the Ferentin admin console. Every managed Mac that launches it the way the catalog names it is covered, and each of its tools starts unvetted until you approve it.
- Is the Elasticsearch (local) integration generally available?
- The Elasticsearch (local) integration is currently beta on Ferentin.
Related integrations
3
Brave Search (local)
Searches the web, images, news and video through the Brave Search API. Every query goes to Brave.
Puppeteer (local)
Browser automation and scraping with Puppeteer, run as a container.
Redis (local)
Read and write access to a Redis database, run as a container.