@smithery/registry

Developer-friendly & type-safe Typescript SDK specifically catered to leverage @smithery/registry API.

Summary

Smithery Registry API: Smithery API for managing servers, profiles, and configurations

Table of Contents

• @smithery/registry
  • SDK Installation
  • Requirements
  • SDK Example Usage
  • Available Resources and Operations
  • Standalone functions
  • Pagination
  • 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 @smithery/registry

PNPM

pnpm add @smithery/registry

Bun

bun add @smithery/registry

Yarn

yarn add @smithery/registry

[!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 { SmitheryRegistry } from "@smithery/registry";

const smitheryRegistry = new SmitheryRegistry();

async function run() {
  const result = await smitheryRegistry.system.checkHealth();

  console.log(result);
}

run();

Available Resources and Operations

config

• getStatus - Get configuration status
• get - Get saved user configuration for a server
• update - Save user configuration for a server

profiles

• list - List user profiles
• listServers - List MCP servers for a profile
• addServer - Save a server to a profile
• getServer - Get a profile server
• deleteServer - Delete a profile server

servers

• list - List all servers
• get - Get a server by ID
• configure - Generate server configuration

system

• checkHealth - Health check

uplink

• createToken - Create uplink token

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.

• configGet - Get saved user configuration for a server
• configGetStatus - Get configuration status
• configUpdate - Save user configuration for a server
• profilesAddServer - Save a server to a profile
• profilesDeleteServer - Delete a profile server
• profilesGetServer - Get a profile server
• profilesList - List user profiles
• profilesListServers - List MCP servers for a profile
• serversConfigure - Generate server configuration
• serversGet - Get a server by ID
• serversList - List all servers
• systemCheckHealth - Health check
• uplinkCreateToken - Create uplink token

Pagination

Some of the endpoints in this SDK support pagination. To use pagination, you make your SDK calls as usual, but the returned response object will also be an async iterable that can be consumed using the for await...of syntax.

Here's an example of one such pagination call:

import { SmitheryRegistry } from "@smithery/registry";

const smitheryRegistry = new SmitheryRegistry();

async function run() {
  const result = await smitheryRegistry.servers.list({
    page: 1,
    pageSize: 10,
    q: "search term",
    profile: "my-profile",
  });

  for await (const page of result) {
    console.log(page);
  }
}

run();

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 { SmitheryRegistry } from "@smithery/registry";

const smitheryRegistry = new SmitheryRegistry();

async function run() {
  const result = await smitheryRegistry.system.checkHealth({
    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 { SmitheryRegistry } from "@smithery/registry";

const smitheryRegistry = new SmitheryRegistry({
  retryConfig: {
    strategy: "backoff",
    backoff: {
      initialInterval: 1,
      maxInterval: 50,
      exponent: 1.1,
      maxElapsedTime: 100,
    },
    retryConnectionErrors: false,
  },
});

async function run() {
  const result = await smitheryRegistry.system.checkHealth();

  console.log(result);
}

run();

Error Handling

SmitheryRegistryError 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 | | error.data$ | | Optional. Some errors may contain structured data. See Error Classes. |

Example

import { SmitheryRegistry } from "@smithery/registry";
import * as errors from "@smithery/registry/models/errors";

const smitheryRegistry = new SmitheryRegistry();

async function run() {
  try {
    const result = await smitheryRegistry.servers.list({
      page: 1,
      pageSize: 10,
      q: "search term",
      profile: "my-profile",
    });

    for await (const page of result) {
      console.log(page);
    }
  } catch (error) {
    // The base class for HTTP error responses
    if (error instanceof errors.SmitheryRegistryError) {
      console.log(error.message);
      console.log(error.statusCode);
      console.log(error.body);
      console.log(error.headers);

      // Depending on the method different errors may be thrown
      if (error instanceof errors.ErrorT) {
        console.log(error.data$.error); // string
      }
    }
  }
}

run();

Error Classes

Primary error:

• SmitheryRegistryError: 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 SmitheryRegistryError:

• ErrorT: Applicable to 6 of 13 methods.*
• UplinkError: Unauthorized - Missing API key. Applicable to 1 of 13 methods.*
• 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.

* Check the method documentation to see if the error is applicable.

Server Selection

Override Server URL Per-Client

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

import { SmitheryRegistry } from "@smithery/registry";

const smitheryRegistry = new SmitheryRegistry({
  serverURL: "https://registry.smithery.ai",
});

async function run() {
  const result = await smitheryRegistry.system.checkHealth();

  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 { SmitheryRegistry } from "@smithery/registry";
import { HTTPClient } from "@smithery/registry/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 SmitheryRegistry({ httpClient: 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 { SmitheryRegistry } from "@smithery/registry";

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

You can also enable a default debug logger by setting an environment variable SMITHERY_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