Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@Junctio List all configured MCP servers and their statuses."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Self-hosted MCP gateway for one developer or a small team. One container, one volume, one endpoint per client.
The promise: auth does not go stale. Not between your client and the gateway, and not between the gateway and its upstreams.
No telemetry. Nothing leaves your machine. There is no phone-home, no analytics, no update ping. The one outbound call the UI ever makes is to the public MCP registry, on the Explore page, and only while you are looking at it. Switch on the security audit and there is a second one, described in docs/security-audit.md, carrying package names and versions and nothing else.
One endpoint per client. Point Claude Code, Codex or Cursor at a single URL and manage the servers behind it from a web UI.
Upstream OAuth that survives. Tokens are refreshed proactively on a schedule, not after a request already failed.
Early, but the whole path works: gateway, aggregation, API key auth, a built-in OAuth authorization server, upstream OAuth, REST API, web UI, registry browsing, import from a pasted client config, a management MCP server and a multi-arch image on GHCR. Expect breaking changes before 1.0; CHANGELOG.md says when a release needs a fresh database.
Related MCP server: MCP Manager
The image is ghcr.io/k2so-dev/junctio, built for amd64 and arm64. latest is the last release, edge follows main.
mkdir junctio && cd junctio
curl -fsSLO https://raw.githubusercontent.com/k2so-dev/junctio/main/compose.yml
curl -fsSL https://raw.githubusercontent.com/k2so-dev/junctio/main/.env.example -o .envSet JUNCTIO_SECRET in .env to the output of openssl rand -hex 32, then start it:
docker compose up -dOr run it straight from the source tree:
bun install
bun run build:web
JUNCTIO_SECRET=$(openssl rand -hex 32) bun run startOpen http://localhost:3000, set an admin password, then:
Add a server. For a package on npm pick the npx runtime and type the package name. The form previews the exact command.
Create a namespace and put the server in it.
Create an endpoint pointing at that namespace and issue an API key.
Paste the snippet into your client.
claude mcp add --transport http junctio https://mcp.example.com/mcp/main \
--header "Authorization: Bearer jn_..."Behind a domain, set JUNCTIO_BASE_URL and JUNCTIO_TRUST_PROXY=true and terminate TLS in front of the gateway. The guides under Documentation do this for you.
Variable | Required | Meaning |
| yes | Key used to encrypt stored tokens and headers. At least 32 characters; generate one with |
| for OAuth | Public URL of the gateway. Redirect URIs and resource identifiers are built from it. |
| no | Bearer token for headless admin access, as an alternative to the password login. Also the key to the management MCP server. When set, it is also required to choose the admin password on first start. |
| no | Issuer URL of an external identity provider. Leave it empty to use the gateway's own authorization server. |
| no | Override the expected audience of an external provider. Defaults to the endpoint URL. |
| no | Where |
| no | Socket of the daemon that runs |
| no | Directory of the built UI. Defaults to |
| no |
|
| no | Listener. Defaults to |
| no |
|
OAuth does not work without TLS. Browsers and MCP clients will refuse the redirects. Terminate TLS in front of the gateway. See docs/caddy.md.
Upstream servers: stdio runtimes, remote transports, servers that ship as an image, upstream OAuth
Endpoints: aggregation, downstream auth, protocol negotiation, client compatibility
Management MCP: let an agent configure the gateway instead of clicking through the UI
Explore: the registry, the catalog of other sources, import from a pasted config
Security audit: scheduled vulnerability checks and what a finding does
Deploy: Caddy on a VPS, Dokploy, Coolify, Portainer.
bun install
bun test # unit and integration suites
bun run typecheck # tsc for the server, vue-tsc for the web
bun run dev # gateway with watch mode
bun run dev:web # vite dev server on 5173, proxies /api to 3000
bun run build:web # SPA into apps/web/dist, served by the gateway
bun run db:generate # regenerate drizzle migrations after a schema changeThe UI is Vue 3, Tailwind 4 and shadcn-vue, built as a static SPA. The gateway serves it from apps/web/dist unless JUNCTIO_PUBLIC_DIR says otherwise.
The test suite covers the things the product claims: upstream refresh under a five second token lifetime with a hundred calls and zero client-visible failures, single-flight collapsing, refresh token rotation, fifty stdio restart cycles with no zombie processes, and 404 on the discovery documents of an API-key-only endpoint.
make help lists the same commands run in a throwaway toolchain container, plus make up, which builds junctio:local from the source tree and starts the stack through compose.build.yml.
The gateway runs arbitrary packages and holds tokens for every integration you connect. Read SECURITY.md before exposing it to anyone but yourself.
MIT
See CONTRIBUTING.md for the setup, the checks a pull request has to pass, and the repository layout. Report a vulnerability privately as described in SECURITY.md.
This server cannot be deployed
Self-hosted federated MCP gateway: one OAuth 2.1 MCP server in front of N apps, user-level scopes.
Governed MCP gateway: one endpoint for your tools, with credential custody and audit log.
Zero-setup MCP gateway securely connecting AI to your tools with authentication and workflows
One connector for 15,000+ MCP servers plus your team's private MCPs, from any AI client.