convez.ai
MCP ServerDevOps & InfraestruturaAvançado
reaatech

MCP Catalog

reaatech/mcp-catalog

Registro centralizado e descoberta dinâmica de servidores MCP para equipes

Ver no GitHub
InicialPluginScore · de 0 a 100

Servidor de registro centralizado para descoberta dinâmica de servidores MCP dentro de organizações. Permite que agentes encontrem, registrem e gerenciem ferramentas disponíveis através de um catálogo unificado com controle de acesso e health-check automático.

Instalação

$npx convez-ai reaatech/mcp-catalog

1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.

Métricas

Estrelas
0
Forks
0
Acompanhando
0
Saúde
57%
Último commit
há 2 meses
Versão
—
Issues abertas
12
Contribuidores
2

Casos de uso

  • Descoberta centralizada de ferramentas MCP em organizações
  • Registro dinâmico e auto-descoberta de servidores MCP via CI/CD
  • Monitoramento de saúde e disponibilidade de servidores MCP
  • Controle de acesso granular a ferramentas por equipe ou função

Veredito

Solução robusta de infraestrutura para organizações que precisam gerenciar múltiplos servidores MCP em escala. Ideal para times com arquiteturas complexas que necessitam descoberta dinâmica, controle de acesso e observabilidade centralizada.

README

A tradução para o português deste README ainda está na fila.

MCP Catalog

A registry server for MCP (Model Context Protocol) server discovery within an organization.

Features

  • Discovery: Find MCP servers by capability
  • Registration: MCP servers self-register or are registered via CI/CD
  • Health Monitoring: Automatic health checks on registered servers
  • Schema Aggregation: Centralized view of all available tools and capabilities
  • Access Control: Fine-grained permissions for who can discover what
  • Meta-Discovery: The catalog itself is exposed as an MCP server

Tech Stack

  • Runtime: Node.js 20+
  • Package Manager: pnpm 9+
  • Language: TypeScript 5.x
  • API Framework: Fastify 4.x with Zod validation
  • Database: PostgreSQL 15+
  • ORM: Drizzle ORM
  • UI: React 18 + Vite + Tailwind CSS
  • Testing: Vitest

Project Structure

mcp-catalog/
├── apps/
│   ├── api/           # Main registry API server
│   ├── web/           # Web UI for browsing/searching
│   └── mcp-server/    # MCP server exposing catalog as tools
├── packages/
│   └── shared/        # Shared types, schemas, and utilities
├── skills/            # Agent skills for development workflows
├── docker-compose.yml # Local PostgreSQL
└── package.json       # pnpm workspace root

Getting Started

Prerequisites

  • Node.js 20+
  • pnpm 9+
  • PostgreSQL 15+ (or use Docker)

Development Setup

# Install dependencies
pnpm install

# Copy environment variables
cp .env.example .env
# Edit .env with your configuration

# Start PostgreSQL (using Docker)
docker-compose up -d postgres

# Run database migrations
pnpm db:migrate

# Seed development data
pnpm db:seed

# Start development servers
pnpm dev

Available Scripts

# Root level
pnpm dev              # Start all services in development mode
pnpm build            # Build all services
pnpm test             # Run all tests
pnpm lint             # Run linters
pnpm format           # Format code with Prettier

# API
pnpm -F api dev       # Start API in development mode
pnpm -F api test      # Run API tests
pnpm -F api db:migrate # Run database migrations

# Web
pnpm -F web dev       # Start web UI in development mode

# MCP Server
pnpm -F mcp-server dev # Start MCP server

API Documentation

Once the API is running, access the interactive documentation at: http://localhost:3000/documentation

Security Notes

  • JWT_SECRET is required and must be at least 32 characters. The API refuses to start without it. Generate one with: node -e "console.log(require('crypto').randomBytes(32).toString('hex'))"
  • docker-compose.yml ships with a hard-coded local Postgres password (mcp_catalog) intended only for development on a developer machine. For any shared or production deployment, override POSTGRES_PASSWORD and the DATABASE_URL via .env, a secret manager, or a separate compose override — and never expose port 5432 outside the internal network.
  • Passwords are hashed with bcrypt; API keys are issued with a random 32-byte body and a non-secret prefix so lookup stays O(1).
  • In NODE_ENV=production the health checker refuses to probe loopback, private, link-local, or multicast addresses to mitigate SSRF from a malicious server registration.

Development Phases

See DEV_PLAN.md for the full development roadmap.

Contributing

See CONTRIBUTING.md and AGENTS.md for development guidelines.

License

MIT

Ver o original no GitHub

Bom para

Relacionados