Connections
Connections are encrypted credential vaults for upstream MCP servers. Instead of putting real API keys in your code, you create a connection in Igris that stores the credential securely and gives you a clean gateway URL.How Connections Work
- Real credentials never leave Igris — encrypted at rest with AES-256-GCM
- Rotate credentials instantly without changing any code
- Revoke access by disabling the connection
- Full audit trail of every request per connection
Create a Connection
In the dashboard: Governance → Connections → New Connection Or via API:Use a Connection
With the SDK
Direct MCP Client Config
Credential Injection
When the gateway receives a request, it:- Strips your Igris API key (never forwarded upstream)
- Decrypts the connection’s credential
- Injects it as
Authorization: Bearer <credential>to the upstream server
Rotate Credentials
Update a credential without changing any SDK configs:Slug Format
Connection slugs must be:- Lowercase letters, numbers, underscores, hyphens
- 3-64 characters
- Start with a letter or number
vk_github_prod, slack-mcp, analytics01