
Utility Network Mcp
io.github.sgdev279Published by GitHub account sgdev279v0.2.0Updated Oct 24, 2026
Esri ArcGIS Utility Network tools: trace, subnetworks, dirty areas, associations
Overview
Local MCP server exposing Esri ArcGIS Utility Network operations — traces, subnetworks, dirty areas and associations — to an assistant.
- What you can do
- Run network traces and inspect subnetworks on an ArcGIS Utility Network feature service.
- Review dirty areas and associations between network features.
- Optionally validate topology and update subnetworks when writes are explicitly enabled.
- When to use it
- Useful when you work with Esri ArcGIS Utility Network data and want an assistant to run traces, check subnetworks, dirty areas or associations without leaving the chat. It is aimed at GIS analysts and utility network administrators rather than general-purpose tasks.
- Requirements
- Runs locally as a Python package launched with uvx (stdio transport), desktop only. Needs UN_FEATURE_SERVICE_URL, plus credentials: a pre-issued token in UN_TOKEN, or portal username/password (UN_PORTAL_URL, UN_USERNAME, UN_PASSWORD), or OAuth client credentials (UN_CLIENT_ID, UN_CLIENT_SECRET). Network access to the ArcGIS portal or service is required.
Installation
In SourceWeft
- Open Utility Network Mcp in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
This repository has no README.
Tools
0Version history
2- v0.2.0LatestSep 29, 2026
- v0.1.0Sep 28, 2026
Score
35% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- License10 pts