Loading page
Loading page

AI
Put all your MCP servers behind one URL per client, with API keys or OAuth and upstream tokens that stay fresh.
Junctio is a gateway for MCP, the protocol AI tools use to call external tools and data. Instead of setting up each MCP server in every client, you add them once in Junctio. Each client then gets one endpoint that exposes the servers you choose.
Its main promise is that auth does not go stale. Clients connect with an API key or through Junctio's own OAuth server. For upstream servers that use OAuth, Junctio refreshes tokens on a schedule, so calls do not fail when a token runs out.
The README says it is built for one developer or a small team. It suits people who use Claude Code, Codex, Cursor or similar tools and are tired of copying MCP configs between machines. It is a developer tool with no end-user features.
An MCP gateway holds the keys to many of your services. Running it yourself keeps those tokens on your own server, encrypted with the JUNCTIO_SECRET from the Environment tab. Junctio sends no telemetry.
The trade-off is maturity. It is a young project, and some releases may need a fresh database. Keep backups of its volume, read the changelog before updating, and keep JUNCTIO_SECRET safe, since stored tokens cannot be read without it.
Containers: ghcr.io/k2so-dev/junctio:0.2.6
Step 1
Choose the Starter plan. It costs $20 a month and runs up to 3 apps.
Step 2
Open App templates in the dashboard, choose Junctio, and click Deploy. We set up the containers, secrets and domain.
Step 3
Wait a few minutes for the first deploy, then open your new URL and finish the Junctio setup screen.