io.github.muend/arcgis-mcp-bridge
ArcGIS MCP Bridge
Is the ArcGIS MCP Bridge MCP server down? No. It is up and needs env, probed 2026-10-31.
Secure local-first MCP server for licensed ArcGIS Pro and ArcPy on Windows.
needs env probed 2026-11-14 · unchanged since 2026-10-31
MCP error -32000: Connection closed
[11/14/26 08:10:42] INFO Catalog tools registered: 100 (plus 3 server.py:364
core tools).
[- Run it
- uvx arcgis-mcp-bridge@0.6.8 (stdio, probed in a container with the network off)
- Host
- pypi.org
- Repository
- https://github.com/muend/arcgis-mcp-bridge
- Registry
- active, updated 2026-10-02 · registry entry
Compare this server with others.
More servers
Other registry entries on pypi.org, the ones next to this name; all of them.
- io.github.mshegolev/jaeger-mcp · needs mcp<2
- io.github.mshegolev/kibana-mcp · needs mcp<2
- io.github.mshegolev/prometheus-mcp · needs mcp<2
- io.github.mshegolev/sonarqube-mcp · needs mcp<2
- Cue io.github.murtazox04/cue · alive
- PlayStation Network io.github.murzin-ml/mcp-ps-store · alive
- AWS CLI MCP Server io.github.musaddiq-dev/aws-cli-mcp-server · alive
- MySQL MCP Server io.github.musaddiq-dev/mysql-mcp-server · crashed on start
Servers that mention arcgis.
- Arcgis Abbotsford io.github.pipeworx-io/arcgis-abbotsford · not MCP
- Arcgis Adamscounty io.github.pipeworx-io/arcgis-adamscounty · not MCP
- Arcgis Albuquerque io.github.pipeworx-io/arcgis-albuquerque · alive
- Arcgis Allegheny io.github.pipeworx-io/arcgis-allegheny · not MCP
- Arcgis Asheville io.github.pipeworx-io/arcgis-asheville · alive
- Arcgis Aurora io.github.pipeworx-io/arcgis-aurora · not MCP
- Arcgis Austin io.github.pipeworx-io/arcgis-austin · alive
- Arcgis Berkscounty io.github.pipeworx-io/arcgis-berkscounty · alive
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- The server exits because an environment variable is missing. The probe starts the package without secrets. A server that starts without secrets and asks for them on the first tool call is measured.