The MCP server registry portal is a web page where people in your organization see the MCP servers they can use and request access to others. You choose which servers the portal lists, and you can make selected servers public so that anyone with the portal URL sees them without signing in. This article is for account owners and administrators. For the end-user view, see Use the MCP server registry portal.
Note: Only account owners and administrators can change these settings, publish servers, and approve requests. Users with Manage or Monitor access see the settings read-only.
Make the registry public
Making the registry public lets anyone with your portal URL, without signing in, see the MCP servers that have Public registry turned on: each server's name, description, connection URL, and its tools, prompts, and resources. It's off by default, and nothing is listed until you also publish a server. Publishing grants no access, because connecting still requires the server's own authentication.
- Go to Account, and then select Company.
- Select AI settings. In a sandbox or other non-production environment, select Company info instead.
- Select Make the registry public, and then select Save.
Note: To stop publishing everything at once, clear Make the registry public and save. Visitors see the sign-in page again. Each server keeps its own Public registry setting, so the same servers are listed again if you make the registry public later.
Publish a server
- Go to AI studio, and then select MCP servers.
- In the Public registry column, turn on the setting for the server.
The change shows on the portal and the registry API the next time they load. To unpublish a server, turn its setting off.
Important: The Public registry column appears only while the registry is public. See Make the registry public. A server that is off can't be published, so turn it on with Off/On first. Turning a published server off removes it from the portal and registry, and turning it back on lists it again with no prompt. Each environment publishes on its own, and legacy sandbox MCP servers can't be published.
Share your registry URLs
Each environment has two URLs, shown in the same settings:
| URL | Who it's for |
| Registry portal | People. Share it with end users and with anyone you want to browse your published servers. It opens in a browser. |
| Registry API | MCP clients and scripts that read a registry, such as the private MCP registry setting in VS Code. See Discover MCP servers with the MCP server registry. |
To copy a URL:
- Open Account > Company > AI settings (or Company info in a non-production environment).
- Select the copy icon beside Registry portal or Registry API.
The portal URL is your MCP account alias, then .registry.mcp. and the integrator.io host you sign in at. For example, if you sign in at integrator.io and your alias is acme-corp-prod, the portal is https://acme-corp-prod.registry.mcp.integrator.io. A sandbox has its own alias and portal.
To see what people see, select View MCP registry on the MCP servers list. The portal opens in a new browser tab with its own sign-in, and it never uses your integrator.io session.
Review access requests
When an end user requests access on the portal, the request appears on the Approvals page and in your header notifications, where you approve or deny it. The account owner also receives an email.
Each request is for one server and one kind of access:
- User access — the person uses the server from their own AI client, signed in as themselves.
- Service token — the person needs a token for a client or agent that can't sign in. Servers that use only Token validation offer this kind only.
To open the requests:
- Go to Account, and then select Users.
- Under End users, select Approvals.
The page lists pending requests with the requester's Email, Access via, Resource (the server), and Requested on, and an Actions column with Approve and Deny. Search finds a request by email or server. When there are no requests, the page reads "No pending access requests."
Approve a user access request
- Select Approve on the request. If the person wrote a message, it's shown at the top of the drawer.
- Choose the capabilities this person can execute.
- Select Approve.
The server is added to the person's end-user access, and it appears in Yours the next time they load the portal. To manage the access through a group instead, add the person to the group from End users.
Approve a service token request
- Select Approve on the request.
- In the drawer, adjust the settings for the new API token, which is scoped to the server: Name, Description, Auto purge token, and a network policy.
- Select Approve, then select Reveal token and copy it.
Send the token to the person through a secure channel outside Celigo, such as your password manager. Celigo never emails it. Manage, revoke, or purge the token with your other API tokens. See Create and manage API and Personal Access tokens.
Deny a request
Select Deny on the request, and then confirm. The request is removed from the queue.
Change the MCP account alias
The alias is part of every MCP server URL, the portal URL, and the registry API URL. When you change it in AI settings and select Save, a dialog warns that existing connections using the old URL break. After you confirm, the old URLs stop working, and clients that hold them must be reconfigured. Share the new portal URL again.
Important: Renaming a server's Relative URI also changes its connection URL and registry name, and the old address isn't redirected. For the rules, see Manage MCP servers.