mcpField
U
utility-network-mcp

utility-network-mcp

Local
github.com/sgdev279Maps & Travel0Updated 2d ago
Repository

About utility-network-mcp

Esri ArcGIS Utility Network tools: trace, subnetworks, dirty areas, associations

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
  "mcpServers": {
    "sgdev279-utility-network": {
      "command": "uvx",
      "args": [
        "utility-network-mcp"
      ],
      "env": {
        "UN_FEATURE_SERVICE_URL": "<UN_FEATURE_SERVICE_URL>",
        "UN_PORTAL_URL": "<UN_PORTAL_URL>",
        "UN_CLIENT_ID": "<UN_CLIENT_ID>",
        "UN_CLIENT_SECRET": "<UN_CLIENT_SECRET>",
        "UN_USERNAME": "<UN_USERNAME>",
        "UN_PASSWORD": "<UN_PASSWORD>",
        "UN_TOKEN": "<UN_TOKEN>",
        "UN_ALLOW_WRITES": "<UN_ALLOW_WRITES>"
      }
    }
  }
}
Run commanduvx utility-network-mcp
Environment variables to set
UN_FEATURE_SERVICE_URLUtility network FeatureServer URL (ends with /FeatureServer)
UN_PORTAL_URLPortal URL, for username/password or OAuth client-credential auth
UN_CLIENT_IDOAuth app client id (client_credentials)
UN_CLIENT_SECRETSecretOAuth app client secret
UN_USERNAMEPortal username (generateToken)
UN_PASSWORDSecretPortal password
UN_TOKENSecretPre-issued ArcGIS token
UN_ALLOW_WRITESSet to true to enable validate topology / update subnetwork tools

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
pypiutility-network-mcp0.2.0

Tools

No tool list yet

Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.

Details

The maintainer has not added details yet. Check the README in the repository.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.