Skip to main content

Extend MCP for ArcGIS Enterprise

You can extend MCP for ArcGIS Enterprise with custom tools that support your organization's workflows. Custom tools let AI applications and agents perform operations beyond those provided by the built-in tools.

ArcGIS Enterprise provides two ways to add custom MCP tools:

  • Expose a web tool—Tag the web tool item of a published geoprocessing service for MCP so that it is available as a custom MCP tool.

  • Develop a Java-based tool—Develop tool logic in Java and deploy it as an .mcp package.

Choose an approach based on the operation you want to expose, your existing implementation, and the development skills available in your organization.

Choose an approach

Consideration Web tools Java-based tools
Primary use GIS analysis and workflows that can be implemented through geoprocessing. Business or organizational workflows that require custom application logic or integration with other systems.
Implementation Publish a geoprocessing service, and share it to your portal as a web tool. Develop the tool in Java using the ArcGIS Enterprise SDK.
Deployment Tag the web tool item with mcp. Package the implementation as an .mcp file and deploy it to ArcGIS Enterprise.
Reuse Reuse existing geoprocessing workflows. Implement logic tailored to the systems and processes involved.
Limits The default catalog includes up to 20 web tools, the most recently modified ones. Custom catalogs have no limit. Up to 50 Java-based tools can be registered.

These are guidelines rather than strict boundaries. A business workflow may include geoprocessing, and a Java-based tool may use GIS capabilities. Choose the approach that best fits the operation and how it will be maintained.

Expose web tools as custom MCP tools

Expose a web tool when the operation is implemented as a geoprocessing workflow, such as spatial analysis or data processing. You tag the web tool item with mcp, and it becomes available to AI applications as a custom MCP tool without custom MCP code.

For instructions, see Expose a web tool as a custom MCP tool.

Develop Java-based custom MCP tools

Use Java-based custom MCP tools when you need custom logic for a business or organizational workflow. This approach is useful when the operation involves application behavior or integration with systems beyond an existing geoprocessing workflow.

For example, a custom tool could get an asset's maintenance history from an organizational system, or combine information from several systems to support a work-order process.

Note:

These examples describe functionality you can develop. They are not built-in capabilities.

The general workflow is as follows:

  1. Define the operation and the inputs and outputs the tool requires.

  2. Develop the tool logic in Java.

  3. Package the implementation as an .mcp file.

  4. Deploy and register the package with ArcGIS Enterprise using the SDK instructions.

  5. Verify that the tool is available and behaves as expected.

Java-based tools registered with ArcGIS Enterprise are included in the default catalog. Up to 50 Java-based tools can be registered. Registration of any additional tool is rejected. A Java-based tool with the same name as an already registered Java-based tool is also rejected.

For development, packaging, and deployment instructions, see the ArcGIS Enterprise SDK MCP guide.

Design tools for their intended workflows

For either approach, give each tool a clear purpose. Provide descriptions that explain when to use it, the inputs it accepts, and the results it returns.

As you build and describe each tool, do the following:

  • Give each tool a name that is unique across built-in tools, web tools, and Java-based tools. For details, see Tool name conflicts.

  • Define input requirements, accepted values, and relevant units.

  • Explain whether an operation reads information or changes data.

  • Return results and errors that help the application understand the outcome.

  • Test with the permissions and credentials intended for the workflow.

  • Document dependencies on other services or organizational systems.

For Java-based integrations, determine how access to external systems is authenticated and authorized. For web tools, see Describe the web tool and its tasks.

Organize custom tools into catalogs

Starting with ArcGIS Enterprise 12.2, administrators can combine built-in tools and custom MCP tools in custom catalogs that support specific workflows. For instructions, see Manage MCP catalogs.