Server Management is where administrators control which MCP servers are available to their organization. Find it at https://airia.ai/settings/mcp-servers.
This page combines two sources into one list: Airia’s built-in server catalogue and any custom servers your organization has added. It’s the tenant-wide approval layer that decides which servers show up when someone is building a Gateway or Deployment, separate from configuring an individual server’s connection or credentials.
Default Mode vs. Custom Mode
Your organization is always in one of two modes:
- Default Mode automatically enables every catalogue server marked Available. New GA servers Airia adds to the catalogue become usable for your org without any action on your part.
- Custom Mode lets you hand-pick exactly which servers are enabled, including Preview servers you want early access to. Taking any approve or revoke action switches your organization into Custom Mode automatically.
If you want to undo your custom selections and go back to letting Airia manage the enabled list, use Reset to Default. This re-enables every Available server and discards your custom choices, so it’s worth double-checking before you confirm it.
The Server List
Each row represents a server, whether it comes from Airia’s catalogue or was added as a custom server, and shows:
| Column | Description |
|---|
| Server | Icon, name, status badge, and description. The column header also shows how many servers are currently enabled out of your total, e.g. “14 of 1200 servers enabled globally.” |
| Category | The category the server falls under, used for filtering. |
| Featured | A star you can toggle to pin an approved server to the top of the list users see when picking servers. Only available once a server is approved, and not shown for custom servers. |
| Status | An Approve / Approved control, the main switch for turning a server on or off for your organization. |
Server Status Badges
| Status | Meaning |
|---|
| Available | Production-ready and fully tested. Stable and recommended for all users. |
| Preview | Yet to go through thourough quality testing, but initial testing is promising. |
| Coming Soon | An official 3rd party server which 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. |
Approving and Revoking Servers
Click Approve on a row to make that server usable in Gateways and Deployments across your organization. Once approved, the same control becomes an Approved badge with a small remove action next to it if you want to revoke it later.
To act on several servers at once, turn on Bulk Edit. This adds a checkbox to each row and a bar at the bottom of the screen with Approve servers and Remove approvals actions, plus a Save Changes button.
A server currently used by a Gateway or Deployment can’t have its approval removed until it’s taken out of those Gateways and Deployments first. If you try, Airia shows you exactly which Gateways or Deployments are using it so you know what to update.
Featuring Servers
Once a server is approved, you can mark it as Featured using the star icon. Featured servers are pinned near the top of the server picker your users see when building Deployments and Gateways, making your organization’s most important integrations easier to find. A server has to be approved before it can be featured, and this option isn’t available for custom servers.
Restricted Servers
Some servers in Airia’s catalogue are marked Restricted and aren’t visible to every organization by default, similar to an early-access or partner integration. If Airia has given you access to a Restricted server, use Add Restricted Server and enter the server’s library ID to grant your organization access to it. It then shows up in your server list like any other catalogue server. The same dialog lets you remove access if you no longer need it.
Managing Custom Servers
Custom servers you’ve added yourself can be edited or deleted directly from this page’s actions menu, unlike catalogue servers. Deleting a custom server that’s currently used by one or more Gateways checks that usage first and warns you which Gateways will be affected before letting you proceed.
See Custom MCP Servers for how to add a new one.
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 instead controlled by the dedicated MCP server management permissions assigned to that role. 
