|
| 1 | +--- |
| 2 | +title: Expose REST API in API Management as MCP server | Microsoft Docs |
| 3 | +description: Learn how to... |
| 4 | +author: dlepow |
| 5 | + |
| 6 | +ms.service: azure-api-management |
| 7 | +ms.topic: how-to |
| 8 | +ms.date: 05/05/2025 |
| 9 | +ms.author: danlep |
| 10 | +--- |
| 11 | +# Expose REST API in API Management as an MCP server |
| 12 | + |
| 13 | +[!INCLUDE [api-management-availability-all-tiers](../../includes/api-management-availability-all-tiers.md)] |
| 14 | + |
| 15 | +Intro |
| 16 | + |
| 17 | +> [!NOTE] |
| 18 | +> Only the API definition can be exported directly from API Management to Postman. Other information such as policies or subscription keys isn't exported. |
| 19 | +
|
| 20 | +## Prerequisites |
| 21 | + |
| 22 | ++ Complete the following quickstart: [Create an Azure API Management instance](get-started-create-service-instance.md). |
| 23 | ++ Make sure that your instance manages a REST API that you'd like to expose as an MCP serer. |
| 24 | + |
| 25 | + > [!NOTE] |
| 26 | + > You can only expose HTTP APIs from API Management as MCP servers. |
| 27 | ++ To test the MCP server, you can use a tool like [MCP Inspector]( |
| 28 | + |
| 29 | +[!INCLUDE [api-management-navigate-to-instance.md](../../includes/api-management-navigate-to-instance.md)] |
| 30 | + |
| 31 | + |
| 32 | +## Expose API as an MCP server |
| 33 | + |
| 34 | +1. In the portal, under **APIs**, select **MCP Servers** > **+ Create new MCP Server**. |
| 35 | +1. In **API**, select a REST API to expose as an MCP server. |
| 36 | +1. Select one or more **API Operations** to expose as tools. You can select all operations or only specific operations. |
| 37 | +1. Select **Create**. |
| 38 | + |
| 39 | +:::image type="content" source="media/export-rest-mcp-server/create-mcp-server.png" alt-text="Screenshot of creating an MCP server in the portal."::: |
| 40 | + |
| 41 | +The MCP server is created and the API operations are exposed as tools. The MCP server is listed in the **MCP Servers** blade. The **URL** column shows the endpoint of the MCP server that you can call for testing or within a client application. |
| 42 | + |
| 43 | + |
| 44 | +:::image type="content" source="media/export-rest-mcp-server/mcp-server-list.png" alt-text="Screenshot of the MCP server list in the portal."::: |
| 45 | + |
| 46 | + |
| 47 | +## Test and use the MCP server |
| 48 | + |
| 49 | +To verify that the MCP server is working, you can use a tool like MCP Inspector to send requests to the server's `sse` endpoint. |
| 50 | + |
| 51 | + |
| 52 | + |
| 53 | +## Related content |
| 54 | + |
| 55 | +* [Blog: Enhanced API developer experience with the Microsoft-Postman partnership](https://techcommunity.microsoft.com/t5/apps-on-azure-blog/enhanced-api-developer-experience-with-the-microsoft-postman/ba-p/3650304) |
| 56 | +* Learn more about [importing API definitions to Postman](https://learning.postman.com/docs/designing-and-developing-your-api/importing-an-api/). |
| 57 | +* Learn more about [authorizing requests in Postman](https://learning.postman.com/docs/sending-requests/authorization/). |
0 commit comments