Azure Topology Graph MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DEFAULT_RG | Yes | Default resource group name | |
| DEFAULT_REGION | Yes | Default Azure region | |
| AZURE_CLIENT_ID | Yes | Your Azure service principal client ID | |
| AZURE_TENANT_ID | Yes | Your Azure tenant ID | |
| SUBSCRIPTION_IDS | Yes | Comma-separated list of Azure subscription IDs to query | |
| AZURE_CLIENT_SECRET | Yes | Your Azure service principal client secret | |
| NETWORK_WATCHER_NAME | Yes | Name of the Network Watcher instance |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_resourcesC | Search Azure resources by name, type, or other properties |
| get_resourceB | Get detailed information about a specific Azure resource |
| get_neighborsC | Get resources connected to a specific resource |
| find_pathC | Find connection path between two Azure resources |
| export_topologyC | Export the complete topology graph |
| refresh_topologyB | Refresh the topology cache by re-querying Azure |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool has a clearly distinct purpose: export_topology for full graph export, find_path for pathfinding between resources, get_neighbors for adjacency queries, get_resource for detailed resource info, refresh_topology for cache updates, and search_resources for filtering. No ambiguity exists as they target different operations on Azure topology data.
All tools follow a consistent verb_noun pattern with clear, descriptive names (e.g., export_topology, find_path, get_neighbors). The naming is uniform across all six tools, using lowercase with underscores, making them predictable and easy to understand.
With 6 tools, the server is well-scoped for managing Azure topology graphs. Each tool serves a specific, non-redundant function, covering key operations like querying, searching, pathfinding, and cache management without being overly sparse or bloated.
The toolset provides strong coverage for querying and analyzing Azure topology, including CRUD-like operations (get, search, refresh) and graph-specific functions (export, find_path, get_neighbors). A minor gap might be the lack of tools for modifying or annotating the topology, but core workflows are well-supported.