Your whole team on approved MCP servers in five minutes.

MCP is how AI agents reach your APIs, which in practice means a live key pasted into a config file on somebody's laptop. Statio connects the whole team to an approved server in one click and enforces the tool-level permissions you set. Nothing gets installed on developer machines, and there is no sales call between you and a working setup.

No endpoint agent required
Nine AI clients, one command
Keys encrypted at rest
Access Control
Per-tool accessAGENT MAY CALL
payments.listChargesALLOWED
payments.getCustomerALLOWED
payments.createRefundDENIED
payments.updateSubscriptionDENIED
Works with the AI clients your team already uses
  • Claude Code
  • Claude Desktop
  • Cursor
  • Windsurf
  • VS Code
  • Cline
  • Continue
  • Zed
  • Amazon Q

Your agents hold one token instead of every key.

Both files below hold the same three integrations. On the left, three live secrets sitting in plaintext on a laptop; on the right, one token that expires in 24 hours.

Keys stored in vault, never exposed
Instant credential rotation
Every API call logged with identity
$mcphub scan
Lists every MCP server configured on this machine and flags the ones that do not route through Statio. Nothing is uploaded until you run mcphub report.
Without Statio
{ "mcpServers": { "stripe": { "env": { "STRIPE_KEY": "sk_live_..." } }, "github": { "env": { "GITHUB_TOKEN": "ghp_..." } }, "slack": { "env": { "SLACK_TOKEN": "xoxb-..." } } } }
With Statio
{ "mcpServers": { "statio": { "env": { "STATIO_TOKEN": "eyJ..." } } } }

Connect the team without handing out the keys.

A new hire gets the approved servers on their first morning. Access is granted per tool rather than per server, so an agent that can read charges cannot issue refunds, and every call it makes is logged against the person behind it.

One-click provisioning

Connect your whole team to an MCP server in one click: Claude Code, Claude Desktop, Cursor, Windsurf, VS Code and more. No hand-edited JSON, and new hires get the approved set on day one.

Shadow MCP discovery

See every MCP server your team has installed, including the ones nobody approved. No EDR or MDM required, and most tools cannot see this without one.

Access policies

Grant or revoke a tool in one click. Permissions are per tool, not per server, and enforced on every request at the gateway.

Credential vaulting

Keys are encrypted at rest and fetched at call time. A compromised agent leaks a token that expires in a day, not a key that never does.

Pre-built catalog

Official MCP servers, hosted and kept working: Stripe, GitHub, Notion and more.

Audit trails

Every tool call logged with identity, timestamp and outcome. Stream it to your SIEM.
Built for the teams calling APIs, the teams publishing them, and the security teams answerable for both.

Find the MCP servers nobody approved, without CrowdStrike, Intune or Jamf.

Most tools discover unapproved MCP servers by reading an endpoint-security or device-management system you already run: CrowdStrike, Intune, Jamf. If you don’t have one, and most teams under a few hundred people don’t, they see nothing. Statio ships its own lightweight agent, so discovery works on day one.

I

Finds what you did not approve

Scans the MCP config of every AI client on the machine and reports what is installed, including the servers that never route through us.
II

Configures everything for them

One click writes the correct config for Claude Code, Claude Desktop, Cursor, Windsurf, VS Code, Cline, Continue, Zed and Amazon Q.
III

Notices the moment it changes

Watches config files rather than polling. A server added at 2pm shows up at 2pm, not in tomorrow night’s inventory sweep.
Fleet · engineering-042 UNAPPROVED
stripeClaude Desktop
MANAGED
githubClaude Code
MANAGED
internal-hr-apiCursor
EXTERNAL
notion-personalClaude Desktop
EXTERNAL
jiraClaude Code
MANAGED

Every call passes one checkpoint.

Your agents never hold a credential. They hold a token, the gateway trades it for the real key at call time, and the key is back in the vault before the response reaches them.

JWT
fetch creds
credentials
API call
IAI agentClaude, GPT, Cursor
IIStatio gatewayValidates the token, applies policy
IIICredential vaultFetches the key at call time
IVMCP serverStripe, GitHub, Notion
VExternal APIThe service being called
Your config
Our infrastructure
External service
I

AI agent

Claude, GPT, Cursor
II

Statio gateway

Validates the token, applies policy
III

Credential vault

Fetches the key at call time
IV

MCP server

Stripe, GitHub, Notion
V

External API

The service being called

Watch a call get refused.

Policies are evaluated at the gateway before a credential is ever decrypted. The agent gets an error, the API is never touched, and you get a line naming who asked, what they wanted and which policy said no.
cursor@acmeAGENT
payments.createRefund
Statio gatewayCHECKPOINT
DENIEDpolicy · finance-only
payments APINEVER REACHED
Allowed in the same second
14:02:09cursor@acmepayments.listCharges
ALLOWED42ms
14:02:10claude-code@acmedocs.search
ALLOWED18ms
14:02:14windsurf@acmegithub.createIssue
ALLOWED61ms
The same events stream by signed webhook to your SIEM: the security monitoring system your team already runs. Retention runs from 7 days on Free to a year on Business, and Enterprise sets its own.

Shipped recently

Statio is under active development. Here’s what landed most recently.
August 2026

Self-serve capacity

Buy additional hosted MCP servers and turn on usage overage from the billing page, with a spend cap you set.
August 2026

Per-tool access policies

Grant access to individual tools rather than whole servers, enforced at the gateway on every request.
July 2026

Fleet MCP discovery

Find every MCP server installed across your team, including the ones nobody approved, without an endpoint agent or device management.
July 2026

SIEM export

Stream signed audit events of every tool call to your existing security tooling.
Full changelog

Flat monthly prices, never per seat.

Adding a member never changes your bill. Free needs no card and has no path to a charge.

Free

$0
Evaluate Statio. Hard limits, never a surprise bill.
  • Servers3 MCP servers
  • HostedNone · connect by URL
  • API calls5,000 / month
  • Members1 member
  • PoliciesCatalog defaults
  • Audit logs7 days
Start free

Developer

$19/mo
For a solo developer running agents in production.
  • Servers10 MCP servers
  • Hosted3 from your own spec
  • API calls25,000 / month
  • Members1 member
  • PoliciesCatalog defaults
  • Audit logs90 days
Start on Developer
Most Popular

Team

$99/mo
For teams sharing one governed endpoint.
  • Servers25 MCP servers
  • Hosted10 from your own spec
  • API calls250,000 / month
  • MembersUp to 25 members
  • PoliciesPer-tool access
  • Audit logs90 days
Start on Team

Business

$349/mo
For organizations that have to answer to a security review.
  • ServersUnlimited
  • Hosted50 from your own spec
  • API calls1,000,000 / month
  • MembersUnlimited members
  • PoliciesFull RBAC + SSO/SAML
  • Audit logs1 year, SIEM export
Start on Business

Enterprise

Unlimited servers and members, custom call volume and log retention, 99.9% SLA, audit exports in the formats your review asks for, bring-your-own proxy, and a named contact who answers.
Talk to us
Pay annually and get 2 months free. Additional hosted MCP servers are $5/month each. Need more calls? Turn on overage billing for $9 per additional 100,000, off by default, with a spend cap you set.

Common questions

Connect your first server.

Three MCP servers and 5,000 calls a month, free and without a card. If you outgrow it the next plan is $19, and it stays $19 as the team grows.
Start free
  • Keys are encrypted at rest and never handed to an agent
  • Cancel anytime. You drop to Free, nothing is deleted
  • No card required, and no way to spend money on Free
How Statio handles credentials →