How to Use the Elastic Enterprise Search MCP in Claude Code

Q: How do I search Elastic Enterprise Search engines from Claude Code?

Run the search tool directly from your terminal session through Claude Code. The CLI agent queries your specified engine and formats the resulting JSON documents directly in your terminal output.

Q: How do I install the Elastic Enterprise Search MCP Server in Claude Code?

Run claude mcp add --transport http elastic-enterprise-search-mcp -- in your terminal. This adds the server configuration directly to your /.claude.json file.

Q: Can I monitor query click-through rates from the command line?

Yes. The analytics tool retrieves query performance metrics and search logs. Claude Code parses this data to show you click-through rates and failed queries directly in your terminal.

Run Elastic Enterprise Search queries, index documents, and monitor analytics directly from your terminal with Claude Code.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Elastic Enterprise Search MCP to Claude Code

Create your Vinkius account to connect Elastic Enterprise Search to Claude Code and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup Elastic Enterprise Search with Claude Code

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Query and inspect Elastic indices from the terminal

The `search` tool executes raw document queries directly from your shell sessions. Claude Code pipes these search results into your terminal, allowing you to grep, filter, or export the JSON payloads without opening a browser window or writing a custom curl command. You can also run `list_documents` to dump and inspect indexed records in an engine. This makes it easy to verify that your document ingestion scripts are mapping fields correctly during terminal-based debugging.

Run terminal-based indexing jobs using this MCP Server

The `index_documents` tool ingests JSON payloads directly from your local shell environment or pipeline. You can pipe raw JSON files or API outputs straight into Claude Code and have it index them into specific engines. It verifies schema alignment before executing the write operation. To ensure you are writing to the correct destination, your terminal agent uses `list_engines` to discover active engines. It prevents indexing into non-existent endpoints by verifying the target configuration first.

Monitor search analytics from command-line sessions

The `analytics` tool pulls search performance metrics and query logs directly into your terminal. Claude Code parses these metrics to show you top queries, click-through rates, and error frequencies. It helps you monitor search health during deployment cycles. By combining analytics with `get_engine`, you can inspect engine status and performance metrics side-by-side. This keeps your search operations visible and manageable without leaving your SSH session or terminal multiplexer.

Setup guide

Set up Elastic Enterprise Search MCP in Claude Code

Prerequisites

Claude Code CLI installed (npm install -g @anthropic-ai/claude-code)
Active Vinkius subscription with a valid endpoint token

1

Run the add command

Open your terminal and run the command shown on the right. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com. Use --scope user to make it available across all projects.
2

Verify the connection

Start a Claude Code session and type /mcp to list connected servers. You should see elastic-enterprise-search-mcp with a green status indicator.
3

Start using tools

Ask Claude Code something like "Check my latest Elastic Enterprise Search transactions." It will automatically discover and invoke the available Elastic Enterprise Search tools.

Terminal

claude mcp add --transport http elastic-enterprise-search-mcp https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp

Get your connection token →

Prerequisites

Claude Code CLI installed
Active Vinkius subscription with a valid endpoint token

1

Open the config file

Create or edit .mcp.json in your project root for project-level scope, or ~/.claude.json for user-level scope.
2

Add the Elastic Enterprise Search MCP

Paste the JSON snippet shown on the right into the mcpServers object. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com.
3

Restart Claude Code

Start a new Claude Code session. Type /mcp to confirm the server is connected. The tools will be automatically available in your conversation.

.mcp.json

{
  "mcpServers": {
    "elastic-enterprise-search-mcp": {
      "type": "url",
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Elastic Enterprise Search. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect Elastic Enterprise Search now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about Elastic Enterprise Search MCP in Claude Code

Run the `search` tool directly from your terminal session through Claude Code. The CLI agent queries your specified engine and formats the resulting JSON documents directly in your terminal output.

Yes. Claude Code can read local JSON files, validate them against your schema, and call `index_documents` to ingest them into your Elastic Enterprise Search engine.

Run `claude mcp add --transport http elastic-enterprise-search-mcp -- ` in your terminal. This adds the server configuration directly to your `~/.claude.json` file.

Yes. The `analytics` tool retrieves query performance metrics and search logs. Claude Code parses this data to show you click-through rates and failed queries directly in your terminal.

The server runs in an isolated, short-lived V8 sandbox that processes requests in memory without disk persistence. Your Elastic credentials are never exposed to the terminal environment, keeping your indexed documents and analytics logs secure.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript