toolhive-registry-server

Overview

The ToolHive Registry Server aggregates MCP servers and skills from various sources including Git repos, Kubernetes clusters, upstream registries, and internal APIs into named catalogs with access control and audit trails. It implements the official Model Context Protocol (MCP) Registry API specification, providing JWT-based visibility control, OAuth 2.0/OIDC authentication, role-based administration, and SIEM-compliant audit logging. The server supports five source types (API, Git, File, Managed, Kubernetes) and allows composing catalogs from multiple sources to serve different teams with appropriate visibility rules.

Try asking AI

After installing, here are 5 things you can ask your AI assistant:

• list_servers

  List all MCP servers from a specific registry

  Try:List all servers in the production registryTry:What MCP servers are available in the dev-team registry?
• get_server_versions

  List all versions of a specific MCP server

  Try:Show me all versions of the postgres-serverTry:What versions are available for the github-tools server?
• get_server_version

  Get details of a specific version of an MCP server

  Try:Get details for version 1.2.3 of the file-tools serverTry:Show me the metadata for github-tools version 2.1.0
• list_skills

  List all skills available in a registry

  Try:Show me all skills in the production registryTry:What skills are available in the dev catalog?
• get_skill

  Get details of a specific skill

  Try:Get the latest version of the data-processing skill in the analytics namespaceTry:Show me the skill 'file-operations' in the dev namespace
• list_skill_versions

  List all versions of a specific skill

  Try:Show me all versions of the report-generator skillTry:What versions exist for the image-processor skill?
• get_skill_version

  Get details of a specific version of a skill

  Try:Get details for version 3.1 of the data-transformation skillTry:Show me metadata for the document-generator version 2.0
• list_sources

  List all configured data sources for the registry

  Try:Show me all configured sourcesTry:What Git repositories are being used as sources?
• list_registries

  List all configured registries with their status

  Try:Show all registries and their sync statusTry:What registries are configured in this system?
• publish_entry

  Publish a new server or skill entry to the registry

  Try:Publish a new server entry for our internal toolsTry:Add a new skill to the registry
• delete_entry

  Delete a specific version of a published entry

  Try:Remove version 1.0 of the old-file-serverTry:Delete the outdated skill version 2.3
• update_entry_claims

  Update access claims for a registry entry

  Try:Update access claims for the production database serverTry:Modify visibility rules for the reporting skills

Comparable tools

Installation

task build

# Run with Git source
thv-registry-api serve --config examples/config-git.yaml

# Run with local file
thv-registry-api serve --config examples/config-file.yaml

task docker-up

{
  "mcpServers": {
    "toolhive": {
      "command": "thv-registry-api",
      "args": ["serve", "--config", "path/to/config.yaml"]
    }
  }
}

FAQ

What is the difference between sources and registries?

Sources are connections to where MCP server and skill entries live (Git repos, Kubernetes clusters, etc.). Registries are named catalogs that aggregate one or more sources into a single consumer-facing endpoint with its own access control rules.

Does this server implement the official MCP Registry API specification?

Yes, it fully implements the official MCP Registry API specification (v0.1) for read operations. It also provides additional ToolHive-specific APIs for administration and skills discovery.

Compare toolhive-registry-server with