For AI agent developers

Your agent config is the place API keys go to be forgotten about. Statio replaces every one of them with a single Statio key you can revoke, and the real credentials stay encrypted in Statio.

Hubert Robert, Bridge over a Cascade · The Met, CC0

Your agent configs are a security liability.

Every agent config file has raw API keys. You have 15 different STRIPE_KEY, GITHUB_TOKEN, SLACK_TOKEN values scattered across agent configs. One leaked config and every key is compromised. Rotating a single key means redeploying every agent that uses it.

Statio is the checkpoint.

Statio stores every credential encrypted. Your agents get one Statio key that reaches every API you have access to. Keys are never handed to an agent. Rotate any credential instantly without touching a single agent config.

  • One token replaces dozens of scattered API keys

    The config on each machine holds one revocable Statio key. Your Stripe, GitHub and Slack secrets are encrypted at rest with AES-256-GCM and added inside the gateway at call time, so the agent never sees them.

  • Each agent gets its own identity

    An agent authenticates as itself, never on your personal token. Suspend or revoke one without touching anything else, and the log names the agent rather than you.

  • Turn off one tool, keep the rest

    Grant an agent a whole server, then deny the tools it should never call. A tool-level deny overrides the server grant, so reading rows does not come with deleting them.

  • Instant credential rotation, with no agent redeployment

    The key is stored in Statio, not in the agent, so rotating it changes nothing in any config file.

  • Works with Claude, Cursor, VS Code and other MCP clients

    The desktop app writes the config for Claude Code, Claude Desktop, Cursor, Windsurf, VS Code, Cline, Continue.dev, Zed and Amazon Q in one click. From a terminal, mcphub config does the same.

  • Catalog servers, or bring your own OpenAPI spec

    Install Stripe, GitHub, Slack and more from the catalog, or give Statio an OpenAPI spec and it generates, builds and hosts the server, on every plan including Free.
    About mcp-gen

  • A record of every tool call, per agent

    Activity lists each call through the gateway with the agent or person behind it, the tool, the server, the latency and the status code. A refused call shows the 403 and the reason.

What changes in the config file

Before Statio, each AI client holds its own copy of every key. After, it holds one Statio key. Illustrative data.

Other use cases

  • For API providers

    Publish your API to agents without building MCP hosting, auth and rate limiting yourself.
    Read more

  • For enterprise security

    Grant access per tool, keep the record of every call, and revoke any agent on its own.
    Read more

Lock down your first tool in minutes.

Three MCP servers, one of them hosted, and 10,000 calls a month, free and without a card. If you outgrow it the next plan is $19.

Two steps: create your account, then install the desktop app on each machine that runs an AI client.

Start freeDownload the app