ToolHive Catalog

v1.0.0Developer Toolsstable

ToolHive's registry catalog of MCP servers

catalogmcpmodel-context-protocolregistry
Share:
22
Stars
0
Downloads
0
Weekly
0/5

What is ToolHive Catalog?

ToolHive Catalog is a Model Context Protocol (MCP) server that allows AI assistants like Claude, Cursor, and VS Code to toolhive's registry catalog of mcp servers

ToolHive's registry catalog of MCP servers

This server falls under the Developer Tools category on MCPgee, the world's largest MCP server directory with 33,000+ servers.

Features

  • ToolHive's registry catalog of MCP servers

Use Cases

Browse and discover available MCP servers.
Access ToolHive's registry of integrated tools.
stacklok

Maintainer

LicenseApache-2.0
Languagego
Versionv1.0.0
UpdatedMay 20, 2026
Statushealthy
Maintenanceactive

Works with

ClaudeOpenAIwindowsmacoslinux

Installation

Manual Installation

npx toolhive-catalog

Configuration

Configuration Details

Config File

claude_desktop_config.json

Performance

Response Metrics

Response Time< 200ms
ThroughputMedium

Resource Usage

Memory UsageLow
CPU UsageLow

How to Set Up and Use ToolHive Catalog

ToolHive Catalog is the official registry of MCP (Model Context Protocol) servers and skills maintained by Stacklok for the ToolHive platform. It provides a structured, community-maintained catalog where each server entry defines how to deploy a containerized or remote MCP server, including environment variables, required permissions, tool names, and provenance metadata. Developers use this catalog to discover, register, and manage MCP servers within the ToolHive ecosystem, which handles container-based MCP server deployment with supply-chain security features like Sigstore provenance.

Prerequisites

  • ToolHive CLI (thv) installed — see https://github.com/stacklok/toolhive for installation instructions
  • Docker or a compatible OCI runtime for running container-based MCP servers
  • Git for contributing new server entries to the catalog
  • An MCP client such as Claude Desktop, Cursor, or VS Code Copilot
1

Browse the catalog

The catalog lives in the registries/toolhive/servers/ directory of the GitHub repository. Each subdirectory contains a server.json file describing one MCP server. Browse or search the repository to discover available servers.

git clone https://github.com/stacklok/toolhive-catalog
ls registries/toolhive/servers/
2

Install a server from the catalog using ToolHive

Use the ToolHive CLI to run an MCP server from the catalog. ToolHive reads the catalog, pulls the OCI container image, and starts the server with the correct environment variables and permissions.

# List available servers in the catalog
thv registry list

# Run a specific server (example: github MCP server)
thv run github
3

Add a new container-based MCP server to the catalog

Create a new folder under registries/toolhive/servers/ using lowercase and hyphens, then add a server.json file conforming to the MCP ServerJSON schema with ToolHive _meta extensions.

mkdir -p registries/toolhive/servers/my-awesome-server
4

Write the server.json file

Create a server.json following the upstream MCP schema plus ToolHive _meta extensions. Specify the OCI image identifier in packages[0].identifier and declare required environment variables.

{
  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
  "name": "io.github.myorg/my-server",
  "description": "What your server does in one sentence",
  "title": "my-server",
  "repository": {
    "url": "https://github.com/myorg/my-server",
    "source": "github"
  },
  "version": "1.0.0",
  "packages": [
    {
      "registryType": "oci",
      "identifier": "ghcr.io/myorg/my-server:v1.0.0",
      "transport": { "type": "stdio" },
      "environmentVariables": [
        {
          "name": "API_KEY",
          "description": "Your API key",
          "isRequired": true,
          "isSecret": true
        }
      ]
    }
  ],
  "_meta": {
    "io.modelcontextprotocol.registry/publisher-provided": {
      "io.github.stacklok": {
        "ghcr.io/myorg/my-server:v1.0.0": {
          "tier": "Community",
          "status": "Active",
          "tags": ["api", "integration"],
          "tools": ["tool_name_1", "tool_name_2"]
        }
      }
    }
  }
}
5

Submit a pull request

Commit your new server.json, push to a fork, and open a pull request against the stacklok/toolhive-catalog repository. The maintainers will review the entry for correctness and security.

git checkout -b add/my-awesome-server
git add registries/toolhive/servers/my-awesome-server/server.json
git commit -m "Add my-awesome-server MCP server"
git push origin add/my-awesome-server

ToolHive Catalog Examples

Client configuration

ToolHive manages the MCP client configuration automatically when you use `thv run`. For manual Claude Desktop configuration, reference the OCI container via a stdio transport wrapper.

{
  "mcpServers": {
    "toolhive-catalog": {
      "command": "thv",
      "args": ["run", "--foreground", "<server-name>"]
    }
  }
}

Prompts to try

Use these with Claude Desktop or another MCP client connected to a ToolHive-managed server from the catalog.

- "List all available MCP servers in the ToolHive catalog"
- "What tools does the github MCP server expose?"
- "Run the fetch MCP server and retrieve the content of https://example.com"
- "Show me servers tagged with 'database' in the ToolHive registry"

Troubleshooting ToolHive Catalog

thv run fails with image pull errors

Ensure Docker is running and you are authenticated to ghcr.io if the image is private. Run `docker pull ghcr.io/myorg/my-server:v1.0.0` manually to diagnose pull issues.

server.json validation errors when contributing to the catalog

Validate your file against the upstream schema at https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json. The _meta extension key must exactly match the packages[0].identifier value (for containers) or remotes[0].url (for remote servers).

MCP client does not see tools from a ToolHive-managed server

Check that the server container started successfully with `thv status`. Verify the transport type is set to 'stdio' in the server.json and that required environment variables (API keys) are passed via `thv run --env KEY=VALUE`.

Frequently Asked Questions about ToolHive Catalog

What is ToolHive Catalog?

ToolHive Catalog is a Model Context Protocol (MCP) server that toolhive's registry catalog of mcp servers It connects AI assistants to external tools and data sources through a standardized interface.

How do I install ToolHive Catalog?

Follow the installation instructions on the ToolHive Catalog GitHub repository. Clone the repo, install dependencies, and add the server config to your AI client.

Which AI clients work with ToolHive Catalog?

ToolHive Catalog works with all major MCP-compatible AI clients including Claude Desktop, Claude Code, Cursor, VS Code (GitHub Copilot), Windsurf, and Cline.

Is ToolHive Catalog free to use?

Yes, ToolHive Catalog is open source and available under the Apache-2.0 license. You can use it freely in both personal and commercial projects.

Browse More Developer Tools MCP Servers

Explore all developer tools servers available in the MCPgee directory. Each server includes setup guides for Claude, Cursor, and VS Code.

Quick Config Preview

{ "mcpServers": { "toolhive-catalog": { "command": "npx", "args": ["-y", "toolhive-catalog"] } } }

Add this to your claude_desktop_config.json or .cursor/mcp.json

Read the full setup guide →

Ready to use ToolHive Catalog?

Browse our complete directory of 33,000+ MCP servers, read setup guides for your editor, and start building with the Model Context Protocol.

33,000+ ServersFree & Open SourceStep-by-Step Guides