mcp-config

mcp-config is a command for Claude Code from ch-bas/kibana-plugin-helper. It costs 30 tokens per session (989 once invoked), scanned A, original, MIT.

A command guide for generating a .mcp.json file that connects Claude Code to Elasticsearch and Kibana servers. Elasticsearch stores and searches data, while Kibana provides a web interface for exploring and monitoring it.

In plain words
What is it for?
Use it to configure live Elasticsearch, Kibana, or Kibana Agent Builder access while developing plugins.
Why use it?
It avoids manually assembling server URLs, authentication settings, environment variables, and project or global configuration.

Command for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: reads .claude/ paths; mentions Claude Code.

Part of the kibana-plugin-helper plugin — 1 skill, 8 commands shipped together

Good fit Use it to configure live Elasticsearch, Kibana, or Kibana Agent Builder access while developing plugins.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/ch-bas/kibana-plugin-helper/mcp-config
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Clone the repo
git clone --depth 1 https://github.com/ch-bas/kibana-plugin-helper

Made for: Claude Code.

Or install kibana-plugin-helper, the plugin that ships this one along with the rest of its 1 skill, 8 commands.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for mcp-config

README.md
[![agentmods](https://agentmods.dev/badge/commands/ch-bas/kibana-plugin-helper/mcp-config.svg)](https://agentmods.dev/commands/ch-bas/kibana-plugin-helper/mcp-config)
Your own site
<a href="https://agentmods.dev/commands/ch-bas/kibana-plugin-helper/mcp-config"><img src="https://agentmods.dev/badge/commands/ch-bas/kibana-plugin-helper/mcp-config.svg" alt="Measured on agentmods" height="20"></a>
Per session 30 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 989 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00030 $0.00989
Opus 5 $0.00015 $0.00495
Sonnet 5 $0.00006 $0.00198
Haiku 4.5 $0.00003 $0.00099

Measured 8d ago against content hash 4ecf92519490, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

mcp-config scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 8d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

commands/mcp-config.md · 130 lines

How it starts

The opening of the file, as written. The whole thing — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Generate MCP Configuration

Set up MCP server connections so Claude Code has live access to your Elasticsearch cluster and Kibana instance while developing plugins. Ask the user for:

  1. Which MCP servers? Options:

    • Elasticsearch MCP only (recommended minimum)
    • Elasticsearch + Kibana MCP (recommended for full-stack plugin dev)
    • Elasticsearch + Kibana Agent Builder MCP (for Kibana 9.2+ / Serverless)
  2. Elasticsearch connection:

    • URL (default: https://localhost:9200)
    • Auth method: API key, username/password, or cloud ID
    • SSL verification (default: true)
  3. Kibana connection (if selected):

    • URL (default: https://localhost:5601)
    • Auth method: API key or username/password
    • For Agent Builder: Kibana Cloud URL
  4. Docker or local?

    • Docker (recommended — no local install needed)
    • Local Node.js (for Kibana MCP community server)
  5. Scope:

    • Project-level (.mcp.json in project root)
    • Global (~/.claude/mcp.json)

Generation Steps

  1. Collect all connection details
  2. Generate .mcp.json with the selected MCP servers
  3. Generate a .env file for secrets (if not using env vars already)
  4. Add .env to .gitignore if not already present
  5. Test the connection by describing how to verify with claude /mcp

Important Rules

  • Never hardcode API keys or passwords in .mcp.json — always use environment variable references
  • Always recommend read-only API keys for development
  • Remind the user to add .env to .gitignore
  • For Docker-based ES MCP, use --network host when ES runs on localhost
  • For the Kibana community MCP server, verify the user has cloned and installed it
  • Test connectivity: after generating, tell the user to run claude /mcp to verify servers are connected
  • Recommend starting with ES MCP alone — it covers 80% of use cases

Template: ES MCP Only (Docker)

{
  "mcpServers": {
    "elasticsearch": {
      "command": "docker",
      "args": [
        "run", "--rm", "-i",
        "--network", "host",
        "-e", "ES_URL",
        "-e", "ES_API_KEY",
        "docker.elastic.co/mcp/elasticsearch"
      ],
      "env": {
        "ES_URL": "${ELASTICSEARCH_URL}",
        "ES_API_KEY": "${ELASTICSEARCH_API_KEY}"
      }
    }
  }
}

Read the full file on GitHub · 130 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 8d ago First seen · 130 lines · 30 tokens per session scan A 4ecf92519490

Subscribe to this mod's changes

mcp-config is a command published in the GitHub repository ch-bas/kibana-plugin-helper (3 stars, last pushed 7mo ago), licensed MIT. It adds 30 tokens to every session and 989 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.