MCP server

The public MCP server provides read-only access to SDK listings, comparisons, documentation, and site pages. No account, API key, or authentication is required.

On this page

Connect

Use https://sdk-sdk.com/mcp as a remote Streamable HTTP server URL. Configure authentication as none. The server supports the 2026-07-28 protocol revision, including stateless requests and server/discover, plus stateless compatibility for older initialization-based clients.

{
  "mcpServers": {
    "sdk-sdk": {
      "type": "http",
      "url": "https://sdk-sdk.com/mcp"
    }
  }
}

Client configuration formats differ. If your client offers a remote-server form, enter the endpoint URL directly. A browser GET of the endpoint returns 405; MCP clients use POST.

Tools

Tool	Purpose
search_site	Search full documentation, SDK records, code examples, and public pages.
list_content	List public content, filtered by kind, with offset pagination.
read_page	Read a complete known page as Markdown, including tables, links, and code.
list_categories	List SDK categories and entry counts.
list_sdks	Filter SDKs by category, kind, or search term.
get_sdk	Retrieve the complete SDK record, sources, caveats, and source review date.
compare_sdks	Compare two or three distinct SDKs.

Every public page is also an MCP resource at its canonical URL. Use resources/list followed by resources/read, or the search and reading tools. Listings and documentation come from the same data as the website. Content changes when the site is deployed; live subscriptions are not provided.

Fair-use limits

120 HTTP requests per minute per IP address, enforced by Vercel before the function runs. Counters are regional rather than a strict global per-IP quota.
On HTTP 429, honor Retry-After when present. Otherwise wait 60 seconds with jitter before retrying. Agents sharing an outbound IP share its allowance.
Maximum request body: 64 KiB. Search queries: 200 characters. List tools: at most 50 items per page. Comparisons: two or three distinct SDKs.
Use search results and pagination to retrieve only what you need, and cache unchanged content within your workflow.

Requests do not execute code samples, call paid provider APIs, fetch arbitrary URLs, or modify site content. Source review dates describe editorial research, not runtime compatibility or a security endorsement.

Protocol and browser clients

Modern requests must include the protocol metadata envelope and matching MCP-Protocol-Version, Mcp-Method, and applicable Mcp-Name headers. The official MCP SDK handles these fields. Malformed or unsupported requests receive protocol errors. Legacy clients can use the initialize handshake on the same endpoint.

Native and server-side agents normally omit Origin and can connect without credentials. Browser requests are limited to this site's origins; local development also permits localhost. Origin and Host validation defend the HTTP endpoint against DNS rebinding. This is not an authentication mechanism.

SDK SDK is an independent discovery hub. Provider examples link to official documentation. App-owned examples are illustrative patterns you can adapt.