Skip to main content
mcpSource-backed

Elastic Agent Builder MCP Server for Claude

Official Elastic Agent Builder MCP server endpoint for connecting Claude, Cursor, VS Code, and other MCP clients to Elastic Agent Builder tools through Kibana with API-key scoped access to Elasticsearch indices and Agent Builder privileges.

by Elastic · submitted by oktofeesh1·added 2026-06-04·
Review first review before installing

Open the source and read safety notes before installing.

Citation facts

Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.

Source URLs
https://www.elastic.co/docs/explore-analyze/ai-features/agent-builder/mcp-server, https://github.com/JSONbored/awesome-claude/blob/main/content/mcp/elastic-agent-builder-mcp-server.mdx, https://www.elastic.co/
Safety notes
Elastic Agent Builder MCP executes with the scope assigned to the API key. Treat the API key as the effective permission boundary for every index, space, inference endpoint, and Agent Builder tool exposed to Claude., Do not use a broad administrator API key for exploratory chats. Elastic's docs recommend setting API key expiration dates and limiting access to only the indices the tools need to query., The example API key privileges include `read` and `view_index_metadata` for selected indices plus Kibana application privileges such as `feature_agentBuilder.read` and `feature_actions.read`. Keep those permissions as narrow as the workflow allows., Agent Builder tools can route AI clients into Elastic data exploration workflows. Require human review before using assistant-generated findings to change detections, alerts, response processes, dashboards, workflows, or production investigation decisions., If your Kibana deployment uses multiple spaces, verify the MCP URL includes the intended space path before connecting the client. A wrong space can expose the wrong tools, saved objects, or index access assumptions., `npx mcp-remote` is a local bridge process. Pin or review runtime dependencies when reproducibility or endpoint trust is required, and avoid running the bridge from untrusted project directories.
Privacy notes
Elastic Agent Builder MCP can expose log events, metrics, traces, security alerts, documents, index mappings, inference context, saved tool behavior, and Agent Builder outputs to the connected AI client., Index names, field names, mappings, document samples, query results, and investigation prompts can reveal internal service names, user identifiers, customer data, infrastructure details, secrets accidentally present in logs, or security investigation context., Store Elastic API keys outside prompts, shell history, committed MCP config, screenshots, tickets, and shared chat transcripts. Rotate keys after exposure and prefer short-lived keys for development., Claude transcripts, IDE logs, MCP client logs, terminal history, support bundles, and generated investigation notes may retain Elastic-derived data outside Elastic's normal access controls and retention policies., The MCP endpoint runs through Kibana. Review Elastic deployment access, Kibana space membership, API key scopes, and any external AI-client data retention policy before connecting regulated or customer-sensitive indices.
Author
Elastic
Submitted by
oktofeesh1
Claim status
unclaimed
Last verified
2026-06-04

Decision playbook

Review trust signals before you adopt

Signals are present but mixed. Use the checklist below to confirm the source and operational safety for your environment.

Compare context
Selected

0

Current score

78

Baseline

Delta

No baseline selected

No major trust-signal divergence detected in the current selection.

Source and provenance checks

Complete

Confirm ownership and provenance before trusting install instructions.

  • Source link availableRequired

    Open the canonical repository and verify ownership.

    Done
  • Source provenance statusRequired

    Marked as source-backed.

    Done
  • Metadata reviewed

    Registry metadata indicates a reviewed listing.

    Done

Safety and privacy checks

Complete

Validate risk disclosures before installation or API wiring.

  • Safety notes presentRequired

    Review the listed safety guidance before running commands.

    Done
  • Privacy notes presentRequired

    Review data handling notes before connecting accounts or secrets.

    Done
  • Trust level risk gateRequired

    Trust level does not block evaluation.

    Done

Package and install checks

Needs review

Check package metadata and artifact integrity signals.

  • Install payload available

    Install or copy payload is available for review.

    Done
  • Package verification flag

    No package verification flag provided.

    Pending
  • Checksum metadata

    No checksum provided for downloaded artifact.

    Pending

Compare-driven decision checks

Needs review

Use compare context to validate trade-offs before adoption.

  • Compare tray has multiple entries

    Add at least one more entry to compare trust differences.

    Pending
  • Baseline comparison available

    No baseline peer selected yet.

    Pending
  • Diverging trust signals identified

    No major trust-signal divergence found.

    Pending

Setup at a glance

CLI install

Copy-ready — paste the snippet to get started.

20 minutes

Adoption plan

Balanced adoption plan

Current risk score 16/100. Use staged verification before broader rollout.

Risk 16

Pre-adoption checks

Validate source and review signals before any execution.

  • Confirm source provenanceRequired

    Source URL/provenance metadata is present.

    Done
  • Confirm metadata review state

    Listing has review metadata.

    Done
  • Verify install payload

    Install/config payload exists and can be inspected.

    Done

Security checks

Confirm safety, privacy, and package integrity signals.

  • Review safety notesRequired

    Safety notes are present.

    Done
  • Review privacy notesRequired

    Privacy notes are present.

    Done
  • Verify package integrity metadata

    No package verification/checksum metadata.

    Pending

Rollout

Adopt in controlled steps based on the selected plan.

  • Run in isolated sandbox firstRequired

    Use a constrained sandbox and observe behavior across multiple tasks.

    Pending
  • Roll out graduallyRequired

    Roll out to a small cohort before wider usage.

    Pending
  • Set monitoring and fallback

    Define rollback path and monitor errors after adoption.

    Pending

Evidence readiness

Evidence readiness matrix · balanced

Required evidence gates are covered (5/6 signals complete).

Risk 15

Source provenance

Present

Source repository/provenance is listed.

Required in this preset

Metadata review

Present

Review metadata is present.

Required in this preset

Safety notes

Present

Safety notes are present.

Required in this preset

Privacy notes

Present

Privacy notes are present.

Optional in this preset

Package integrity

Missing

Package integrity metadata is missing.

Optional in this preset

Install payload

Present

Install payload is available.

Required in this preset

Required evidence gates are covered for this preset.

Decision timeline

Decision timeline · balanced

5/6 steps complete with no blocking gaps for this preset.

Risk 14

triage

Confirm source provenanceRequired

Source/provenance metadata is available.

Done

triage

Check metadata review statusRequired

Review metadata is available.

Done

verify

Review safety notesRequired

Safety notes are available.

Done

verify

Review privacy notes

Privacy notes are available.

Done

verify

Validate package integrity metadata

Package integrity metadata is missing.

Pending

rollout

Verify install payload and commandsRequired

Install payload is available.

Done

No required blockers for this timeline preset.

Prerequisite readiness

Prerequisite readiness

6 prerequisites to line up before setup. Have accounts and credentials ready first. Includes a review or approval gate.

0/6 ready
Account & credentials1Install & runtime4Review & approval120 minutes

Safety & privacy surface

Safety & privacy surface

6 safety and 5 privacy notes across 6 risk areas. Review closely: credentials & tokens, permissions & scopes, network access.

6 areas
  • SafetyCredentials & tokensElastic Agent Builder MCP executes with the scope assigned to the API key. Treat the API key as the effective permission boundary for every index, space, inference endpoint, and Agent Builder tool exposed to Claude.
  • SafetyCredentials & tokensDo not use a broad administrator API key for exploratory chats. Elastic's docs recommend setting API key expiration dates and limiting access to only the indices the tools need to query.
  • SafetyCredentials & tokensThe example API key privileges include `read` and `view_index_metadata` for selected indices plus Kibana application privileges such as `feature_agentBuilder.read` and `feature_actions.read`. Keep those permissions as narrow as the workflow allows.
  • SafetyExecution & processesAgent Builder tools can route AI clients into Elastic data exploration workflows. Require human review before using assistant-generated findings to change detections, alerts, response processes, dashboards, workflows, or production investigation decisions.
  • SafetyLocal filesIf your Kibana deployment uses multiple spaces, verify the MCP URL includes the intended space path before connecting the client. A wrong space can expose the wrong tools, saved objects, or index access assumptions.
  • SafetyNetwork access`npx mcp-remote` is a local bridge process. Pin or review runtime dependencies when reproducibility or endpoint trust is required, and avoid running the bridge from untrusted project directories.
  • PrivacyData retentionElastic Agent Builder MCP can expose log events, metrics, traces, security alerts, documents, index mappings, inference context, saved tool behavior, and Agent Builder outputs to the connected AI client.
  • PrivacyCredentials & tokensIndex names, field names, mappings, document samples, query results, and investigation prompts can reveal internal service names, user identifiers, customer data, infrastructure details, secrets accidentally present in logs, or security investigation context.
  • PrivacyCredentials & tokensStore Elastic API keys outside prompts, shell history, committed MCP config, screenshots, tickets, and shared chat transcripts. Rotate keys after exposure and prefer short-lived keys for development.
  • PrivacyPermissions & scopesClaude transcripts, IDE logs, MCP client logs, terminal history, support bundles, and generated investigation notes may retain Elastic-derived data outside Elastic's normal access controls and retention policies.
  • PrivacyCredentials & tokensThe MCP endpoint runs through Kibana. Review Elastic deployment access, Kibana space membership, API key scopes, and any external AI-client data retention policy before connecting regulated or customer-sensitive indices.

Safety notes

  • Elastic Agent Builder MCP executes with the scope assigned to the API key. Treat the API key as the effective permission boundary for every index, space, inference endpoint, and Agent Builder tool exposed to Claude.
  • Do not use a broad administrator API key for exploratory chats. Elastic's docs recommend setting API key expiration dates and limiting access to only the indices the tools need to query.
  • The example API key privileges include `read` and `view_index_metadata` for selected indices plus Kibana application privileges such as `feature_agentBuilder.read` and `feature_actions.read`. Keep those permissions as narrow as the workflow allows.
  • Agent Builder tools can route AI clients into Elastic data exploration workflows. Require human review before using assistant-generated findings to change detections, alerts, response processes, dashboards, workflows, or production investigation decisions.
  • If your Kibana deployment uses multiple spaces, verify the MCP URL includes the intended space path before connecting the client. A wrong space can expose the wrong tools, saved objects, or index access assumptions.
  • `npx mcp-remote` is a local bridge process. Pin or review runtime dependencies when reproducibility or endpoint trust is required, and avoid running the bridge from untrusted project directories.

Privacy notes

  • Elastic Agent Builder MCP can expose log events, metrics, traces, security alerts, documents, index mappings, inference context, saved tool behavior, and Agent Builder outputs to the connected AI client.
  • Index names, field names, mappings, document samples, query results, and investigation prompts can reveal internal service names, user identifiers, customer data, infrastructure details, secrets accidentally present in logs, or security investigation context.
  • Store Elastic API keys outside prompts, shell history, committed MCP config, screenshots, tickets, and shared chat transcripts. Rotate keys after exposure and prefer short-lived keys for development.
  • Claude transcripts, IDE logs, MCP client logs, terminal history, support bundles, and generated investigation notes may retain Elastic-derived data outside Elastic's normal access controls and retention policies.
  • The MCP endpoint runs through Kibana. Review Elastic deployment access, Kibana space membership, API key scopes, and any external AI-client data retention policy before connecting regulated or customer-sensitive indices.

Prerequisites

  • Elastic deployment with Kibana and Elastic Agent Builder available.
  • Kibana URL for the target deployment; custom Kibana spaces use `/s/{SPACE_NAME}/api/agent_builder/mcp`.
  • MCP-capable client such as Claude Desktop, Claude Code, Cursor, VS Code, or another client that can run `npx mcp-remote`.
  • Node.js and npm available for the documented `npx mcp-remote` bridge.
  • Elastic API key with Kibana application privileges for Agent Builder and only the Elasticsearch index privileges the assistant should use.
  • Index patterns, Kibana space, and Agent Builder tools reviewed before exposing them to an external AI client.

Schema details

Install type
cli
Troubleshooting
No
Collection metadata
Estimated setup
20 minutes
Difficulty
intermediate
Tool listing metadata
Full copyable content
{
  "mcpServers": {
    "elastic-agent-builder": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "${KIBANA_URL}/api/agent_builder/mcp",
        "--header",
        "Authorization:${AUTH_HEADER}"
      ],
      "env": {
        "KIBANA_URL": "${KIBANA_URL}",
        "AUTH_HEADER": "ApiKey ${API_KEY}"
      }
    }
  }
}

About this resource

Content

Elastic Agent Builder MCP Server is Elastic's official MCP endpoint for connecting external AI clients to Elastic Agent Builder tools. Instead of running a standalone Elasticsearch MCP package, you connect the client to the Kibana endpoint for the deployment and authenticate with an Elastic API key scoped to the exact indices, Kibana space, and Agent Builder privileges the assistant should use.

Use it when Claude needs a governed bridge into Elastic Agent Builder workflows for logs, metrics, search, observability, security, or document exploration. The useful part is also the risky part: the assistant sees whatever the API key and configured Agent Builder tools can access, so the right default is a short-lived, least-privilege API key tied to a narrow space and index pattern.

Features

  • Official Elastic Agent Builder MCP endpoint documented by Elastic.
  • Standard endpoint at {KIBANA_URL}/api/agent_builder/mcp.
  • Custom Kibana space endpoint at {KIBANA_URL}/s/{SPACE_NAME}/api/agent_builder/mcp.
  • Setup pattern for MCP clients such as Claude Desktop, Cursor, VS Code, and similar clients.
  • Uses mcp-remote to bridge local MCP clients to the Kibana HTTP endpoint.
  • API key authentication through an Authorization: ApiKey ... header.
  • Kibana application privilege requirements for Elastic Agent Builder.
  • Elasticsearch index privilege scoping through role descriptors.
  • Support for narrow production API keys that expose only selected index patterns such as logs-* or metrics-*.
  • Explicit docs guidance to set API key expiration dates and rotate keys.
  • Works with the Agent Builder tools configured in the target Elastic deployment and Kibana space.

Use Cases

  • Let Claude inspect approved Elastic logs or metrics indexes during incident triage without giving it broad cluster access.
  • Expose a narrow Agent Builder toolset for support investigations in one Kibana space.
  • Query selected observability indices and summarize recurring errors, affected services, or recent patterns.
  • Use an API key scoped to logs-* and metrics-* while keeping sensitive security or customer-data indices out of the assistant's reach.
  • Test Agent Builder tools from Claude Desktop, Cursor, or VS Code before publishing them to a wider team.
  • Reproduce a 403 by checking whether the API key includes the required Kibana Agent Builder application privileges.

Installation

Default Kibana space

Set the Kibana URL and API key:

export KIBANA_URL="https://your-deployment.kb.us-central1.gcp.cloud.es.io"
export API_KEY="your-api-key"

Then configure the MCP client with mcp-remote:

{
  "mcpServers": {
    "elastic-agent-builder": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "${KIBANA_URL}/api/agent_builder/mcp",
        "--header",
        "Authorization:${AUTH_HEADER}"
      ],
      "env": {
        "KIBANA_URL": "${KIBANA_URL}",
        "AUTH_HEADER": "ApiKey ${API_KEY}"
      }
    }
  }
}

Custom Kibana space

For a non-default Kibana space, include the space segment:

{
  "mcpServers": {
    "elastic-agent-builder": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "${KIBANA_URL}/s/${SPACE_NAME}/api/agent_builder/mcp",
        "--header",
        "Authorization:${AUTH_HEADER}"
      ],
      "env": {
        "KIBANA_URL": "${KIBANA_URL}",
        "SPACE_NAME": "default",
        "AUTH_HEADER": "ApiKey ${API_KEY}"
      }
    }
  }
}

API key shape

Elastic's docs show an API key role descriptor with cluster access for inference monitoring, index-level read and view_index_metadata, and Kibana application privileges for Agent Builder. For production, restrict index names to the smallest useful patterns:

{
  "indices": [
    {
      "names": ["logs-*", "metrics-*"],
      "privileges": ["read", "view_index_metadata"]
    }
  ],
  "applications": [
    {
      "application": "kibana-.kibana",
      "privileges": ["feature_agentBuilder.read", "feature_actions.read"],
      "resources": ["space:default"]
    }
  ]
}

Examples

Inspect approved logs

Use Elastic Agent Builder MCP to summarize recurring errors in the approved logs-* indices from the last 30 minutes. Do not change detections, dashboards, or workflows.

Verify MCP permissions

Before querying data, confirm which Kibana space and index patterns this Elastic MCP connection can access.

Debug 403 access

Use the Elastic MCP setup context to explain why the current API key might receive 403 Forbidden when connecting to the Agent Builder endpoint.

Keep scope narrow

Only use Elastic Agent Builder MCP tools that read logs and metrics. Avoid security, customer-data, or broad wildcard index queries.

Source Notes

  • Elastic's official docs describe the MCP server as a standardized interface for external clients to access Elastic Agent Builder tools.
  • Elastic documents the endpoint as {KIBANA_URL}/api/agent_builder/mcp and the custom-space variant as {KIBANA_URL}/s/{SPACE_NAME}/api/agent_builder/mcp.
  • Elastic's client example uses npx mcp-remote with an API key authorization header.
  • Elastic documents required Kibana application privileges for Agent Builder and notes that missing feature_agentBuilder.read causes a 403 Forbidden connection failure.
  • Elastic's best practices recommend API key expiration dates and limiting API keys to only the indices the tools need to access.

Duplicate Check

Checked current upstream/main, open PR titles, open PR changed files, source URLs, and content files for Elastic Agent Builder MCP, Elastic MCP, Elasticsearch MCP, elastic-agent-builder-mcp-server, /api/agent_builder/mcp, and elastic.co/docs/explore-analyze/ai-features/agent-builder/mcp-server. Existing content mentions Elastic only in broad infrastructure, search, or observability examples; there is no dedicated Elastic Agent Builder MCP Server entry, source URL duplicate, or open content PR for this server.

Editorial Disclosure

Elastic is a commercial search, observability, and security platform with open-source components, but this listing is not sponsored, paid, affiliate-backed, or submitted by Elastic. Use Elastic's current Agent Builder docs, Kibana space model, API key privileges, and deployment policies as the source of truth before connecting sensitive indices to any AI client.

Source citations

Add this badge to your README

Show that Elastic Agent Builder MCP Server for Claude is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.

Listed on HeyClaude
[![Listed on HeyClaude](https://heyclau.de/badge/mcp/elastic-agent-builder-mcp-server.svg)](https://heyclau.de/entry/mcp/elastic-agent-builder-mcp-server)

How it compares

Elastic Agent Builder MCP Server for Claude side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.

2 trust signals differ across this comparison (Source provenance, Submitter).

Field

Official Elastic Agent Builder MCP server endpoint for connecting Claude, Cursor, VS Code, and other MCP clients to Elastic Agent Builder tools through Kibana with API-key scoped access to Elasticsearch indices and Agent Builder privileges.

Open dossier

Connect Claude to your Elasticsearch cluster — search indices, inspect mappings, run ES|QL, and check shard health — with Elastic's official Model Context Protocol server.

Open dossier

Connect Claude to Meilisearch — manage indexes, add and search documents, tune settings, and monitor tasks — with Meilisearch's official Model Context Protocol server.

Open dossier

Connect Claude to BorealHost's MCP server for hosting and infrastructure management — 47 tools spanning servers, domains, DNS, SSL, and deployments. Add it remotely with claude mcp add --transport http, or run it locally over stdio via pip install borealhost-mcp with a BOREALHOST_API_KEY.

Open dossier
Next steps
Trust
Review statusReviewedMaintainer reviewedReviewedMaintainer reviewedReviewedMaintainer reviewedReviewedMaintainer reviewed
Package trustPackage not verifiedPackage not verifiedPackage not verifiedPackage not verified
Source provenanceDiffersSource-backedSource-backedSource-backedSubmission linkedSource submission
SubmitterDiffersoktofeesh1kiannidev
Install riskReview firstReview firstReview firstReview first
Notes Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓
Brand
Categorymcpmcpmcpmcp
SourceSource-backedSource-backedSource-backedSource-backed
AuthorElasticElasticMeilisearchBorealHost
Added2026-06-042026-06-172026-06-172026-06-14
Platforms
Harness
Source repo
Safety notesElastic Agent Builder MCP executes with the scope assigned to the API key. Treat the API key as the effective permission boundary for every index, space, inference endpoint, and Agent Builder tool exposed to Claude. Do not use a broad administrator API key for exploratory chats. Elastic's docs recommend setting API key expiration dates and limiting access to only the indices the tools need to query. The example API key privileges include `read` and `view_index_metadata` for selected indices plus Kibana application privileges such as `feature_agentBuilder.read` and `feature_actions.read`. Keep those permissions as narrow as the workflow allows. Agent Builder tools can route AI clients into Elastic data exploration workflows. Require human review before using assistant-generated findings to change detections, alerts, response processes, dashboards, workflows, or production investigation decisions. If your Kibana deployment uses multiple spaces, verify the MCP URL includes the intended space path before connecting the client. A wrong space can expose the wrong tools, saved objects, or index access assumptions. `npx mcp-remote` is a local bridge process. Pin or review runtime dependencies when reproducibility or endpoint trust is required, and avoid running the bridge from untrusted project directories.Search, ES|QL, and shard tools run live read queries against the configured cluster; a broad or expensive query can add load. Scope the Elasticsearch API key to least privilege (read-only on the indices Claude should see) before connecting.Tools create and delete indexes and documents and rotate API keys — scope the key and confirm destructive actions. Settings and index deletes change live search behavior; review before running them through Claude.Hosting management tools can provision, reconfigure, or destroy servers and DNS records. BOREALHOST_API_KEY grants account-level access; store it as an environment variable, not in chat. Review each destructive tool call before approval in automated agent workflows. Remote HTTP mode may expose different tool subsets than local stdio; verify capabilities in docs.
Privacy notesElastic Agent Builder MCP can expose log events, metrics, traces, security alerts, documents, index mappings, inference context, saved tool behavior, and Agent Builder outputs to the connected AI client. Index names, field names, mappings, document samples, query results, and investigation prompts can reveal internal service names, user identifiers, customer data, infrastructure details, secrets accidentally present in logs, or security investigation context. Store Elastic API keys outside prompts, shell history, committed MCP config, screenshots, tickets, and shared chat transcripts. Rotate keys after exposure and prefer short-lived keys for development. Claude transcripts, IDE logs, MCP client logs, terminal history, support bundles, and generated investigation notes may retain Elastic-derived data outside Elastic's normal access controls and retention policies. The MCP endpoint runs through Kibana. Review Elastic deployment access, Kibana space membership, API key scopes, and any external AI-client data retention policy before connecting regulated or customer-sensitive indices.Index data, field mappings, and query results enter the MCP client context and the model's prompt. ES_URL and ES_API_KEY are secrets — store them in the client config or environment, never in shared repositories.Indexed documents and search results enter the MCP client context and the model's prompt. MEILI_HTTP_ADDR and MEILI_MASTER_KEY are secrets — keep them in the client config or environment.Server hostnames, IP addresses, and account metadata returned by tools may be sensitive infrastructure data. API keys and OAuth-like session tokens must not be committed to repositories or shared connectors. Support logs should reference resource IDs, not full customer site contents or credentials.
Prerequisites
  • Elastic deployment with Kibana and Elastic Agent Builder available.
  • Kibana URL for the target deployment; custom Kibana spaces use `/s/{SPACE_NAME}/api/agent_builder/mcp`.
  • MCP-capable client such as Claude Desktop, Claude Code, Cursor, VS Code, or another client that can run `npx mcp-remote`.
  • Node.js and npm available for the documented `npx mcp-remote` bridge.
  • Docker installed (the server is distributed as the docker.elastic.co/mcp/elasticsearch image).
  • An Elasticsearch cluster URL (ES_URL) you can reach.
  • An Elasticsearch API key (ES_API_KEY) or username/password (ES_USERNAME + ES_PASSWORD).
  • An MCP client such as Claude Code or Claude Desktop.
  • A reachable Meilisearch instance URL (MEILI_HTTP_ADDR).
  • A Meilisearch master or API key (MEILI_MASTER_KEY) when your instance requires authentication.
  • uv (uvx) or pip to run meilisearch-mcp, or Docker (getmeili/meilisearch-mcp).
  • An MCP client such as Claude Code or Claude Desktop.
  • Python 3.10+ and pip for local stdio install via pip install borealhost-mcp.
  • Optional BorealHost account and BOREALHOST_API_KEY for account-specific hosting tools.
  • Claude Code or Claude Desktop with MCP support for stdio, or Connectors for remote HTTP.
  • Understanding that some hosting tools may create, modify, or delete infrastructure resources.
Install
npx mcp-remote ${KIBANA_URL}/api/agent_builder/mcp --header 'Authorization:ApiKey ${API_KEY}'
claude mcp add elasticsearch -- docker run -i --rm -e ES_URL=<your-cluster-url> -e ES_API_KEY=<your-api-key> docker.elastic.co/mcp/elasticsearch stdio
claude mcp add meilisearch -e MEILI_HTTP_ADDR=<your-meili-url> -e MEILI_MASTER_KEY=<your-key> -- uvx -n meilisearch-mcp
claude mcp add --transport http borealhost https://borealhost.ai/mcp/
Config
{
  "mcpServers": {
    "elastic-agent-builder": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "${KIBANA_URL}/s/${SPACE_NAME}/api/agent_builder/mcp",
        "--header",
        "Authorization:${AUTH_HEADER}"
      ],
      "env": {
        "KIBANA_URL": "${KIBANA_URL}",
        "SPACE_NAME": "default",
        "AUTH_HEADER": "ApiKey ${API_KEY}"
      }
    }
  }
}
{
  "mcpServers": {
    "elasticsearch-mcp-server": {
      "command": "docker",
      "args": [
        "run", "-i", "--rm",
        "-e", "ES_URL", "-e", "ES_API_KEY",
        "docker.elastic.co/mcp/elasticsearch", "stdio"
      ],
      "env": {
        "ES_URL": "<elasticsearch-cluster-url>",
        "ES_API_KEY": "<elasticsearch-api-key>"
      }
    }
  }
}
{
  "mcpServers": {
    "meilisearch": {
      "command": "uvx",
      "args": ["-n", "meilisearch-mcp"],
      "env": {
        "MEILI_HTTP_ADDR": "<your-meili-url>",
        "MEILI_MASTER_KEY": "<your-key>"
      }
    }
  }
}
{
  "mcpServers": {
    "borealhost": {
      "command": "borealhost-mcp",
      "args": [],
      "env": {
        "BOREALHOST_API_KEY": "${BOREALHOST_API_KEY}"
      },
      "type": "stdio"
    }
  }
}
Citations
ClaimUnclaimedUnclaimedUnclaimedUnclaimed
Open 4 picks in the interactive comparison tool

Related guides

Signals

Loading live community signals…

More like this, weekly

A short, calm digest of reviewed Claude resources. Unsubscribe any time.