Overview
Step-by-step setups for running Keycard with a gateway, identity provider, or agent platform you already use.
A recipe takes a product you already run, such as Kong, Azure API Management, Microsoft Entra ID, or Amazon Bedrock AgentCore, to a working Keycard setup on one page. Your product keeps doing its job, and Keycard decides which people and agents may reach each resource and issues the short-lived credentials they use.
- Agent or MCP client Signs in through Keycard, for a person or as itself, and asks for access to a resource.
- Keycard Checks policy, then issues a short-lived token for that caller and that resource, or refuses.
- Your gateway or service Checks the token before it lets the call through.
- Keycard Records each decision in the Audit Log.
Find a recipe
Section titled “Find a recipe”| If you’re asking | Start with |
|---|---|
| Our MCP servers sit behind a gateway. Can Keycard decide who reaches them? | agentgateway |
| Can the gateway call GitHub or Google as the person who asked? | agentgateway upstream credentials |
| We already run Kong, Azure API Management, or Gravitee. Can Keycard allow or refuse each tool call inside it? | Kong AI Gateway, Azure API Management, Gravitee |
| Our agents run as Entra app registrations. Can they sign in to Keycard with their own Entra token? | Entra service principals |
| We have many agents in Entra. Can we register them all from Terraform? | Entra service principals with Terraform |
| Our agents run on Amazon Bedrock AgentCore. How do they get Keycard tokens? | Amazon Bedrock AgentCore |
| Other agents need to call our AgentCore runtime. Can Keycard decide which ones may? | AgentCore runtime access |
What every recipe has
Section titled “What every recipe has”Each recipe starts with what happens on each request, then has these sections in this order:
- Prerequisites, including the product version the recipe was tested with.
- The setup steps, grouped by what each part sets up.
- Verify, with one call that Keycard allows and one that it refuses.
- Clean up, which removes what the recipe created, in Keycard and outside it.
- Limits, which says where Keycard’s part ends and what the recipe doesn’t cover.
- Troubleshooting, which lists errors you might see, each with its cause and fix.
Browse by component
Section titled “Browse by component” Gateways Your gateway checks Keycard tokens, and Keycard decides who reaches the MCP servers behind it.
Identity providers Agents sign in to Keycard with identities from the provider you already run.
Agent platforms Agents on a cloud platform get Keycard tokens without a stored secret.