[DOCS] MCP server listings rendered via React component are inaccessible in raw markdown

Documentation Type

Missing documentation (feature not documented)

Documentation Location

• https://code.claude.com/en/mcp - https://docs.anthropic.com/en/docs/agents-and-tools/remote-mcp-servers

Section/Topic

The "Remote MCP servers" section on both pages, which lists available MCP server integrations.

Current Documentation

mcp.md (line 234):

<MCPServersTable platform="claudeCode" />

remote-mcp-servers.md (line 25):

<MCPServersTable platform="mcpConnector" />

The component definition (mcp.md, line 5-6) includes:

export const MCPServersTable = ({platform = "all"}) => {
  const ifYouAreAnAiAgentReadingThisYouShouldInsteadFetch = 'https://api.anthropic.com/mcp-registry/docs';

What's Wrong or Missing?

The list of available MCP servers—critical reference information—is rendered via a React component that fetches data at runtime. This creates accessibility gaps:

1. Raw markdown readers (GitHub, editors, documentation mirrors) see only the component tag
2. Git diffs don't show when servers are added or removed
3. Search tools cannot locate server names in the markdown files
4. Offline documentation doesn't include the server listings
5. Text-based browsers and screen readers may not render the React component

The actual content is dynamically loaded from the MCP registry API, which works well for rendered docs but leaves non-rendered contexts empty.

Suggested Improvement

The component code includes a helpful hint for AI agents pointing to the registry API. Consider extending this accessibility approach to human readers with one of these options:

Option A: Static fallback in markdown

<MCPServersTable platform="claudeCode" />

<details>
<summary>Server list for offline viewing</summary>

| Server | Description |
|--------|-------------|
| Atlassian | Access Jira & Confluence |
| GitHub | GitHub integration |
| Linear | Issue and project management |
| ... | ... |

*For current listings, visit the live documentation or query the [MCP registry API](https://api.anthropic.com/mcp-registry/v0/servers).*
</details>

Option B: Link to the registry API

Add a note like: "For programmatic access or offline reference, the server list is available at https://api.anthropic.com/mcp-registry/v0/servers."

Option C: Document a CLI command

If claude mcp list-available or similar exists, document it as an alternative way to discover available servers.

Impact

High - Prevents users from using a feature

Additional Context

• The component already includes an AI-readable hint (ifYouAreAnAiAgentReadingThisYouShouldInsteadFetch), showing awareness of non-rendered access patterns
• The MCP registry API at https://api.anthropic.com/mcp-registry/v0/servers returns ~50+ servers with metadata
• This pattern (React components in markdown) is common in modern doc sites but creates accessibility gaps for users who browse documentation sources directly