Without a gateway, each agent on each machine holds its own credentials, and rotating a leaked one means finding every machine. Lanyard puts one URL in front of the servers you choose, with a key per agent you can revoke on its own.
- 400+ servers in the catalog
- Agents act as a person
- Tools are opt-in, not default
- Revoke one key, not all of them
Three tools instead of three hundred
Agents see list, search and call_tool rather than every tool of every server at once. Context stays small, and adding a server does not make every prompt more expensive.
- A catalog of 400+ remote MCP servers, including Linear, GitHub, Atlassian, Notion, Slack and ShareCube
- Or paste any remote MCP endpoint your provider documents
- Works with Claude Code, Claude Desktop, Cursor, VS Code, Codex, Windsurf and CAPA
Agents act as a person, never a shared bot
Everybody connects their own account to each server, with OAuth or a token. An agent using your key calls Jira as you, with your permissions. It never receives the credential itself.
- Tokens encrypted in the browser and sealed at rest
- One key per agent, revoked on its own, with the last use shown
- Keys revoked automatically when somebody loses access or leaves
Decide what agents may do, once
Every tool is opt-in per gateway. Read-only tools are on by default; anything that writes or deletes waits for a person to tick it, and you are told when an approved tool changes under you.
- Per-gateway tool allowlists, grouped by read, write and destructive
- An org-wide allowlist of server hosts, and your own registered OAuth clients
- Share gateways with people or identity-provider groups, and revoke instantly
- An audit log of every call and change, with CSV and JSON export
Pricing
Free for one gateway, five servers and 10,000 tool calls a month. Team is $10 per seat a month. Enterprise: contact@infragate.co.
