[DOCS] MCP docs omit paginated resource, template, and prompt discovery behavior

Documentation Type

Missing documentation (feature not documented)

Documentation Location

https://code.claude.com/docs/en/mcp

Section/Topic

Use MCP resources and Use MCP prompts as commands — especially discovery behavior for paginated MCP servers and resource templates.

Current Documentation

The page currently says:

## Use MCP resources MCP servers can expose resources that you can reference using @ mentions, similar to how you reference files. Type @ in your prompt to see available resources from all connected MCP servers. Resources appear alongside files in the autocomplete menu. * Claude Code automatically provides tools to list and read MCP resources when servers support them

Later on the same page it says:

## Use MCP prompts as commands MCP servers can expose prompts that become available as commands in Claude Code. Type / to see all available commands, including those from MCP servers. * MCP prompts are dynamically discovered from connected servers

There is no documentation on this page explaining MCP resource templates, or that Claude Code should keep discovering resources, resource templates, and prompts when an MCP server returns multiple pages.

What's Wrong or Missing?

Changelog v2.1.147 says:

Fixed paginating MCP servers dropping resources, templates, and prompts past page 1

The current MCP docs describe resources and prompts as generally available from connected servers, but they never document the expected behavior for paginated capability lists.

That leaves two user-visible gaps:

A. No pagination guidance for non-tool MCP capability discovery

The docs do not tell readers that Claude Code is expected to walk paginated MCP responses for resources and prompts, so items returned after page 1 should still appear in the @ picker or / command discovery.

B. No resource-template documentation

The changelog fix explicitly calls out MCP templates, but the main MCP page does not explain whether resource templates are supported, how they surface in Claude Code, or where users should expect to find them.

Without that documentation, users with larger MCP servers cannot tell whether resources/prompts/templates that only appear on later pages reflect unsupported behavior, a server bug, or a Claude Code bug.

Suggested Improvement

Update https://code.claude.com/docs/en/mcp to document paginated discovery for non-tool MCP capabilities.

Minimum fix:

1. In Use MCP resources, add a note that Claude Code continues through paginated MCP responses so resources and resource templates returned after page 1 remain discoverable.
2. Add a short MCP resource templates subsection that explains whether/how templates surface in Claude Code.
3. In Use MCP prompts as commands, add a note that prompt discovery also traverses paginated MCP responses, so prompts from later pages still appear in / command discovery.
4. Add a brief troubleshooting note telling users that if later-page entries do not appear, they should verify both server pagination behavior and Claude Code version (v2.1.147 or later).

Impact

Medium - Makes feature difficult to understand

Additional Context

Affected Pages:

| Page | Line(s) | Context |
|------|---------|---------|
| https://code.claude.com/docs/en/mcp | 895-933 | Resources section says resources from connected MCP servers appear in @ autocomplete, but does not mention paginated responses or resource templates |
| https://code.claude.com/docs/en/mcp | 1016-1053 | Prompts section says prompts are dynamically discovered, but does not say discovery continues past page 1 |
| https://code.claude.com/docs/en/changelog | 32 | v2.1.147 confirms paginated MCP servers should not drop resources, templates, or prompts past page 1 |

Total scope: 2 pages affected

Version context: Behavior clarified by changelog v2.1.147.