jupyter-server-proxy

What it is and what it does

Jupyter Server Proxy is a Jupyter server extension that lets you run and access arbitrary external processes through your Jupyter environment. It works by starting external services (like RStudio, Shiny Server, or PostgreSQL) and proxying authenticated web requests to them through Jupyter-managed paths, so users see them as part of the Jupyter interface rather than separate applications.

The package is commonly used in two scenarios: allowing JupyterHub or Binder users to launch into non-Jupyter web interfaces (RStudio, Shiny, OpenRefine) without leaving the Jupyter environment, and enabling frontend JavaScript code to safely access local web APIs of other processes. It includes both a Python server extension and bundled JupyterLab extension with launcher buttons for registered services. The documentation notes a security consideration: ensure proxied processes cannot be accessed directly by other users, typically by running Jupyter in a container with restricted network access.

Use it for:

• Launch RStudio or Shiny Server from JupyterHub or Binder alongside Jupyter notebooks for users who need R-based interfaces.
• Provide JupyterLab users with one-click access to local development tools like Code Server or OpenRefine without leaving the lab.
• Allow JupyterLab extensions to safely communicate with local web APIs of background processes.
• Expose database management interfaces through Jupyter for data science workflows.
• Create unified entry points for multi-tool data science environments where Jupyter is the hub.

Worth the install?

AI-flagged interpretation of the facts on this page — verify before relying

Jupyter Server Proxy runs external processes (RStudio, Shiny, PostgreSQL, Code Server, etc.) alongside your Jupyter server and proxies authenticated web access to them through paths like `/rstudio`.

Yes. The package is actively maintained, has low install friction, carries a permissive BSD 3-Clause License, and solves a real problem for Jupyter users who need to run or access external services. The security warning in the documentation is important to understand but does not disqualify the package—it simply requires thoughtful deployment. No known vulnerabilities are recorded.

Install

jupyter-server-proxy on PyPI

pip install jupyter-server-proxy

uv add jupyter-server-proxy

poetry add jupyter-server-proxy

Installing jupyter-server-proxy

Before you install

Low install friction with a pure-Python wheel distribution. Actively maintained with a recent release; last commit on 2026-08-11 and 400 repository stars indicate ongoing support.

License in practice

BSD 3-Clause License permits redistribution and modification with minimal restrictions, making it safe for commercial and private use provided copyright notice is retained.

Quickstart

pip install jupyter-server-proxy

Then configure a process in your Jupyter configuration to proxy it through the server extension, which will appear in JupyterLab's launcher panel.

Requires Python >=3.8 and a running Jupyter server; external processes must not be directly accessible by other users to maintain security.

Verify before relying

• Whether the JupyterLab extension (@jupyterhub/jupyter-server-proxy) is automatically installed or requires separate setup.
• Specific security isolation guarantees when running untrusted external processes.
• Performance characteristics when proxying multiple concurrent external services.

Package facts

Evidence: jupyter_server_proxy-4.5.0-py3-none-any.whl

Keywords: jupyter, jupyterlab, jupyterlab-extension

Tags

More Dynamic Content packages