MCP Directory BFF [In Development] / Claude Code v2.1.101

What

A new Backend-for-Frontend endpoint for the MCP server directory, with configurable visibility filters.

Status

Feature-flagged via tengu_mcp_directory_bff (defaults to false)

Details

New https://api.anthropic.com/api/directory/servers endpoint alongside the legacy mcp-registry/v0/servers endpoint
Supports configurable visibility categories: commercial, gsuite, enterprise, health
Uses cursor-based pagination with up to 500 results per page
Controlled by tengu_mcp_directory_visibility flag for the visibility filter list

Evidence

MCP directory BFF (gated by tengu_mcp_directory_bff, search for "api/directory/servers")

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

The build it came inv2.1.101

10 Apr 2026 · 32 entries, this one is #31.

Either side of it

Open the release →

Names in this entry

flagtengu_mcp_directory_bff
Default false. Chooses the endpoint for the list of official MCP server URLs: when on, /api/directory/servers (up to 500 per page, remote servers only); when off, the legacy /mcp-registry/v0/servers (version=latest, 100 per page). Either way at most 20 pages are fetched.
flagtengu_mcp_directory_visibility
Default ["commercial", "gsuite", "enterprise", "health"]. Visibility values sent, comma-joined, as the visibility parameter when fetching the official MCP server directory. A non-array or an array with a non-string entry uses the default; empty strings are dropped, and an empty result skips the fetch and leaves the official URL set empty.

Is this right?