Official AntV MCP server that turns a description of your data into a rendered chart — 26 visualization types from bar and line to sankey, mind-map, fishbone and geographic maps.

Apache Doris MCP Server
Summary
Apache's official read-only MCP server for Doris — eight tool domains and 55 progressively disclosed children covering catalog, query, cluster, lineage and lakehouse.
Features
- Eight stable tool domains with 55 progressively disclosed children
- Read-only catalogue — the admin domain is reserved, not registered
- Query, explain, profile, diagnosis and slow-query inspection
- Cluster nodes, metrics, memory, cache, compaction and workload groups
- Data lineage, audit, quality and storage governance tools
- Static token, JWT, OAuth/OIDC and Doris-backed OAuth authentication
- MCP 2026-07-28 on both stdio and Streamable HTTP
Installation
Set up this MCP server in your favorite AI agent — copy a ready-made configuration below.
Description
The Apache Doris MCP Server exposes the real-time analytics database to agents over the MCP 2026-07-28 specification, and its 1.0 release is a deliberate rebuild of the tool surface. Instead of dozens of flat tools competing for context, it presents eight stable domains — doris_catalog, doris_query, doris_cluster, doris_pipeline, doris_search, doris_governance, doris_lakehouse and doris_semantic — each of which is called with {} to discover the authorised children and their exact schemas, then called again with a child_tool, arguments and the returned manifest_version. Fifty-five children sit underneath, covering everything from table context and query profiling through node metrics, compaction and workload groups to ingestion freshness, text/vector/hybrid search, data lineage, audit and external lakehouse catalogs. Hosts that cannot do progressive disclosure can set MCP_TOOL_EXPOSURE_MODE=flat.
The catalogue is read-only by design — doris_admin is reserved and not registered — and authorisation is explicit, with static tokens, JWT, external OAuth/OIDC and Doris-backed OAuth all supported, plus per-request RBAC against the Doris route.
Requires Python 3.12+, Apache Doris 2.0.0+ and network access to the FE MySQL endpoint (usually port 9030). Both stdio and Streamable HTTP are GA; a legacy HTTP adapter (ENABLE_LEGACY_HTTP_ADAPTER=true, /mcp/legacy) covers hosts still on the 2025-06-18 handshake. Apache 2.0 licensed.
Related MCP Servers
Turso's hosted MCP server — manage Turso Cloud databases, branch them point-in-time and run SQL from a coding agent, authorised over OAuth with no API token to paste.
Google's official Firebase MCP server — 70+ tools across Firestore, Auth, Crashlytics, Cloud Functions, Storage, Messaging and Remote Config, shipped inside the Firebase CLI.
InfluxData's official MCP server for InfluxDB 3 — schema discovery, bounded SQL and InfluxQL queries, line-protocol writes and token administration across Core, Enterprise and Cloud.
