M
MCP Directory CURATED DIRECTORY
911 MCP servers indexed
中文
← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

Compare scores, permissions, risks, and fit in one decision-focused table.

DimensionKibanaMCP server to access and manage Kibana instances with natural languageMartinLoop MCP ServerAn independent control layer that gives AI coding agents budgets, brakes, and receipts
FMRS51 / 100 · D79 / 100 · B
Reliability6 / 2012 / 20
Security and permissions8 / 2018 / 20
Maintenance10 / 2016 / 20
Documentation14 / 2018 / 20
Setup experience13 / 2015 / 20
Best for
  • Teams using Kibana for log analysis, monitoring, and visualization
  • Users who want to manage Kibana resources within AI assistants like Claude
  • Developers integrating Elastic Stack workflows
  • Engineering teams scaling AI coding agents while controlling spend
  • Platform teams that need auditable, rollback-aware agent execution records
  • Organizations using multiple agents (Claude, Codex, Gemini) under one governed flow
Not for
  • Not for direct Elasticsearch data operations (a companion Elasticsearch MCP server exists)
  • Not an official Elastic product; community-maintained, not for mission-critical production use without support
  • Developers who just want a simple code-completion helper without run governance
  • Teams unwilling to accept local JSONL run records with HMAC signing
  • Environments without a supported adapter (Claude/Codex/Gemini CLIs, direct provider, or verifier-only)
Required permissions
  • Requires access to the Kibana server (KIBANA_URL)
  • Needs authentication credentials (API Key, username/password, or cookies) to perform operations
  • In HTTP mode, requires opening a network port (default 3000)
  • Read/write access to the configured repo root (writable scope restrictable via --allow-path/--deny-path)
  • Ability to invoke the chosen agent CLI (Claude/Codex/Gemini, etc.) and its underlying model account
  • Local disk writes for run records, receipts, and share outputs (share/run-receipt., etc.)
  • Execution of user-configured verifier commands (e.g. npm test)
Risks and side effects
  • Misconfiguration could lead to unauthorized access or data leakage
  • Executing API requests may modify or delete saved objects, risking data loss
  • SSL verification disablement (NODE_TLS_REJECT_UNAUTHORIZED=0) may expose to man-in-the-middle attacks
  • Community-maintained, no official support, updates may carry risks
  • Verifier commands are executed; poorly chosen verifier commands carry security risk despite preflight policy checks
  • Cost and token figures may be estimates (labeled with provenance) and should not be treated as settled accounting
  • Receipt integrity must be verified before use as trustworthy evidence; missing rollback evidence is flagged as EVIDENCE_BOUNDARY
  • Policy defaults come from martin.config.yaml and can be overridden by CLI flags; misconfiguration can loosen safety boundaries
Supported clientsClaude DesktopClaude Code, Codex, Gemini CLI, Cursor, VS Code, GitHub Copilot, Continue
Tools160