Question: Would arcgis-mcp-bridge fit CLI-Hub as a standalone ArcGIS Pro / ArcPy MCP server?

[muend]

Hi CLI-Anything maintainers,

I maintain an open-source project called arcgis-mcp-bridge and wanted to ask whether it would fit CLI-Hub as a standalone external entry before opening a registry PR.

Repo:
https://github.com/muend/arcgis-mcp-bridge

arcgis-mcp-bridge is a local-first MCP server for ArcGIS Pro / ArcPy. It exposes 100 declarative ArcGIS Pro / ArcPy geoprocessing tools to MCP-compatible LLM clients through stdio JSON-RPC.

The project is not a live ArcGIS Pro GUI bridge. Its main focus is secure local geoprocessing through a two-process architecture:

• Layer A: MCP server

  • handles stdio / JSON-RPC
  • exposes tool definitions
  • validates requests with Pydantic contracts
  • applies PathGuard filesystem sandboxing
  • enforces confirmation gates for destructive operations
  • does not import ArcPy

• Layer B: ArcPy worker

  • runs in a separate subprocess
  • uses the configured ArcGIS Pro / ArcPy-capable Python interpreter
  • imports ArcPy only inside the worker boundary
  • executes real geoprocessing locally
  • returns structured results or structured errors

This design is meant to keep the MCP host process separate from the licensed ArcGIS Pro / ArcPy runtime, while giving agents bounded access to local GIS workflows.

Current status:

• PyPI package: arcgis-mcp-bridge
• Entry point: arcgis-mcp-server
• SKILL.md added:
  https://github.com/muend/arcgis-mcp-bridge/blob/main/SKILL.md
• 100 ArcGIS Pro / ArcPy tool definitions
• 10 GIS verticals
• PathGuard filesystem sandboxing
• explicit confirm: true gates for destructive operations
• mocked ArcPy tests for CI without ArcGIS Pro
• Apache-2.0 license

Real geoprocessing requires Windows + licensed ArcGIS Pro. Cloud or hub environments are useful only for discovery, installation metadata, and health_check-style introspection.

I noticed that CLI-Hub already has ArcGIS-related work focused on live ArcGIS Pro interaction. This project is intended to be complementary rather than a replacement: it focuses on headless, isolated, local ArcPy geoprocessing with explicit filesystem safety controls.

Would a standalone registry entry for arcgis-mcp-bridge be appropriate for CLI-Hub?

If yes, I can open a registry-only PR with source_url, install_cmd, entry_point, and skill_md pointing to the standalone repository.

Thanks.