maruyue commented on issue #175:
URL:
https://github.com/apache/doris-mcp-server/issues/175#issuecomment-5162214984
1. I agree that doris-mcp-server is a general-purpose Doris MCP gateway and
should not be bound to a specific semantic layer. By contrast,
new-doris-mcp-server was originally designed based on Doris's semantic
query service and is intended for agentic analytics.
2. I believe the two have fundamentally different goals. The new-mcp-server
was actually positioned from the start as an analytics-mcp-server, not as a
general-purpose Doris MCP gateway. However, among users/customers
focused on Doris and agent integration who have reached out to me, the ones
primarily
concerned with the semantic layer account for 100% of them. They see
that commercial MCP server products have this capability and want it
open-sourced
into the Doris MCP server — that is the purpose of merging it into the
open-source MCP server.
3. I have the following three suggestions for the Doris MCP server in this
repository:
- The current Doris MCP server is far too complex. Most users use Doris
MCP server for ChatBI and agentic analytics — a single execute_query tool would
probably suffice. Yet we currently have over 50 tools, which is
excessive.
- I think Doris MCP server would be better implemented as a CLI. Users
want to access multiple clusters simultaneously, and with a CLI, agents can
redirect results to files for subsequent analysis. With an MCP
server, returning large results can overwhelm the agent's context window.
- Doris MCP server needs to support the semantic layer in a more
user-friendly way — for example, how users can define a MetricFlow semantic
model and
how to integrate it. The existing MCP server hasn't clearly addressed
this issue, which nearly 100% of users care about. This is the key point
everyone is anticipating from the new MCP server. Of course, Doris
MCP server/CLI could also choose not to provide semantic layer capabilities —
in
practice, these would be provided by a separate data agent/data
analytics server that is more oriented toward agentic analytics. SelectDB plans
to
offer related functionality at the data agent/analytics server layer
in the future.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
