Gateway Directory
See every MCP gateway in your organization, who can reach it, and the apps and tools it exposes, without being able to change any of it.
Gateway Directory is a read-only view of every MCP gateway in your organization. It lists every static gateway and every person's Dynamic Gateway, shows who can reach each one and which AI clients use it, and opens any of them to show the apps, tools and skills it exposes. Open MCP → Gateway Directory, or go to https://airia.ai/gateway/mcp-inventory.
It exists so that reviewing a gateway doesn't require owning it or being able to edit it. A static gateway's configuration is otherwise visible only in the editable gateway editor, and a Dynamic Gateway's toolkits only on its owner's own MCP Self-Service page. Without the directory, reviewing someone else's gateway means granting the reviewer permissions that can also change it, or asking each owner for screenshots.
Gateway Directory is strictly read-only. Every view on this page leaves out the controls that would change something, and the permission that opens it isn't accepted by any action that writes.
Who can reach it
The directory needs the MCP → Gateway Directory → Read permission. Four of the built-in roles hold it:
| Role | Holds Gateway Directory Read |
|---|---|
| Platform Admin | Yes |
| Admin | Yes |
| Security Admin | Yes |
| Read-Only Admin | Yes |
| Project Admin | No |
| End User | No |
A custom role can hold the permission on its own. It grants the whole directory, the list and both detail views, and nothing else: no ability to create, edit, delete, toggle, connect, approve, or change a credential on any gateway, toolkit, tool or setting. Someone without the permission doesn't see the menu entry and can't open the page. See the permissions reference.
If you hold the permission and still don't see Gateway Directory in the menu, it hasn't been made available for your organization yet. Contact your Airia representative.
The directory
The page has two views, Static Gateways and Dynamic Gateways. Pick one with the Gateway type switch at the top. Clicking any row opens that gateway's detail view, and Back returns you to the same view, page and filters you left.
Static Gateways
Admin-built gateways with a name, a scope and a chosen set of apps and tools. Every static gateway in your organization appears here, Tenant and Personal, whoever created it.
| Column | What it shows |
|---|---|
| Name | The gateway's name |
| Scope | Tenant or Personal. Tenant gateways are shared across your organization; a Personal gateway can only be used by the person who owns it. See Tenant vs. Personal Gateway Configs |
| Users | Who can use the gateway: the users and groups it's assigned to, or All users when it isn't restricted |
| Clients | The AI clients, such as Claude or Cursor, connected to the gateway. Hover over or focus a client's logo to see when it was last seen |
To narrow the list:
- Search gateways, apps and tools matches a gateway's name, or any app or tool it includes.
- Scope shows only Tenant or only Personal gateways.
- Assigned user shows the gateways one person can use: the Personal gateways they own, unrestricted Tenant gateways, and Tenant gateways assigned to them or their groups.
- Clients shows only the gateways a given client is connected to.
Dynamic Gateways
Every person has exactly one Dynamic Gateway, which they manage through toolkits and a Radar cache in MCP Self-Service. This view lists one row per person; someone appears here after their first connection.
| Column | What it shows |
|---|---|
| User | The person whose Dynamic Gateway this is |
| Client | The AI clients using that person's Dynamic Gateway. A client drops off after a day without use |
| Radar cache size | How many tools that person's Radar keeps ready for single-call use, and how many of those slots are filled |
To narrow the list:
- Search apps and tools finds the people whose Dynamic Gateway exposes a matching app or tool.
- Search users shows one person's Dynamic Gateway.
- Clients shows only the people a given client is connecting for.
Static gateway detail view
The detail view is the gateway editor shown read-only, so you see the same screen the gateway's owner does rather than a separate summary of it.
| What you see | How it differs from the editor |
|---|---|
| Gateway Settings | Every field, toggle and dropdown is greyed out. Values stay readable; nothing can be changed |
| Applications | The apps the gateway includes, with no control to add one |
| Select Tools | The tools the gateway includes, listed without toggles |
| Select Skills | The skills the gateway includes, listed without toggles. Shown only where an app has skills. See Skills over MCP |
Dynamic Gateway detail view
The detail view is the person's MCP Self-Service page shown read-only and marked View only: their toolkits and their Radar cache.
| What you see | How it differs from MCP Self-Service |
|---|---|
| Toolkits | Every toolkit the person has, their own and those an admin assigned |
| Toolkit and tool toggles | Greyed out. Whether each one is on or off stays readable |
| Inside a toolkit | The same page the owner sees, without the controls to delete the toolkit or add an app to it |
Toggles are greyed out rather than hidden on purpose. Whether a toolkit or tool is switched on is usually the answer a review is looking for, so removing the control would remove that state with it.
A detail view lists only what that gateway includes. If a gateway includes 4 of an app's 40 tools, you see those 4, with no sign of the other 36: the directory holds no credentials for the connected apps, so it never reads an app's full tool list. A gateway that includes every tool of an app shows the tool list the gateway last saw from that app.