Blue Bridge MCP Server

Most cloud and infrastructure work still happens through a UI a human drives. Blue Bridge MCP server moves it into the conversation instead. Sample prompts and recipes for using Model Context Protocol (MCP) server to query and manage Azure resources — scenarios include Azure Managed Grafana, Azure Data Explorer (Kusto), Azure Resource Graph, Azure Resource Manager and more.

Getting it running

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

The tools it exposes

The server publishes 5 tools. What each one is for:

• Variable — Purpose
• AzureManagedGrafanaEndpoint — Azure Managed Grafana endpoint URL
• KustoUri — Azure Data Explorer (Kusto) cluster URI
• UseManagedIdentity — Set to true to use managed identity
• ManagedIdentityClientId — Client ID of the managed identity to use

Things to watch

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

How it compares

Among the cloud and infrastructure options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Blue Bridge's toolset — Variable, AzureManagedGrafanaEndpoint, KustoUri and 2 more — is a fair guide to whether it matches your workflow. It is maintained by Azure; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Blue Bridge's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.