Skip to main content

Manage MCP catalogs

Starting with ArcGIS Enterprise 12.2, administrators can create custom MCP catalogs in addition to the default catalog, selecting tools for specific workflows and managing access through item sharing. For an introduction to catalogs, see MCP catalogs.

Default and custom catalogs

Catalog type Availability Contents Endpoint
Default catalog All supported ArcGIS Enterprise versions Built-in tools and custom MCP tools. For details, see Default catalog. /mcp/default
Custom catalog ArcGIS Enterprise 12.2 and later A selected set of tools for a particular workflow, plus the tools that are automatically included in every custom catalog. /mcp/<item-id>

A custom catalog can include any number of web tools tagged for MCP, and up to 50 Java-based custom MCP tools. The default catalog includes only the 20 most recently modified web tools, so use a custom catalog when a workflow needs a web tool that the default catalog does not include.

Each custom catalog is represented by an item of type MCP Catalog. You manage its tool selection on the item page, and you share it using the organization sharing model.

For more information about the default catalog, see Default MCP catalog overview.

Plan a custom catalog

Create a custom catalog when an AI application needs a focused set of tools for a particular purpose.

For example, a site suitability workflow may need tools to find relevant content, inspect layers, query data, and run a specific geoprocessing service. A custom catalog groups these tools under one endpoint, which reduces the number of tools that the application must consider.

When planning a catalog, follow these general guidelines:

  • Identify the workflow and the tools needed to complete it.

  • Decide which users or groups need access.

  • Choose a descriptive name, and explain the catalog's intended purpose.

  • Verify that the intended users have permission to access the underlying content and services.

  • Verify that the selected tools have unique names. If two tools in a custom catalog have the same name, only the tool listed first in the catalog item's data is used. For details, see Tool name conflicts.

Before you begin

Before you create a custom catalog, verify the following:

  • Your deployment uses ArcGIS Enterprise 12.2 or later.

  • MCP Services for ArcGIS Enterprise are installed.

  • External AI client access is turned on in the organization's AI settings.

The External AI client access setting controls access to both the default catalog and custom catalogs. For instructions, see Enable MCP for ArcGIS Enterprise.

Create a custom catalog

Follow these steps to create a custom MCP catalog:

  1. Sign in to your organization as an administrator.

  2. At the top of the site, click Content.

  3. On the My content tab, click New item, and click MCP Catalog.

  4. Under the Catalog details section, provide a catalog name and description.

    The catalog name can contain up to 50 characters, and the catalog description can contain up to 1024 characters.

  5. Under the Catalog components section, select the MCP tools to include in the catalog.

    Note:

    Describe Item, Describe Layer, and Search Portal Content are automatically included in every custom catalog. If the catalog includes a custom MCP tool from a web tool, Get GP Task Definition and Get GP Task Job Status are also included automatically.

  6. Click Create MCP catalog.

    The custom MCP catalog is added to your organization as an item. Custom catalogs are cached to improve performance, so the catalog may take a few minutes to become available.

  7. Share the MCP Catalog item with the intended users and groups.

Sharing a catalog does not grant access to the underlying resources, so review that access separately. For example, sharing a catalog that contains Query Data does not automatically give users access to every feature layer they may try to query.

Connect to a custom catalog

Use the URL available on the custom catalog's item page to configure an MCP client connection. The URL uses the following format:

https://<domain>/<server-context>/mcp/<item-id>

Replace <domain> and <server-context> with the domain and ArcGIS Server context path configured for your deployment. The <item-id> is the custom catalog item's ID.

Follow these steps to connect to a custom catalog:

  1. At the top of the site, click Content.

  2. On the My content tab, click the catalog to open its item page.

  3. Under the Details section, copy the URL in the URL text box.

    Note:

    This URL is different from the URL of the item page.

  4. Use the URL to add an MCP connection in your client.

  5. Configure a supported authentication technique. For more information, see Select an authentication technique and Connect from MCP clients.

  6. Verify that the connection can discover the tools in the catalog.

Edit a custom catalog

Caution:

Removing a tool from a catalog may affect workflows that depend on it.

Follow these steps to edit the list of tools included in a custom catalog:

  1. At the top of the site, click Content.

  2. On the My content tab, click the catalog to open its item page.

  3. Under the Catalog components section, click Edit.

  4. Add or remove tools as needed and click Save.

Custom catalogs are cached to improve performance, so changes may take a few minutes to be reflected. After that time, refresh or reconnect the MCP client as that client requires, and verify the available tools.

If the catalog's purpose has changed, update its description.

Delete a custom catalog

Note:

Before you delete a custom catalog, identify the AI applications or agents that use its endpoint and configure an alternative as needed.

Follow these steps to delete a custom catalog:

  1. At the top of the site, click Content.

  2. On the My content tab, check the box next to the catalog you want to delete and click Delete.

  3. In the Delete item window, click Delete.

The custom catalog is removed, and any AI applications or agents that use its endpoint can no longer connect to it.

Maintain your catalogs

Periodically review custom catalogs to confirm that their tool selection, descriptions, and sharing settings still meet the intended workflow.

When you change a catalog, test a representative request using the identity or credential of an intended user. Verify both tool discovery and access to the resources needed to complete the task.