A named bundle of grants you can give to people as one unit. See Permissions.
A person's administrative standing in the organization: Member, Developer, Admin or Owner. It decides who can install, deploy and manage, not which tools someone may call.
The person who answers for an agent and every grant it holds. If they can no longer be accountable, the agent is frozen until someone else is named. See People and agents.
The dashboard's record of tool calls: every call through the gateway, allowed or refused. See Reading the audit log.
A non-human caller with its own identity, its own grants and its own credential, created under Settings → Agents. Use one for CI jobs, bots and anything else that runs without a person at the keyboard.
An agent's client ID and client secret. It is exchanged for a token that lives five minutes. An agent can hold two at once, so a credential can be rotated without downtime.
The list of hosts a server Statio runs may connect to. Everything else is refused. See Outbound control.
A credential for automating the control plane: deploys, the registry API, CI pipelines. It acts as the person who created it. API keys cannot call tools.
The dashboard's record of changes: servers, deployments, credentials, keys, agents and access, with who made each one.
The list of ready-made MCP servers you can install in one step. A catalog server is either run by Statio or hosted by its vendor.
The secret an MCP server needs for the API it wraps, such as a Stripe key or a GitHub token. Also called the upstream credential.
Where credentials are kept, encrypted at rest. A value goes in once and comes out only inside the gateway, at the moment a call is forwarded. No API returns it. See Credentials.
A rule that removes one tool from one person. A person's own deny wins over a grant they get through a team.
A signature a person's client adds to each request, made with a key held on their enrolled device. It means a stolen token is not enough on its own.
Outbound traffic from an MCP server: the connections it opens to the internet. Statio controls it with an allowlist enforced outside the server's container. Also called outbound control.
An MCP server you host yourself and connect to Statio by URL. Statio governs who may call it and with which credential; where it sends traffic is up to you.
The only address your clients and agents talk to. It checks who is calling, whether they may use the tool, injects the credential, forwards the call and records it. See What happens on every call.
Permission to call tools. A grant on a server covers every tool on it; a grant on a tool covers that tool alone. Nothing is granted by default.
An MCP server Statio builds and runs for you, generated from your OpenAPI spec or run from your own image.
The process on your machine, at 127.0.0.1:7777, that your clients connect
to. It holds your sign-in and attaches a fresh token to each request, so no key
is written into a client's config. Run by the desktop app or mcphub serve.
The Model Context Protocol, the open standard for how AI clients call tools. See What is MCP?.
Statio's command-line tool. It signs you or an agent in, runs the local proxy, writes client configs and scans for shadow MCP servers.
Your company's space in Statio. Servers, credentials, agents and the audit record all belong to it, not to the person who created them.
A human member of the organization, calling tools from a client on an enrolled device.
Whoever a call is made as, and whose grants are checked: a person or an agent.
An MCP server: a service that wraps an API and exposes it as tools. In Statio it is hosted, installed from the catalog, or external.
An MCP server someone configured on their own machine without review. mcphub scan and the desktop app find them. See
Find shadow MCP servers.
The secret Statio signs webhook deliveries with, so your endpoint can check they came from Statio. It is shown once.
A group of people. A grant to a team reaches every member, and leaving the team removes it.
One function an MCP server exposes, such as search_issues or
create_release. Permissions are decided per tool.
A catalog server that runs on the vendor's own MCP endpoint, such as Linear. Statio connects you to it, usually with OAuth, and still checks permissions and records every call.
An HTTPS endpoint you run that receives Statio's audit records and tool calls as signed events, on Business and Enterprise.