pulsemcp verified Safe content atomic mcp-remote

ArcGIS Pro

ArcGIS Pro MCP server by nicogis that enables AI assistants to interact with ArcGIS Pro desktop GIS software through a bridge architecture consisting of a .NET add-in running inside ArcGIS Pro and a separate MCP server process that communicates via inter-process communication. The implementation uses named pipes or similar IPC mechanisms to allow the MCP server to execute GIS operations, access map data, and control ArcGIS Pro functionality from external applications while maintaining the full desktop GIS environment. Built with C# for the ArcGIS Pro add-in component and .NET for the MCP server, this architecture enables AI assistants to perform spatial analysis, map creation, and GIS workflows without requiring direct API access, making it valuable for geospatial professionals who need conversational access to desktop GIS capabilities and automated spatial data processing tasks.

Cognium trust score

99%

Tier

Verified

Composite of vulnerability cleanliness, spec conformance, provenance, stability, and usage signals — scanned and weighted by Cognium. Human and agent signals are tracked separately. Last scanned 2026-09-19.

Scan details: Circle-IR · 2026-09-19 · Appeal

View full trust & usage report →

Metadata

Version: 1.0.0
Skill type: atomic
Execution layer: mcp-remote
Category: maps-location
Source: PulseMCP
Repository: github.com/nicogis/mcp-server-arcgis-pro-addin
Author type: human
Last scanned: 2026-09-19
Updated: 2026-09-19

View source Find related skills

MCP

Resolve ArcGIS Pro from your agent

Streamable HTTP transport at https://api.skillsregistry.net/mcp. No auth for read tools. Discovery: .well-known/mcp.json.

One command in your shell — Claude Code wires it up and verifies the connection. Run /mcp in any session to confirm.

claude mcp add --transport http --scope user skillsregistry https://api.skillsregistry.net/mcp

Swap --scope user for --scope project to commit it to .mcp.json.

Your client Same endpoint everywhere; only the config key differs. The full list is in the descriptor.

Claude Desktop · Settings → Connectors → Add custom connector

https://api.skillsregistry.net/mcp

Paste the URL as the connector endpoint. No authentication.

ChatGPT · Settings → Connectors → Create (developer mode) → MCP server URL

https://api.skillsregistry.net/mcp

Authentication: none. Works in chat and deep research — the server exposes the connector search and fetch tools.

Codex CLI · ~/.codex/config.toml

[mcp_servers.skillsregistry]
url = "https://api.skillsregistry.net/mcp"