Catalog review

Under the Approval required policy, platform admins decide what reaches the company catalog. Admin › MCP servers lists every team's servers; servers waiting for review come first, under Waiting for approval. Filter by state, pending changes, team, auth mode or the auth provider a server requires. Auditors see the same pages, read-only.

Review a serverCopy Anchor Link

Open a server to see its Overview (URL, health, auth mode, the team's note and the publishing history), its Capabilities with their full definitions and hints, and its Health. Things to look at:

• The capabilities' text. Names, descriptions and schemas are prompts a model will read. Look for instructions aimed at the model, and treat the server's read-only or destructive hints as claims, not facts.
• The endpoint. Is it the team's, and is it healthy? A failing server is flagged.
• Upstream sign-in. For a server in OAuth mode: the authorization server (its host is highlighted when it differs from the server's), the issuer, how the client was registered, the scopes asked for and those the server supports, and whether the resource indicator is sent.
• User authorization. The provider and scopes the server requires, and any per-capability overrides: these decide which of a person's tokens the server will receive.
• Send identity token. Whether people's names, emails and teams go to this server.

Then, on the server's Company catalog card:

• Approve… › Approve and publish: the server is published with its current capabilities approved. It can't be approved until its capabilities have been read from its current URL.
• Reject… › Reject, with a note for the team (required): it stays private to its team, which sees your note and can fix what's needed and ask again.

A published server can be taken off the catalog the same way: rejecting a published server removes it from the catalog and marks it rejected, with your note.

Approve changed capabilitiesCopy Anchor Link

When a published server's capability changes, or a new one appears, it stays out of the catalog until approved, while the rest of the server stays published. The server's pending-changes count and the changes filter find them. On the Capabilities tab, read the new definition and Approve change. Under Self-publish, the team's owners and admins approve their own changes.

What comes back for reviewCopy Anchor Link

Under Approval required, a published server returns to Waiting for review on its own when its URL changes, when it switches to OAuth mode, to another authorization server or to new scopes, or when a capability's user authorization requirement widens. It leaves the catalog until you review it again. The team's note and the history say why it's back.

Every decision is in the audit log (mcp_server.publish, mcp_server.reject, mcp_capability.approve).