doris-mcp-server — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Monitor exact implementation activity, MCP interface, permission and setup changes.

Reviewed Oct 10, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

Apache Doris database read-oriented integration

What we know

Apache Doris MCP Server Public Radar listing describes capability; verify precise runtime setup and privilege boundaries upstream.

Maintenance / activity evidence

GitHub exact repo pushed_at 2026-10-01T19:00:50Z

Tracking evidence observed Oct 10, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: medium.

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Database credentials and query access; upstream documents a read-only catalog and separate auth/RBAC controls. Complete write authority is not verified.
Doris credentials; stdio or local Streamable HTTP; configure authentication for network access
Sensitive access: Doris tables, metadata, query results

Database credentials and query access; upstream documents a read-only catalog and separate auth/RBAC controls.
Public tracking suitability is not an installation safety audit.

Full authority, access and evidence limits are available in Review context and Access & risk.

Popularity

351 repository stars

Stars observed Oct 10, 2026.

Repository total for apache/doris-mcp-server.

All limitations / Review context

Has doris-mcp-server changed its documented MCP interface, authentication or privilege boundaries, and does it merit promotion?

Limited editorial listing; known permission implications disclosed, no independently established publication blocker.

Database credentials and query access; upstream documents a read-only catalog and separate auth/RBAC controls.
Public tracking suitability is not an installation safety audit.
Doris credentials; stdio or local Streamable HTTP; configure authentication for network access
Doris tables, metadata, query results
Sensitive access: Doris tables, metadata, query results
Complete write authority is not verified.
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
Upstream credential and permission scopes must be validated before runtime use.
Write actions/tool inventory not confirmed against exact tool documentation; listed action classes remain illustrative or context-dependent. Empty inventory does not establish read-only.
Some integration/runtime instructions are not confirmed from a first-party install guide and therefore intentionally omitted.
Exact GitHub pushed_at 2026-10-01T19:00:50Z

Original activity observations

GitHub exact repo pushed_at 2026-10-01T19:00:50Z

Technical identity

github.com/apache/doris-mcp-server

Exact implementation source: https://github.com/apache/doris-mcp-server ↗
Reviewed resource type: MCP Server
Repository identity: apache/doris-mcp-server

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 10, 2026 · Latest source observation Oct 10, 2026

GitHub repository ↗
apache/doris-mcp-server
Recorded repository material and project history.

Setup · Watchlist

Install & Agents

Publisher instructions.

Source evidence observed Oct 12, 2026.

Additional setup details required — see the specific gaps below.

Install / connect
Publisher instructions
Apache Doris MCP 1.0 requires following the official 1.0 deployment and migration guides, not old pre-1.0 flat-tool tutorials. Current GA transport options are stdio or Streamable HTTP; choose matching host integration and database scope.
pip install doris-mcp-server==1.0.0
doris-mcp-server --transport stdio
Configure / authenticate
Publisher instructions
Consult official Doris 1.0 configuration reference, security model, deployment and host integration guides for version-compatible stdio/HTTP launch and database credentials. Do not reuse obsolete flat tool names or expose write permissions; 1.0 documents eight capability domains. Use the official 1.0 MCP Server launch for hosting; `doris-mcp-client` is a distinct client executable, not the server.
Advanced configuration · mcpServers json
{ "mcpServers": { "doris": { "args": [ "--transport", "stdio" ], "command": "doris-mcp-server", "env": { "DORIS_DATABASE": "information_schema", "DORIS_HOST": "127.0.0.1", "DORIS_PASSWORD": "REPLACE_WITH_DORIS_PASSWORD", "DORIS_PORT": "9030", "DORIS_USER": "mcp_reader", "MCP_TOOL_EXPOSURE_MODE": "hierarchical" } } } }
Check connection
Suggested check
Verify the server starts in the intended stdio/HTTP mode, the client discovers eight tool domains and read-only database access succeeds. Compare actual enabled child capabilities to official 1.0 version matrix; runtime results depend on database support and auth.
Remove / uninstall / revoke
MCP100 setup guide
Stop the application/service using its documented controls. Platform-specific uninstall and credentials management require separate evidence. Remove only `doris` from this MCP client’s `mcpServers` configuration and restart/reload that client. Other entries must remain intact. In the MCP client settings remove only the `mcpServers.doris` entry and restart/reload. This is a concrete client disconnect, separate from uninstalling the local package.
python -m pip uninstall doris-mcp-server

Official Documentation & Sources

What it does

Apache Doris MCP Server Public Radar listing describes capability; verify precise runtime setup and privilege boundaries upstream.

Capability: Data & Databases
Resource type: MCP Server
Best fit: Apache Doris database read-oriented integration

Representative uses

Apache Doris database read-oriented integration

Limitations

Database credentials and query access; upstream documents a read-only catalog and separate auth/RBAC controls.
Some integration/runtime instructions are not confirmed from a first-party install guide and therefore intentionally omitted.
Exact GitHub pushed_at 2026-10-01T19:00:50Z

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: Doris credentials; stdio or local Streamable HTTP; configure authentication for network access
Permissions: Database credentials and query access; upstream documents a read-only catalog and separate auth/RBAC controls.
Data handling: Doris tables, metadata, query results
Cost: Provider or usage fees possible; verify current pricing
Risk and cautions: Database credentials and query access; upstream documents a read-only catalog and separate auth/RBAC controls.

Access scope and cautions

Write actions: Not verified
Sensitive access: Doris tables, metadata, query results
Risk level: high
Security notes: Database credentials and query access; upstream documents a read-only catalog and separate auth/RBAC controls. Public tracking suitability is not an installation safety audit.

The reviewed evidence does not establish the complete write authority of this MCP. Consult the unresolved evidence before granting write access.

FAQ

Based on reviewed evidence as of 2026-10-10T03:38:00Z. Watchlist tracking is not a recommendation or a security certification.

Which tasks are documented for this implementation?

The reviewed tasks include: Apache Doris database read-oriented integration.

What setup and authentication are documented?

A complete connection procedure is not verified. Client notes: Installation command omitted unless verified or clearly package-specific; do not infer npx/uvx entrypoints. These facts do not supply missing installation commands, credentials or a verified authentication procedure. Authentication: Doris credentials; stdio or local Streamable HTTP; configure authentication for network access

Can it modify data or perform write operations?

Not verified. The available evidence does not establish the complete write authority. Recorded permission context: Database credentials and query access; upstream documents a read-only catalog and separate auth/RBAC controls.

What data-handling boundary should I consider?

Doris tables, metadata, query results Recorded sensitive-access context: Doris tables, metadata, query results.

What limitations and risks should I check before use?

Database credentials and query access; upstream documents a read-only catalog and separate auth/RBAC controls. Some integration/runtime instructions are not confirmed from a first-party install guide and therefore intentionally omitted. Exact GitHub pushed_at 2026-10-01T19:00:50Z. Public tracking suitability is not an installation safety audit. Upstream credential and permission scopes must be validated before runtime use.