Connect from MCP clients
An MCP client allows an AI application or agent to connect to an MCP catalog, discover its tools, and use them to perform GIS tasks.
Many AI applications support MCP, but their connection procedures differ. Depending on the application, you may configure a connection through settings, an administrative interface, a configuration file, or a command-line tool. Authentication options and requirements also vary.
This topic describes the general workflow to connect to MCP for ArcGIS Enterprise. For specific interface labels, configuration formats, and account requirements, see your MCP client's documentation.
Choose an MCP client
MCP for ArcGIS Enterprise supports connections from various MCP clients, such as Microsoft Copilot Studio, Claude Desktop, Kiro, Gemini CLI, ChatGPT, GitHub Copilot, and Goose.
Connections can use API keys, portal tokens, or manually configured OAuth 2.0, depending on the authentication options that the client supports. Before you choose a client, review its documentation to verify that it supports your preferred authentication technique and meets your organization's connection requirements.
When you evaluate a client, consider the following:
Remote connections—The client must support connecting to the MCP catalog URL hosted by your organization, using remote MCP servers over Streamable HTTP. For details, see Protocol version and transport.
Authentication—The client must support the authentication technique that you intend to use.
Network access—The component that makes the connection must be able to reach your ArcGIS Enterprise deployment.
Client administration—Your account or organization may require additional permissions or configuration to enable MCP connections.
Tool controls—Review how the client enables tools and requests approval before running tools.
For guidance on authentication options, see Select an authentication technique.
Before you connect
Verify that MCP Services for ArcGIS Enterprise are installed on the ArcGIS Enterprise hosting server. For ArcGIS Enterprise 12.2 and later, also verify that external AI client access is enabled. Confirm that the user or credential associated with the connection has permission to access the content and services that your workflow requires.
Prepare the following information:
| Information | Description |
|---|---|
| Catalog URL | The endpoint of the MCP catalog that you want to use. |
| Authentication details | An API key, a valid portal token, or the information needed for manual OAuth 2.0 configuration. |
| Required resources | The ArcGIS content and services that your workflow needs. |
| Client configuration instructions | The client provider's instructions for adding a remote MCP connection and configuring authentication. |
Connect to a catalog
The exact steps vary by client, but most connections include the following steps.
Step 1: Add an MCP connection
Use your client's documented procedure to add a remote MCP server connection.
If the client asks for a connection name, use a descriptive name that identifies the deployment and catalog, such as Organization GIS – Default catalog.
Step 2: Specify the catalog URL
For the default catalog, use the following URL format:
https://<domain>/<server-context>/mcp/default
Replace <domain> and <server-context> with the domain and ArcGIS Server context path configured for your deployment.
For a custom catalog, which requires ArcGIS Enterprise 12.2 or later, see Connect to a custom catalog.
Step 3: Configure authentication
Configure a supported authentication technique using the options available in your client.
API key or portal token
Supply the credential through the client's documented authentication method. Some clients provide a credential field, while others require additional connection configuration.
API keys require ArcGIS Enterprise 11.4 or later. To get a portal token, see Generate a portal token.
Note:
A browser URL that contains a token query parameter may not be the format your MCP client requires. Follow the client's instructions for supplying credentials.
OAuth 2.0
Configure OAuth 2.0 manually using the authorization endpoint URL, client ID, and redirect URI. The authorization endpoint uses the following URL format:
https://<domain>/<portal-context>/sharing/rest/oauth2/authorize
Replace <domain> with the domain of your portal and <portal-context> with the name of your portal's Web Adaptor or its context name. The redirect URI must match a redirect URI registered for the OAuth application in your portal.
Dynamic Client Registration (RFC 7591) is not supported, so the client must allow manual configuration. For details, see OAuth 2.0 authentication.
Complete the sign-in and authorization process when you are prompted.
Step 4: Enable the connection and tools
Save the configuration, and complete any steps the client requires to activate the connection.
Review the tools discovered from the catalog. Depending on the client, you may need to enable the connection for a particular conversation, workspace, or agent, and approve access to individual tools.
Step 5: Verify the connection
Ask the application which tools are available from the connection. For example:
What ArcGIS tools can you use?
If the application lists the tools from the catalog, the connection works.
After you prepare your content, test a request that uses content you are authorized to access. For example:
List the hosted feature services I have access to in my ArcGIS Enterprise.
If the client shows tool activity, check that it used a tool from the catalog. Confirm that the results match the request.
A successful connection confirms access to the catalog. Access to individual content items and services still depends on the permissions associated with the connection.
Understand where the connection runs
The application interface may run on your computer while the MCP connection is established by a cloud-hosted service. Consider where the connection originates when you evaluate network access.
If your ArcGIS Enterprise deployment is accessible only through an internal network, verify that the client's connection environment can reach the catalog endpoint. For more information, see Can a client connect to an internal deployment?
Important:
Being able to open the endpoint in your own browser does not necessarily mean that a cloud-hosted client can reach it.
Work with your administrator to determine an appropriate connection arrangement for your deployment.
Troubleshoot a connection
If the connection does not work as expected, see Troubleshoot common symptoms. For client-specific errors and configuration requirements, see the client provider's documentation.
Next steps
After you verify the connection, see Prepare your content for use with MCP to help AI applications discover and use the appropriate GIS content.