Azure API Management MCP Server Tools picker shows only first 100 API operations

Question

Azure API Management MCP Server Tools picker shows only first 100 API operations

Errico, Giuliano [COMRES/COLDCHAIN/BLU] 0

We are using Azure API Management to expose a managed REST API as an MCP server.

The issue is not about the number of tools we want to enable. We only want to expose a subset of operations.

The problem is that in the APIM portal, under MCP Servers -> selected server -> Tools, the list of API operations available for selection appears to be capped at 100 items. As a result, we cannot select operations beyond the first 100 shown in the UI, even though the underlying API contains more operations.

Expected behavior: The Tools selection list should show the complete set of API operations for the selected API, or provide paging/search/filtering so that all operations can be selected.

Actual behavior: Only 100 operations are visible/selectable in the Tools blade. Operations beyond that are not shown, so they cannot be selected as MCP tools.

This appears to be a portal/UI limitation or bug in the MCP Server Tools blade, not a desired product constraint for our scenario.

Pravallika KV 12,820 Reputation points Microsoft External Staff Moderator

2026-04-06T00:58:31.6966667+00:00
Hi @Errico, Giuliano [COMRES/COLDCHAIN/BLU],

Thanks for reaching out to Microsoft Q&A.

It is a hard limit: API Management only supports up to 100 operations per API when you expose it as an MCP server. The Tools blade simply caps out at 100 items and doesn’t page or lazy-load beyond that.

Here’s what you can do:

Confirm the count

Double-check how many operations your managed API actually has. If it’s over 100, you’ve hit the “Operations per API” limit.

Workarounds

Split or reorganize your API into multiple smaller APIs, each can expose its own set of up to 100 tools.

Use the search/filter box in the Tools blade to jump directly to a specific operation (even if it’s beyond item 100).

Group related operations under fewer umbrella “tool” operations if that makes sense for your scenario.

Long-term solution

If you truly need more than 100 distinct tools, consider filing a feature request on the Azure feedback forum to ask for paging or an increased limit.

References:

API Management limits: “Operations per API – 100”

Expose REST API in API Management as an MCP server

Troubleshoot MCP-related issues in APIM

Hope this helps!
Pravallika KV 12,820 Reputation points Microsoft External Staff Moderator

2026-04-07T01:46:42.7733333+00:00

Hi @Errico, Giuliano [COMRES/COLDCHAIN/BLU], following up to see if the above provided information was helpful. Please let me know if you have any questions.

1 answer

Your answer

Pravallika KV 12,820 Reputation points Microsoft External Staff Moderator

2026-04-06T00:58:31.6966667+00:00

Hi @Errico, Giuliano [COMRES/COLDCHAIN/BLU],

Thanks for reaching out to Microsoft Q&A.

It is a hard limit: API Management only supports up to 100 operations per API when you expose it as an MCP server. The Tools blade simply caps out at 100 items and doesn’t page or lazy-load beyond that.

Here’s what you can do:

Confirm the count

Double-check how many operations your managed API actually has. If it’s over 100, you’ve hit the “Operations per API” limit.

Workarounds

Split or reorganize your API into multiple smaller APIs, each can expose its own set of up to 100 tools.

Use the search/filter box in the Tools blade to jump directly to a specific operation (even if it’s beyond item 100).

Group related operations under fewer umbrella “tool” operations if that makes sense for your scenario.

Long-term solution

If you truly need more than 100 distinct tools, consider filing a feature request on the Azure feedback forum to ask for paging or an increased limit.

References:

API Management limits: “Operations per API – 100”

Expose REST API in API Management as an MCP server

Troubleshoot MCP-related issues in APIM

Hope this helps!
Pravallika KV 12,820 Reputation points Microsoft External Staff Moderator

2026-04-07T01:46:42.7733333+00:00

Hi @Errico, Giuliano [COMRES/COLDCHAIN/BLU], following up to see if the above provided information was helpful. Please let me know if you have any questions.

Answer 1

The provided documentation for MCP servers in Azure API Management describes how to:

Expose a managed REST API as an MCP server and select operations as tools.
Configure policies and govern MCP servers.

However, it does not document any limit on the number of API operations that can be displayed or selected as tools in the MCP Server Tools blade, nor does it describe UI paging or search behavior, or a 100-operation cap in the portal.

Because this specific behavior (only the first 100 operations visible/selectable in the Tools picker) is not covered in the available documentation, it cannot be confirmed or worked around based on the context. The behavior described aligns with a portal/UI limitation or bug, but that is not stated in the referenced materials.

References:

Share via

Azure API Management MCP Server Tools picker shows only first 100 API operations

1 answer

Your answer