azure-mcp-inspector

Deploy MCP Inspector to Azure Container Apps with an nginx same-origin proxy.

1|1|Updated Feb 26, 2026

Search Tags:#deployment #azure #cloud #nginx #container-apps #mcp-inspector #same-origin

Ready to run

npx skills add https://github.com/JerryNixon/vslive-2026-las-demos --skill azure-mcp-inspector

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: azure-mcp-inspector
Source: https://github.com/JerryNixon/vslive-2026-las-demos/tree/main/.github/skills/azure-mcp-inspector
Command: npx skills add https://github.com/JerryNixon/vslive-2026-las-demos --skill azure-mcp-inspector

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Deploy MCP Inspector to Azure Container Apps with a built-in same-origin proxy to merge ports and auto-configure the UI.

Core Features & Use Cases

Deploy to Azure Container Apps with a single ingress by merging UI (6274) and proxy (6277) behind port 80 using nginx.
Auto-fill transport type and server URL via a proxied /config endpoint to simplify onboarding.
Preconfigure Inspector UI for cloud deployments and containerized environments.

Quick Start

Deploy the Azure MCP Inspector container and open the inspector URL to complete automatic preconfiguration.

Frequently Asked Questions about azure-mcp-inspector

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I deploy MCP Inspector to Azure Container Apps with a single ingress?▼

You can deploy MCP Inspector to Azure Container Apps by using an nginx-based same-origin proxy that merges the UI port 6274 and proxy port 6277 behind a single port 80 ingress, eliminating the need for multiple exposed ports.

Why does the MCP Inspector UI need a same-origin proxy for cloud deployments?▼

A same-origin proxy is needed to merge UI and proxy traffic onto port 80, preventing cross-origin issues in cloud environments and allowing the Inspector UI to communicate seamlessly with the proxy backend.

Can I auto-configure the MCP Inspector UI server URL for cloud environments?▼

Yes, you can auto-configure the MCP Inspector UI by setting the MCP_SERVER_URL environment variable, which automatically populates the transport type and server URL via a proxied /config endpoint.

Does deploying MCP Inspector to Azure require managing multiple ingress ports?▼

No, deploying MCP Inspector to Azure does not require managing multiple ingress ports because the built-in nginx proxy merges the UI and proxy traffic into a single port 80 ingress for simplified cloud configuration.

What environment variables are supported when containerizing MCP Inspector for Azure?▼

When containerizing MCP Inspector for Azure, the deployment supports the MCP_SERVER_URL environment variable to auto-populate the UI configuration and the ALLOWED_ORIGINS variable to control access.

Best way to preconfigure MCP Inspector UI for a containerized cloud environment?▼

The best way to preconfigure the MCP Inspector UI is deploying it with a same-origin proxy that auto-populates the /config endpoint using MCP_SERVER_URL, simplifying onboarding for containerized cloud environments.