Tokens are not stored in plain text
Gateway, OAuth, and credential-setup tokens are stored as hashes.
Remote MCP, without the credential sprawl
Your agent needs tools.
Not every tool.
Put remote MCP providers behind one Streamable HTTP endpoint. Juraguard gives AI clients compact search and call controls, loads schemas only when needed, and keeps provider credentials on the server.
01 — The problem
More connections should not mean more exposure.
Tool overloadAgents should not receive hundreds of tool definitions before they know which one they need.
Secret sprawlProvider credentials do not belong in every client config, prompt path, or developer machine.
Scattered controlAccess should be revocable and reconnectable in one place—not hunted across clients.
02 — The mechanism
Small at the edge.
Capable behind it.
- 01
Connect once
Point your AI client at one Streamable HTTP MCP endpoint and complete its browser authorization flow.
- 02
Search before loading
Compact search controls find relevant tools. Full tool schemas load only when the agent needs them.
- 03
Call by exact name
The gateway routes the call to the selected remote provider while provider credentials stay encrypted and server-side.
- 04
Govern centrally
Writes require an explicit per-integration toggle. Revoke access or reconnect provider credentials from one dashboard.
03 — Fits the clients you use
For developers and teams connecting AI clients to remote MCP providers.
Clients
- Claude Code / Desktop
- Cursor
- VS Code / Copilot
- Codex CLI
- OpenCode
- Gemini CLI
- Windsurf
- Streamable HTTP MCP clients
Providers today
- GitLabDirect provider integration.
- Remote OAuth MCPGeneric Streamable HTTP connection.
- Custom-header MCPGeneric Streamable HTTP connection.
04 — Security by construction
Secrets stay behind the gateway.
Concrete controls, not certification badges or borrowed trust.
Provider credentials remain private
OAuth credentials, GitLab tokens, and custom headers are encrypted server-side.
Setup links close quickly
Credential setup links are one-use and expire after 15 minutes.
Public mode rejects unsafe targets
SSRF protections block private and otherwise unsafe upstream destinations.
Upstreams have limits
Provider requests use bounded responses and timeouts rather than open-ended reads.
Security events avoid secrets
Recorded security events redact credential-like and token-like values.
Managed cloud · free beta
Operate tools.
Not the gateway.
Join the managed cloud beta at no cost. Beta users receive 50% off their first 12 paid months after beta.
Final cloud pricing will be announced before the beta ends.
Join the free beta05 — Choose who operates it
A clear path now.
No invented price later.
Managed cloud
Free beta
Juraguard operated for you. Final cloud pricing announced before beta ends; beta users get 50% off their first 12 paid months.
Join the free betaSelf-host · personal
AGPL-3.0 core
Run the personal core with Docker on one host. SQLite is the default; PostgreSQL is optional for deployments that need it.
Read self-host docsSelf-host · organization
Commercial license
Organization modules are commercially licensed and separate from the AGPL personal core. Contact Pyango for terms.
Ask about organization licensing06 — Questions, answered
Before you connect.
Where do provider credentials live?
Encrypted on the Juraguard server. AI clients use the gateway endpoint and do not receive the saved OAuth credentials, GitLab tokens, or custom headers.
Can I self-host Juraguard?
Yes. The AGPL-3.0 personal core has a Docker one-host installer, uses SQLite by default, and can use PostgreSQL. Follow the self-host documentation for production deployment rather than exposing a development container port.
Which providers and clients work today?
Providers are GitLab directly, plus generic remote OAuth or custom-header Streamable HTTP MCP servers. Documented clients include Claude Code/Desktop, Cursor, VS Code/Copilot, Codex CLI, OpenCode, Gemini CLI, and Windsurf; other compatible Streamable HTTP MCP clients can connect too.
Can an agent write to a provider by default?
Not through an integration unless its write toggle is explicitly enabled. You can turn writes off again, revoke client access, or reconnect provider credentials centrally.
What happens after the managed beta?
Final cloud pricing will be announced before beta ends. Beta users receive 50% off their first 12 paid months; there is no final monthly price to announce yet.
What if commercial license validation is temporarily unavailable?
A previously validated, signed organization license can remain usable for its configured outage grace period. The personal AGPL core needs no commercial license and is unaffected by license-server availability.
One endpoint. Credentials under control.