Skip to content

Commit 88ce91a

Browse files
author
gitName
committed
wip
1 parent 9aeaeee commit 88ce91a

File tree

2 files changed

+15
-13
lines changed

2 files changed

+15
-13
lines changed

articles/api-management/expose-existing-mcp-server.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -52,7 +52,7 @@ Follow these steps to expose an existing MCP server is API Management:
5252
1. In the [Azure portal](https://portal.azure.com), navigate to your API Management instance.
5353
[!INCLUDE [preview-callout-mcp-feature-flag](includes/preview/preview-callout-mcp-feature-flag.md)]
5454

55-
1. In the left-hand menu, under **APIs**,select **MCP servers** > **+ Create MCP server**.
55+
1. In the left-hand menu, under **APIs**, select **MCP servers** > **+ Create MCP server**.
5656
1. Select **Connect existing MCP server**.
5757
1. In **Backend API**:
5858
1. Enter the existing **MCP server base URL**.

articles/api-management/mcp-server-overview.md

Lines changed: 14 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,10 @@
11
---
22
title: Overview of MCP servers in Azure API Management
3-
description: Learn about Model Context Protocol (MCP) servers in Azure API Management, their architecture, and how they enable AI agents to access external data sources.
3+
description: Learn how Azure API Management enables secure, scalable access to remote MCP servers for AI agents, including architecture and management features.
44
author: dlepow
55
ms.service: azure-api-management
66
ms.topic: concept-article
7-
ms.date: 07/18/2025
7+
ms.date: 07/23/2025
88
ms.author: danlep
99
ms.custom:
1010
---
@@ -39,31 +39,33 @@ The architecture consists of the following components:
3939

4040
The MCP architecture is built on [JSON-RPC 2.0 for messaging](https://modelcontextprotocol.io/docs/concepts/architecture). Communication between clients and servers occurs over defined transport layers, and supports primarily two modes of operation:
4141

42-
* **Remote MCP servers** - MCP clients connect to MCP servers over the internet, establishing a connection using HTTP and server-sent events (SSE), and authorizing the MCP client access to resources on the user's account using OAuth.
42+
* **Remote MCP servers** - Run as independent processes accessible over the internet using HTTP-based transports (like Streamable HTTP), enabling MCP clients to connect to external services and APIs hosted anywhere.
4343

44-
* **Local MCP servers** MCP clients connect to MCP servers on the same machine, using standard input/output as a local transport method.
44+
* **Local MCP servers** MCP clients use standard input/output as a local transport method to connect to MCP servers on the same machine,.
4545

4646
Azure API Management supports the remote MCP server mode, using native features of API Management and [capabilities of the AI gateway](./genai-gateway-capabilities.md).
4747

4848
> [!NOTE]
4949
> MCP server support in API Management is in preview. In preview, API Management supports MCP server tools, but doesn't currently support MCP resources or prompts.
5050
51-
5251
## MCP server endpoints
5352

5453

55-
[TBD]
56-
<!-- Add a section about MCP server endpoints, including SSE and Streamable HTTP endpoints -->
54+
MCP provides the following transport types and typical endpoints for remote servers:
55+
56+
| Transport Type | Endpoints | Notes |
57+
|----------------|----------|-------|
58+
| Streamable HTTP | `/mcp` | Replaces HTTP + SSE transport |
59+
| SSE (server-sent events) | `/sse` - Used to establish SSE connection<br/><br/>`/messages` - Used for bidirectional messaging between MCP client and server | Deprecated as of protocol version `2024-11-05` |
5760

5861
## Expose MCP servers in API Management
5962

6063
API Management supports two ways to expose MCP servers:
6164

62-
* **Expose a REST API as an MCP server** - Use this option to expose any REST API managed in API Management as an MCP server, including APIs imported from Azure resources. The API operations are exposed as tools that can be called by MCP clients. For more information, see [Expose REST API in API Management as MCP server](export-rest-mcp-server.md).
63-
64-
65-
66-
* **Expose an existing MCP server** - Use this option to expose an existing MCP-compatible server, such as a LangChain or LangServe tool server, or an MCP server created in Azure Logic Apps, or Azure Functions. For more information, see [Expose an existing MCP server](expose-existing-mcp-server.md).
65+
| Source | Description |
66+
|-------------------------------------------|-----------------------------------------------------------------------------------------------|
67+
| REST API as MCP server | Expose any REST API managed in API Management as an MCP server, including REST APIs imported from Azure resources. API operations become MCP tools. [Learn more](export-rest-mcp-server.md). |
68+
| Existing MCP server | Expose an MCP-compatible server (for example, LangChain, LangServe, Logic Apps, Azure Functions) via API Management. [Learn more](expose-existing-mcp-server.md). |
6769

6870

6971
## Govern MCP servers

0 commit comments

Comments
 (0)