Create a custom catalog to control which API operations AI can discover. This guide walks you through the process.
Create a custom catalog when you want to:
If the standard catalog has everything you need with no restrictions, you don’t need a custom catalog.
Select who will own the catalog:
Choose an organization for team catalogs.
Enter a handle for your catalog:
https://mcp.toolcog.com/{owner}/{handle}Examples: internal-apis, payments-stack, client-acme
Choose who can use the catalog:
Private (default)
Public
Click Create Catalog. Your catalog is created but empty—no operations are discoverable yet.
An empty catalog discovers nothing. Add sources to include operations:
See Adding Sources for details.
Your catalog is accessible at:
https://mcp.toolcog.com/{owner}/{handle}For example:
https://mcp.toolcog.com/acme/internal-apisUse this URL in your MCP client configuration.
Configure your MCP client with your catalog’s URL:
{ "mcpServers": { "my-catalog": { "url": "https://mcp.toolcog.com/acme/internal-apis" } }}Ask AI:
“What operations are available in this catalog?”
If AI returns a list of operations, your catalog is working.
Ask AI to find something:
“Find operations for creating customers”
If your catalog includes Stripe and you added customer operations, AI should find them.
Navigate to Operations to see all operations in your catalog, grouped by API.
Navigate to Sources to see where operations come from and manage filters.
Navigate to Settings to:
You can create variants of a catalog for different environments:
https://mcp.toolcog.com/acme/apis # Main varianthttps://mcp.toolcog.com/acme/apis@staging # Staging varianthttps://mcp.toolcog.com/acme/apis@dev # Development variantEach variant can have different sources, filters, and overrides.