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 languageGitHub MCP ServerGitHub's official MCP server for managing repos, issues, PRs, and workflows via natural language
FMRS51 / 100 · D76 / 100 · B
Reliability6 / 2013 / 20
Security and permissions8 / 2014 / 20
Maintenance10 / 2018 / 20
Documentation14 / 2017 / 20
Setup experience13 / 2014 / 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
  • Teams that want an AI assistant to directly operate on GitHub repos and collaboration workflows
  • Users already in the GitHub Copilot ecosystem who want a zero-deployment remote option
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
  • Scenarios where you don't want the assistant to have write access to repos (enable only read-only toolsets)
  • Environments with strict network isolation for private repos that can't reach the official remote endpoint
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)
  • A personal access token (PAT) or OAuth App token; effective scope depends on the token's own permissions
  • Enabling toolsets like actions/issues/pull_requests grants write access — request tokens on a least-privilege basis
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
  • Write toolsets (creating/merging PRs, triggering workflows) can cause accidental changes if the token is overscoped — try a read-only toolset first
  • In hosted mode, credentials travel via the Authorization header — make sure the client-to-api.githubcopilot.com connection is trusted
Supported clientsClaude DesktopClaude Desktop, Claude Code, VS Code, Cursor, Windsurf, JetBrains IDEs, Zed, Amp
Tools1615