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.

DimensionDruid MCP ServerA comprehensive MCP server for Apache Druid cluster management and analyticsMCP Toolbox for DatabasesGoogle's official database MCP toolbox — define AI-accessible database tools via config
FMRS55 / 100 · C74 / 100 · B
Reliability10 / 2013 / 20
Security and permissions8 / 2013 / 20
Maintenance12 / 2017 / 20
Documentation13 / 2016 / 20
Setup experience12 / 2015 / 20
Best for
  • Data analysts and engineers who want to query and explore Apache Druid data via AI assistants like Claude, ChatGPT, or Gemini using natural language.
  • Teams looking to automate or streamline Druid cluster management tasks such as monitoring tasks, compaction, retention rules, and ingestion.
  • Developers integrating MCP clients via supported transports (STDIO, Streamable HTTP) looking for a standard 'out-of-the-box' server to interact with Druid.
  • Users who want a conversational data interface in a local desktop application such as Ypipe.
  • Teams that want precise control over which database operations an AI can perform, rather than open arbitrary SQL execution
  • Scenarios needing a unified MCP setup across multiple database engines
Not for
  • Not for latency-sensitive real-time data operations when MCP session overhead is unacceptable.
  • Not for headless, non-interactive scenarios where MCP protocol abstraction is unnecessary.
  • Not for users who require deep, custom Druid API capabilities or complex workflows that are not exposed through the MCP.
  • Not for those looking for a server to interoperate with cloud-hosted services such as Imply Polaris.
  • Lightweight cases that just want to run a few ad-hoc SQL queries without maintaining a tools.yaml config (a simpler single-database MCP may be a better fit)
Required permissions
  • Must be provided with URLs for Druid Router (required) and Coordinator (recommended) via environment variables.
  • Optionally provide Druid username and password for authentication via HTTP Basic.
  • For HTTP transports, OAuth2 is enabled by default and requires clients to present a valid Bearer token.
  • Varying permissions are required for admin operations depending on which Spring profiles are active (`ops`, `permissions`, `health`).
  • Read access to Druid system tables/catalog and data access depending on the scope of queries.
  • Database credentials (username/password/connection string) are supplied via env vars or config
  • A tool's actual permission is whatever SQL statement is defined in tools.yaml — designed for least privilege, but misconfiguration can still over-expose access
Risks and side effects
  • Risk of unintentional data deletion or modification when the `ops` profile is active and tokens are compromised, as `manageDatasourceOrSegment` allows permanently dropping datasources.
  • Using SSL with disabled certificate verification (`DRUID_SSL_SKIP_VERIFICATION=true`) can expose connections to man-in-the-middle attacks.
  • Exposing sensitive cluster metadata and query results to AI assistants may lead to data leakage.
  • The `permissions` tools can modify users, roles, and authorization policies when proper permissions are held.
  • Because tools are activated on-demand based on Spring profiles, there is a risk of misconfiguration if the required profiles are not activated correctly.
  • If tools.yaml defines SQL statements that allow unconstrained writes or deletes, the AI could accidentally modify data
  • The prebuilt toolsets (--prebuilt) favor convenience and may expose broader query capability than a specific business actually needs — use a custom tools.yaml in production
Supported clientsClaude Desktop, Generic MCP ClientClaude Code, Gemini CLI, Zed, Antigravity
Tools290