kkalyan commented on PR #5277:
URL: https://github.com/apache/zeppelin/pull/5277#issuecomment-4883156830

   Thanks @jongyoul, this is great feedback — agreed on all three points.
   
   I've added a design doc at `zeppelin-mcp/DESIGN.md` (in the latest commit) 
that works through the architecture question in detail. Short version:
   
   **On a remote in-instance MCP server:** I agree that's the right long-term 
home. Since Zeppelin is already a web service, a remote MCP endpoint hosted by 
`zeppelin-server` over Streamable HTTP means no per-user install, one shared 
auth surface (reuse Shiro), multi-user by construction, and access to 
in-process state the REST API doesn't publish. The doc captures this as the 
Phase 2 target.
   
   The reason this PR starts with a **standalone stdio server** is phasing, not 
disagreement: it ships with no server-side changes, works against any existing 
Zeppelin (including already-deployed older versions), uses the mature Python 
MCP SDK, and lets us stabilize the tool surface before committing it to the 
server's release cadence. Crucially the **tool definitions + orchestration 
logic are transport-agnostic** — the same tools move from stdio to HTTP without 
redesign — so Phase 1 is a stepping stone, not throwaway work.
   
   One nuance worth surfacing: a useful MCP server isn't a 1:1 re-serialization 
of the REST API — the value is the orchestration layer (synchronous run 
semantics, stuck-interpreter detection, actionable errors, output shaping, 
cross-system diagnostics). That layer is identical regardless of where the 
server is hosted.
   
   **On docs + community discussion:** agreed — I'll start a `[DISCUSS]` thread 
on dev@ linking the doc, JIRA, and this PR, and add a user-facing page under 
`docs/`. Will hold merge until that conversation lands.
   


-- 
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]

Reply via email to