Azure Revisor

You run the Azure Revisor MCP Server to enable real-time MCP connections with Azure Revisor as the backend. It exposes an MCP endpoint you can connect to from your MCP client and handles authentication via an Azure PAT. This server is built with TypeScript and is driven by a straightforward install/run flow, making it easy to deploy in development or production environments.

How to use

Connect your MCP client to the Azure Revisor MCP Server using the HTTP MCP URL. You can monitor events and receive updates as they are streamed from the server. If you need to configure authentication or adjust the server behavior, set the necessary environment variables and restart the service.

How to install

Prerequisites for running the server are Node.js v18+ and pnpm.

Step 1: Install dependencies locally for development or deployment.

pnpm install

Step 2: Create a configuration file with your Azure PAT. Place the value in a .env file at the project root.

AZURE_PAT=YOUR_AZURE_PAT

Step 3: Build the server for production.

pnpm run build

Step 4: Start the server in production mode.

pnpm start

Additional sections

Configuration details: The server uses an Azure Personal Access Token (PAT) for authentication. Store the PAT securely in a .env file as AZURE_PAT and ensure it is loaded when the server starts.

Connecting the MCP client: You will point your MCP client to the HTTP endpoint exposed by the server. The example below shows how to wire the MCP URL in the client configuration.

{
  "mcpServers": {
    "azure_revisor": {
      "url": "http://localhost:3000/sse"
    }
  }
}

Notes on running locally: When you start the server with pnpm start, it serves the MCP endpoint at the configured address. Ensure port 3000 (or your chosen port) is accessible from your client and that AZURE_PAT is loaded in the environment before startup.