Implemented an incoming JupyterLab MCP server, finding an Advocate to guide it into a subproject

I recently drafted https://github.com/complyue/jupyterlab-rtc-mcp which allows any other MCP client (AI agent runner) connect to JupyterLab functionalities via jupyterlab-rtc-mcp MCP server.

By leveraging RTC (jupyter-collaboration) infrastructure, AI agents operate in real-time to collaborate with human users.

I’d like it to live as a Jupyter subproject, to easily accept subsequent contributions and maintenance.

The proposed Subproject must have an Advocate who is an active Steering Council member. The role of the Advocate is to introduce the Subproject team to the Jupyter community and help them through incubation processes. While the Advocate may be involved in the actual development and design of the Subproject, that is not required.

3 Likes

I believe these guidelines are a bit outdated, there is no Steering Council anymore. I think the spirit of the incubation process is still valid though. I am happy to support your effort in placing this in one of jupyter or jupyter-contrib organisations.

Let me reply on Implemented an incoming MCP server · Issue #17812 · jupyterlab/jupyterlab · GitHub .

2 Likes