Skip to main content
Publish your organization’s production MCP servers at a single registry URL. Compatible clients can discover them there, and FastMCP Gateway keeps the catalog current as servers are added, changed, or removed.
Organization MCP registry publication is available on Enterprise. An organization Admin controls publication.
The registry includes every current and future organization server that has a production target. Each catalog entry points to the server’s canonical FastMCP Gateway Streamable HTTP endpoint. A server enters or leaves the catalog when its production target changes. The registry publishes server metadata through an anonymous URL because clients such as GitHub Copilot fetch the catalog without FastMCP Gateway credentials. The URL is opaque, but it is not a secret or an authentication control. Anyone with the URL can read the published server names, descriptions, and endpoint URLs.
Registry publication changes discovery only. The gateway still applies each server’s authentication and authorization settings when a client connects or calls a capability.

​
Publish

Publish the registry when your organization is ready to expose its production server metadata to an external discovery client. The first publication creates an organization URL that remains stable until an Admin regenerates or unpublishes it. The URL uses the following format:
1

Open the Registry page

In FastMCP Gateway, select the organization and open Registry.
2

Open registry settings

Select MCP registry in the page header.
3

Publish the catalog

Review the public metadata notice, then select Publish. FastMCP Gateway immediately projects every server with a production target into the catalog.
4

Copy the URL

Copy the displayed registry URL and store it with the client or company policy that will use it.
Organization Members can view and copy an existing registry URL. Only an organization Admin can publish, regenerate, or unpublish the registry.

​
GitHub Copilot

GitHub Copilot Business and GitHub Copilot Enterprise can use the FastMCP Gateway registry URL for organization or enterprise MCP discovery. The GitHub owner who configures the policy can use the URL that a FastMCP Gateway Admin copied from the Registry page.
1

Open Copilot policies

In the GitHub organization or enterprise settings, open the Copilot policy controls for MCP servers.
2

Enable MCP servers

Enable MCP servers in GitHub Copilot for the applicable organization or enterprise.
3

Set the registry URL

Paste the FastMCP Gateway registry URL into the MCP Registry URL field, then save the policy.
4

Choose an access policy

Use Allow all when the registry is for discovery without a server restriction. Use Registry only when GitHub should apply its registry allowlist policy.
GitHub controls which products and IDE versions support organization registries. See GitHub’s MCP server access guide for the current policy locations, supported plans, and enforcement behavior. A discovered server still needs a valid FastMCP Gateway sign-in or API key when its FastMCP Gateway authentication is enabled. See Connect a client for the server authentication model.

​
URL lifecycle

Regenerate the URL when the current URL was shared outside its intended audience or when you want to replace it as an operational precaution. Regeneration invalidates the previous URL immediately and keeps the same organization registry. Update every client and company policy that used the previous URL. Unpublishing deletes the publication and invalidates its URL immediately. The organization server configuration remains unchanged. Publishing again creates a new registry and a new URL. If the organization moves to a plan without registry publication, FastMCP Gateway suspends anonymous catalog reads and keeps the publication state. Returning to an eligible plan resumes the same URL. An Admin can unpublish the registry while it is suspended.