Evaluate your organization's needs
Before you implement MCP for ArcGIS Enterprise, identify how AI applications and agents will help people use your organization's GIS content and capabilities. Your workflows, users, content, and security requirements should guide your choice of tools, authentication techniques, and MCP clients.
Planning requires input from the people who will use the workflows, the owners of the relevant GIS content, and the administrators responsible for ArcGIS Enterprise and AI applications. Work together to define an initial scope, assign responsibilities, and determine how you will evaluate results.
Identify users and workflows
Start with specific tasks that people need to complete. Describe the expected outcome, the information required, and the GIS operations involved.
For example, users may need to do the following:
Find maps and layers relevant to a project.
Get information about assets within an area.
Display query results on a map.
Find locations or calculate routes.
Run an established geoprocessing workflow.
Combine GIS information with information from another organizational system.
For each workflow, identify who will use it and how often. Analysts using a desktop AI assistant, developers building agents, and staff using an organizational application may have different connection and access requirements.
Consider whether users understand the underlying GIS operations or need the AI application to help them select appropriate data and tools. Define what a successful response should contain. A request to find a map may require links to relevant items, while an analysis request may require results, an explanation of the method, and identification of the source data.
Begin with a manageable set of workflows whose results you can verify.
Review your ArcGIS Enterprise version
MCP for ArcGIS Enterprise supports specific ArcGIS Enterprise versions, and some capabilities depend on the version you use:
ArcGIS Enterprise 12.2 and later—The default catalog is available only after an administrator enables external AI client access. Administrators can also create custom catalogs.
ArcGIS Enterprise 12.1, 11.5, 11.3, and 11.1—The default catalog is available after MCP Services for ArcGIS Enterprise are installed, without the need for a separate enablement step. Custom catalogs are not available.
Assess your content
Identify the content that your workflows need AI applications to discover and use. For each item, review the following:
Discoverability—Items must have the
mcptag to be found through Search Portal Content.Descriptions—Titles, summaries, and descriptions help AI applications select the right item.
Sharing—Items must be shared with the users or credentials that will use them.
Budget time to prepare that content, and assign item owners to maintain it. For guidance, see Prepare your content for use with MCP.
Plan authentication and access
Decide whether access should follow an individual user's permissions or the access configured for a credential, and confirm that your deployment version and MCP clients support the technique. Assign responsibility for creating, storing, replacing, and revoking credentials.
For a comparison of techniques, see Select an authentication technique.
Evaluate clients and connectivity
Choose MCP clients that fit the intended users and workflows, and that support your authentication technique and tool approval requirements. Each client must support remote MCP servers that use Streamable HTTP. If you plan to use OAuth 2.0, the client must accept manual configuration, because Dynamic Client Registration (RFC 7591) is not supported.
Verify that the environment making the connection, which may be a cloud-hosted service, can reach your deployment.
For connection guidance, see Connect from MCP clients.
Determine tool requirements
Compare your intended workflows with the tools available in the default catalog. The default catalog contains the following:
Built-in tools—Tools for content and data, mapping, location services, and geoprocessing. For details, see Default MCP catalog overview.
Custom MCP tools—Tools that your organization adds to support its own workflows.
Identify which workflows the built-in tools support and which require custom MCP tools. You can add custom MCP tools to the default catalog in the following ways:
Expose a portal web tool as a custom MCP tool—Tag a web tool item in your portal for MCP to make its geoprocessing service available as a custom MCP tool. For details, see Expose a web tool as a custom MCP tool.
Develop a new MCP tool—Develop Java-based tools for business logic or integrations with other systems. For details, see Develop Java-based custom MCP tools.
To compare the two approaches, see Extend MCP for ArcGIS Enterprise.
For example, a site suitability workflow may combine content search and data queries with a geoprocessing service that applies your organization's analysis criteria.
Consider the dependencies of each workflow, including required services, data sources, and supporting tools. For longer-running analysis, determine how users should get progress information and results.
Starting with ArcGIS Enterprise 12.2, administrators can also group selected tools into custom catalogs for specific workflows or audiences. For details, see Manage MCP catalogs.
Establish security and governance requirements
Review your organization's policies for AI applications and for sharing information with AI services. Results returned by tools are passed to the AI application, which may send them to an AI model provider. Review how those applications and services process and retain information, and confirm that this handling is appropriate for your content.
Determine which operations the workflows should perform and where users need to review or approve an action. For tools that modify data or trigger business processes, identify the expected effects, and verify that the client provides the controls your organization requires.
Also decide the following:
Who can create catalogs and expose custom tools
How access and credentials will be reviewed
How activity will be investigated, including through ArcGIS Server logs
Who is responsible for reviewing results before they inform decisions
GIS tools return data and analysis outputs, while an AI application may add explanations or conclusions. Users should be able to distinguish the source results from the application's interpretation, and confirm that the data and method are appropriate for the decision.
Plan operations and maintenance
Plan installation, removal, and updates around the availability requirements of your hosting server and connected applications. Review the procedures for your operating system to identify service restarts and periods when MCP access will be unavailable. Schedule maintenance, and notify affected users as appropriate.
MCP Services for ArcGIS Enterprise have a release cycle independent of ArcGIS Enterprise. Decide how you will evaluate and adopt new releases. Also include uninstalling and reinstalling MCP Services for ArcGIS Enterprise in your ArcGIS Enterprise upgrade plan. For details, see Upgrade MCP Services for ArcGIS Enterprise.
Test changes in a development or staging environment where practical, especially when you introduce custom tools or change catalogs. Verify representative workflows after updates to services, content, credentials, or client configurations.
For diagnostics, see Troubleshoot MCP for ArcGIS Enterprise.