mcp-registry

Name: mcp-registry
Author: JHSeo-git

@JHSeo-git

Repository

About mcp-registry

A Registry for a MCP Servers

#mcp-registry #server-management #docker

Basic information

Config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "mcp-registry": {
      "command": "docker",
      "args": [
        "compose",
        "up",
        "-d"
      ]
    }
  }
}

Tools

No tools detected

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

What is mcp-registry?

mcp-registry is a web-based registry for MCP (Model Context Protocol) servers. It is designed for developers who need to manage, discover, and deploy MCP servers within a private environment. The server integrates with a private Docker registry (Harbor) and uses PostgreSQL for data storage.

How to use mcp-registry?

Set up prerequisites (Docker, Node, Bun, Harbor), copy the .env.example to .env and fill in database and Docker credentials, then run bun i, docker compose up -d, bun db:m, and bun dev for development. Build with bun run build.

Key features of mcp-registry

Registry for discovering and managing MCP servers
Supports deployment management (screenshots show deployments)
Tool invocation interface (screenshots show tool calls)
Uses PostgreSQL for server metadata and relations
Private Docker registry integration via Harbor

Use cases of mcp-registry

Registering custom MCP servers for internal team use
Discovering available MCP servers in an organization
Managing deployment status of MCP server instances
Testing MCP server tool calls through a web interface

FAQ from mcp-registry

What are the system requirements?

Docker, Node.js, Bun, a private Docker registry (Harbor recommended), and Docker Compose (Orbstack for personal, Rancher Desktop for company use).

How do I configure the database?

Copy .env.example to .env and set POSTGRES_DB, POSTGRES_USER, POSTGRES_PASSWORD, and POSTGRES_URL. After starting Docker Compose, run bun db:m to run migrations.

How do I run the server in development?

After installing dependencies (bun i) and starting Docker Compose, run bun dev. The server will be accessible at the configured port.

Does mcp-registry require a GitHub token?

Yes, GITHUB_TOKEN is needed for git clone operations, but the README notes a TODO to create a project account for this token.

How is authentication handled?

The README does not describe authentication or transport details. Setup uses environment variables for Docker and GitHub credentials, but no user authentication mechanism is documented.