feat: Add Proxied Jupyter UI Tools MCP Server - #398
Open
acook4148 wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Sets up a proxied Jupyter UI Tools MCP server that allows conflict resolution with an enterprise MCP config for Claude Code.
The current MCP setup implements the jupyter UI tools MCP server as an in-process MCP server which gets passed to the claude-agent-sdk and then passed to the Claude Code CLI as it's own MCP config with
--mcp-config. This will conflict with an enterprise MCP config (managed-mcp.json) file, causing an error to be thrown by the Claude Code CLI and then the Claude Mode sidebar to fail.This proxied jupyter UI tools MCP server is a mimic of the current in process server, except it runs in the same jupyterlab server through a proxy URL. This allows developers to modify their enterprise MCP config to add a section for this proxied MCP server so that it will work in the same way as the in-process MCP server
A toggle is provided which allows developers to choose whether they want the proxied MCP jupyter UI tools server, or the original in-process one. The default is the original in-process jupyter UI tools server. Using the proxied MCP server requires the enterprise MCP config to also register this server.