Server Management
Approve which MCP servers your organization can use in Gateways and Deployments.
For the gateway as an administrator configures it — access control, visibility, observability and security posture — see MCP Gateway under Secure.
Server Management is the tenant-wide approval layer for MCP servers. It decides which servers show up when someone builds a Gateway or Deployment, for everyone in your organization. Find it at https://airia.ai/settings/mcp-servers.
The list combines two sources: Airia's built-in server catalogue and any custom servers your organization has added.
Server Management controls availability, not connection. It decides which servers your org can use. Configuring an individual server's connection details or credentials happens separately, when you add that server to a Gateway or Deployment.
Default Mode vs. Custom Mode
Your organization is always in one of two modes.
| Default Mode | Custom Mode | |
|---|---|---|
| What's enabled | Every catalogue server marked Available | Only the servers you approve, including Preview servers |
| New GA servers | Become usable automatically as Airia adds them | Stay off until you approve them |
| How you enter it | The starting state | Automatically, the moment you approve or revoke any server |
To discard your custom selections and hand the enabled list back to Airia, use Reset to Default. This re-enables every Available server and drops your custom choices.
Reset to Default is not reversible. It discards every approval and revocation you've made. Confirm your selections before you use it.
The server list
Each row is a single server, from either the catalogue or your custom servers.
| Column | What it shows |
|---|---|
| Server | Icon, name, status badge, and description. The header also shows how many servers are enabled out of your total, for example "14 of 1200 servers enabled globally." |
| Category | The server's category, used for filtering. |
| Featured | A star that pins an approved server to the top of server pickers and turns it on by default in users' Dynamic Gateways. Available only after a server is approved, and not shown for custom servers. |
| Status | The Approve / Approved control. This is the main switch that turns a server on or off for your organization. |
Use the search box and the Category, Featured, and Status filters above the table to narrow a long list. Each row has an actions menu for viewing server details, and for custom servers, editing or deleting them.
Server status badges
| Status | Meaning |
|---|---|
Available | Production-ready and fully tested. Stable and recommended for all users. |
Preview | Has not gone through thorough quality testing, but initial testing is promising. |
Coming Soon | An official third-party server that exists but is in active development by the provider. Potentially usable, but server-side bugs are not uncommon. |
Deprecated | Being phased out. |
Custom | A server your organization added itself, rather than one from Airia's catalogue. |
Approve and revoke servers
Approving a server makes it usable in Gateways and Deployments across your organization.
Click Approve on the server's row. The control becomes an Approved badge with a small remove action next to it.
Click the remove action on the Approved badge to make the server unavailable again.
Turn on Bulk Edit to add a checkbox to each row and a bar at the bottom of the screen with Approve servers and Remove approvals actions. Select the servers you want, choose an action, then click Save Changes.
A server that a Gateway or Deployment currently uses can't have its approval removed until you take it out of those Gateways and Deployments first. If you try, Airia shows you exactly which Gateways or Deployments are using it.
Feature servers
Once a server is approved, mark it as Featured with the star icon. Featured servers are pinned near the top of the server picker your users see when building Gateways and Deployments. They also start on by default in each user's Dynamic Gateway, although users can switch them off in MCP Self-Service.
A server must be approved before it can be featured, and featuring is not available for custom servers.
Restricted servers
Some catalogue servers are marked Restricted and aren't visible to every organization by default, similar to an early-access or partner integration.
If Airia has granted you access to a Restricted server, use Add Restricted Server and enter the server's library ID. It then appears in your server list like any other catalogue server. The same dialog removes access when you no longer need it.
Manage custom servers
Custom servers you've added can be edited or deleted from the row's actions menu, unlike catalogue servers.
Deleting a custom server that one or more Gateways currently use checks that usage first and warns you which Gateways will be affected before you proceed. To add a new custom server, see Custom MCP Servers.
Who can access Server Management
Server Management is available to the Platform Admin, Admin, and Security Admin roles. If your organization uses custom roles, access is controlled instead by the dedicated MCP server management permissions assigned to that role.