Summary

Official MCP Registry: A community driven registry service for Model Context Protocol (MCP) servers.

GitHub repository | Documentation

Table of Contents

• SDK Installation
• Requirements
• SDK Example Usage
• Authentication
• Available Resources and Operations
• Standalone functions
• Retries
• Error Handling
• Server Selection
• Custom HTTP Client
• Debugging
• Development
  • Maturity
  • Contributions

SDK Installation

The SDK can be installed with either npm, pnpm, bun or yarn package managers.

NPM

npm add mcp-registry-sdk

PNPM

pnpm add mcp-registry-sdk

Bun

bun add mcp-registry-sdk

Yarn

yarn add mcp-registry-sdk zod

# Note that Yarn does not install peer dependencies automatically. You will need
# to install zod as shown above.

[!NOTE] This package is published with CommonJS and ES Modules (ESM) support.

Requirements

For supported JavaScript runtimes, please consult RUNTIMES.md.

SDK Example Usage

Example

import { McpRegistry } from "mcp-registry-sdk";

const mcpRegistry = new McpRegistry({
  bearer: process.env["MCPREGISTRY_BEARER"] ?? "",
});

async function run() {
  const result = await mcpRegistry.auth.exchangeDnsToken({
    domain: "example.com",
    signedTimestamp: "abcdef1234567890",
    timestamp: "2023-01-01T00:00:00Z",
  });

  console.log(result);
}

run();

Authentication

Per-Client Security Schemes

This SDK supports the following security scheme globally:

| Name | Type | Scheme | Environment Variable | | -------- | ------ | ------- | -------------------- | | bearer | apiKey | API key | MCPREGISTRY_BEARER |

To authenticate with the API the bearer parameter must be set when initializing the SDK client instance. For example:

import { McpRegistry } from "mcp-registry-sdk";

const mcpRegistry = new McpRegistry({
  bearer: process.env["MCPREGISTRY_BEARER"] ?? "",
});

async function run() {
  const result = await mcpRegistry.auth.exchangeDnsToken({
    domain: "example.com",
    signedTimestamp: "abcdef1234567890",
    timestamp: "2023-01-01T00:00:00Z",
  });

  console.log(result);
}

run();

Available Resources and Operations

admin

• editServer - Edit MCP server

auth

• exchangeDnsToken - Exchange DNS signature for Registry JWT
• exchangeGithubToken - Exchange GitHub OAuth access token for Registry JWT
• exchangeGithubOidcToken - Exchange GitHub OIDC token for Registry JWT
• exchangeHttpToken - Exchange HTTP signature for Registry JWT
• exchangeOidcToken - Exchange OIDC ID token for Registry JWT
• oidcCallback - Handle OIDC authorization callback
• oidcStart - Start OIDC authorization flow

health

• get - Health check

ping

• get - Ping

publish

• server - Publish MCP server

servers

• list - List MCP servers
• get - Get MCP server details

Standalone functions

All the methods listed above are available as standalone functions. These functions are ideal for use in applications running in the browser, serverless runtimes or other environments where application bundle size is a primary concern. When using a bundler to build your application, all unused functionality will be either excluded from the final bundle or tree-shaken away.

To read more about standalone functions, check FUNCTIONS.md.

• adminEditServer - Edit MCP server
• authExchangeDnsToken - Exchange DNS signature for Registry JWT
• authExchangeGithubOidcToken - Exchange GitHub OIDC token for Registry JWT
• authExchangeGithubToken - Exchange GitHub OAuth access token for Registry JWT
• authExchangeHttpToken - Exchange HTTP signature for Registry JWT
• authExchangeOidcToken - Exchange OIDC ID token for Registry JWT
• authOidcCallback - Handle OIDC authorization callback
• authOidcStart - Start OIDC authorization flow
• healthGet - Health check
• pingGet - Ping
• publishServer - Publish MCP server
• serversGet - Get MCP server details
• serversList - List MCP servers

Retries

Some of the endpoints in this SDK support retries. If you use the SDK without any configuration, it will fall back to the default retry strategy provided by the API. However, the default retry strategy can be overridden on a per-operation basis, or across the entire SDK.

To change the default retry strategy for a single API call, simply provide a retryConfig object to the call:

import { McpRegistry } from "mcp-registry-sdk";

const mcpRegistry = new McpRegistry({
  bearer: process.env["MCPREGISTRY_BEARER"] ?? "",
});

async function run() {
  const result = await mcpRegistry.auth.exchangeDnsToken({
    domain: "example.com",
    signedTimestamp: "abcdef1234567890",
    timestamp: "2023-01-01T00:00:00Z",
  }, {
    retries: {
      strategy: "backoff",
      backoff: {
        initialInterval: 1,
        maxInterval: 50,
        exponent: 1.1,
        maxElapsedTime: 100,
      },
      retryConnectionErrors: false,
    },
  });

  console.log(result);
}

run();

If you'd like to override the default retry strategy for all operations that support retries, you can provide a retryConfig at SDK initialization:

import { McpRegistry } from "mcp-registry-sdk";

const mcpRegistry = new McpRegistry({
  retryConfig: {
    strategy: "backoff",
    backoff: {
      initialInterval: 1,
      maxInterval: 50,
      exponent: 1.1,
      maxElapsedTime: 100,
    },
    retryConnectionErrors: false,
  },
  bearer: process.env["MCPREGISTRY_BEARER"] ?? "",
});

async function run() {
  const result = await mcpRegistry.auth.exchangeDnsToken({
    domain: "example.com",
    signedTimestamp: "abcdef1234567890",
    timestamp: "2023-01-01T00:00:00Z",
  });

  console.log(result);
}

run();

Error Handling

McpRegistryError is the base class for all HTTP error responses. It has the following properties:

| Property | Type | Description | | ------------------- | ---------- | ------------------------------------------------------ | | error.message | string | Error message | | error.statusCode | number | HTTP response status code eg 404 | | error.headers | Headers | HTTP response headers | | error.body | string | HTTP body. Can be empty string if no body is returned. | | error.rawResponse | Response | Raw HTTP response |

Example

import { McpRegistry } from "mcp-registry-sdk";
import * as errors from "mcp-registry-sdk/models/errors";

const mcpRegistry = new McpRegistry({
  bearer: process.env["MCPREGISTRY_BEARER"] ?? "",
});

async function run() {
  try {
    const result = await mcpRegistry.auth.exchangeDnsToken({
      domain: "example.com",
      signedTimestamp: "abcdef1234567890",
      timestamp: "2023-01-01T00:00:00Z",
    });

    console.log(result);
  } catch (error) {
    if (error instanceof errors.McpRegistryError) {
      console.log(error.message);
      console.log(error.statusCode);
      console.log(error.body);
      console.log(error.headers);
    }
  }
}

run();

Error Classes

Primary error:

• McpRegistryError: The base class for HTTP error responses.

Network errors:

• ConnectionError: HTTP client was unable to make a request to a server.
• RequestTimeoutError: HTTP request timed out due to an AbortSignal signal.
• RequestAbortedError: HTTP request was aborted by the client.
• InvalidRequestError: Any input used to create a request is invalid.
• UnexpectedClientError: Unrecognised or unexpected error.

Inherit from McpRegistryError:

• ResponseValidationError: Type mismatch between the data returned from the server and the structure expected by the SDK. See error.rawValue for the raw value and error.pretty() for a nicely formatted multi-line string.

Server Selection

Select Server by Index

You can override the default server globally by passing a server index to the serverIdx: number optional parameter when initializing the SDK client instance. The selected server will then be used as the default on the operations that use it. This table lists the indexes associated with the available servers:

| # | Server | Description | | --- | -------------------------------------------------- | ----------------- | | 0 | https://registry.modelcontextprotocol.io | Production server | | 1 | https://staging.registry.modelcontextprotocol.io | Staging server |

Example

import { McpRegistry } from "mcp-registry-sdk";

const mcpRegistry = new McpRegistry({
  serverIdx: 1,
  bearer: process.env["MCPREGISTRY_BEARER"] ?? "",
});

async function run() {
  const result = await mcpRegistry.auth.exchangeDnsToken({
    domain: "example.com",
    signedTimestamp: "abcdef1234567890",
    timestamp: "2023-01-01T00:00:00Z",
  });

  console.log(result);
}

run();

Override Server URL Per-Client

The default server can also be overridden globally by passing a URL to the serverURL: string optional parameter when initializing the SDK client instance. For example:

import { McpRegistry } from "mcp-registry-sdk";

const mcpRegistry = new McpRegistry({
  serverURL: "https://staging.registry.modelcontextprotocol.io",
  bearer: process.env["MCPREGISTRY_BEARER"] ?? "",
});

async function run() {
  const result = await mcpRegistry.auth.exchangeDnsToken({
    domain: "example.com",
    signedTimestamp: "abcdef1234567890",
    timestamp: "2023-01-01T00:00:00Z",
  });

  console.log(result);
}

run();

Custom HTTP Client

The TypeScript SDK makes API calls using an HTTPClient that wraps the native Fetch API. This client is a thin wrapper around fetch and provides the ability to attach hooks around the request lifecycle that can be used to modify the request or handle errors and response.

The HTTPClient constructor takes an optional fetcher argument that can be used to integrate a third-party HTTP client or when writing tests to mock out the HTTP client and feed in fixtures.

The following example shows how to use the "beforeRequest" hook to to add a custom header and a timeout to requests and how to use the "requestError" hook to log errors:

import { McpRegistry } from "mcp-registry-sdk";
import { HTTPClient } from "mcp-registry-sdk/lib/http";

const httpClient = new HTTPClient({
  // fetcher takes a function that has the same signature as native `fetch`.
  fetcher: (request) => {
    return fetch(request);
  }
});

httpClient.addHook("beforeRequest", (request) => {
  const nextRequest = new Request(request, {
    signal: request.signal || AbortSignal.timeout(5000)
  });

  nextRequest.headers.set("x-custom-header", "custom value");

  return nextRequest;
});

httpClient.addHook("requestError", (error, request) => {
  console.group("Request Error");
  console.log("Reason:", `${error}`);
  console.log("Endpoint:", `${request.method} ${request.url}`);
  console.groupEnd();
});

const sdk = new McpRegistry({ httpClient });

Debugging

You can setup your SDK to emit debug logs for SDK requests and responses.

You can pass a logger that matches console's interface as an SDK option.

[!WARNING] Beware that debug logging will reveal secrets, like API tokens in headers, in log messages printed to a console or files. It's recommended to use this feature only during local development and not in production.

import { McpRegistry } from "mcp-registry-sdk";

const sdk = new McpRegistry({ debugLogger: console });

You can also enable a default debug logger by setting an environment variable MCPREGISTRY_DEBUG to true.

Development

Maturity

This SDK is in beta, and there may be breaking changes between versions without a major version update. Therefore, we recommend pinning usage to a specific package version. This way, you can install the same version each time without breaking changes unless you are intentionally looking for the latest version.

Contributions

While we value open-source contributions to this SDK, this library is generated programmatically. Any manual changes added to internal files will be overwritten on the next generation. We look forward to hearing your feedback. Feel free to open a PR or an issue with a proof of concept and we'll do our best to include it in a future release.

SDK Created by Speakeasy