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.

DimensionGreptimeDB MCP ServerQuery and analyze GreptimeDB metrics, logs, and traces via SQL, TQL, and RANGE queries.DBHubBytebase's official, minimalist two-tool database MCP server
FMRS60 / 100 · C74 / 100 · B
Reliability10 / 2013 / 20
Security and permissions12 / 2013 / 20
Maintenance11 / 2016 / 20
Documentation14 / 2015 / 20
Setup experience13 / 2017 / 20
Best for
  • Developers working with time-series and observability data.
  • Teams needing natural language access to their database for query and analysis.
  • Users wanting to integrate AI-assisted data exploration within MCP clients.
  • Scenarios wanting the smallest possible tool count and lowest context-window overhead for database access
  • Cases needing to grant non-technical teammates safe, read-only database access
Not for
  • Users who need write operations or DDL/DML (read-only by default; write mode only for local/test, extremely risky).
  • Users not using GreptimeDB.
  • Users who need direct database access without MCP integration.
  • Scenarios needing database administration operations (creating indexes, altering schema) rather than just querying (DBHub is positioned as a query tool, not a DBA management tool)
Required permissions
  • Read-only access to GreptimeDB for SQL, TQL, and RANGE queries.
  • Access to HTTP API (default port 4000) for pipeline and dashboard management.
  • Access to configured credentials via environment variables or CLI arguments.
  • Data masking is enabled by default to prevent sensitive column exposure.
  • Requires a database connection string (DSN), which may contain sensitive credentials
  • execute_sql can run arbitrary SQL (including writes) by default — must be constrained via read-only mode or the underlying database account's own permissions
Risks and side effects
  • If write mode is enabled (disabled by default), AI could execute destructive SQL; never enable against production.
  • Queries may be expensive if complex or misused; restrict access and resources.
  • Providing secret environment variables over HTTP could increase exposure risk.
  • Database may be inaccessible due to network configuration or startup issues.
  • Under default settings, if the connected database account has write access, execute_sql could let the assistant perform an unintended write or delete — pair with a read-only database account in production
  • The DSN contains a plaintext password — pay attention to the access permissions on wherever the config is stored
Supported clientsClaude DesktopClaude Desktop, Claude Code, VS Code, Cursor, Zed
Tools132