JunctioUse cases
Each page is one setup, end to end: what you connect, how it authenticates, and where it stops.
Connect a client
One page per client and per way of hosting it: the endpoint, the auth mode, and what the gateway does for you once it is in place.
Claude CodeOne MCP endpoint for Claude CodeReplace a dozen server entries in Claude Code with one HTTP endpoint that Junctio keeps authenticated.ReadCursorCursor with a self-hosted MCP gatewayPoint Cursor at one Streamable HTTP endpoint and stop managing per-project mcp.json files.Readclaude.aiA custom connector for claude.ai and Claude DesktopServe your own MCP servers to claude.ai and Claude Desktop through the built-in OAuth authorization server.ReadTeamShared MCP servers for a small teamOne gateway, one namespace per role, one key per person. No shared secrets in client configs.ReadSelf-hostedJunctio on a VPS behind CaddyRun the gateway on your own server with automatic TLS, a persistent volume and OAuth that works.Read
Give the agent hands
The gateway is the OAuth door for claude.ai, Claude Desktop, Codex and Claude Code. Behind it, anything with an API becomes tools the agent can call.
DokployReplacing Lovable with a $5 VPS and DokployDeploy the gateway on Dokploy, put the Dokploy MCP server behind it, and let your agent write a site and ship it to your own VPS.ReadOpenAPIAny REST API as MCP tools, in an eveningPoint the OpenAPI MCP Server at a spec, let an agent write the tool descriptions through the management MCP, hand the client one endpoint.Read3x-uiA VPN panel your agent operates3x-ui publishes an OpenAPI spec and issues bearer tokens. Load it into the OpenAPI MCP Server behind Junctio and ask for a client, a limit and a link.Read