Skip to main content
Azure API Management can front an external MCP server as a passthrough resource, so your agents call your APIM instance and it forwards to Consensus. Available on Developer, Basic, Basic v2, Standard, Standard v2, Premium, and Premium v2 tiers.

Register the server

1

Create the MCP server

In the Azure portal open your API Management instance, go to APIs › MCP servers, select + Create MCP server, then Expose an existing MCP server.
2

Backend MCP server

3

New MCP server

Set Name to Consensus, a Base path such as consensus, and a Description. Assign Products and select Create.

Authentication

Store your Consensus API key as a secret Named Value (for example consensus-api-key) and add an inbound policy on the MCP server:

Notes

  • A 401 from the backend usually means the Authorization header wasn’t forwarded; check the set-header policy.
  • Don’t read context.Response.Body in MCP server policies; buffering the body breaks the response stream.
  • APIM requires the backend to speak MCP 2025-06-18 or later.
Microsoft docs: Expose an existing MCP server · Secure MCP servers