mcp-registry

mcp-registry

Centralized registry for MCP tools, resources, and prompt templates with JSON schema validation and role-based access control filtering.

Category
访问服务器

README

<div align="center">

<img src="https://raw.githubusercontent.com/Devopstrio/.github/main/assets/Browser_logo.png" height="90"/>

<h1>mcp-registry</h1>

<p><strong>Centralized Model Context Protocol (MCP) Tool, Resource, & Prompt Registry</strong></p>

Build Status Python Version MCP Registry Terraform

</div>


Executive Summary

The mcp-registry repository provides a production-grade, centralized catalog and discovery registry for the Model Context Protocol (MCP). It indexes enterprise MCP tools, resources, and prompt templates with strict JSON schema validation and Role-Based Access Control (RBAC) filtering.

Business Problem

As autonomous AI agents expand across an enterprise, discovering and governing available MCP tools faces operational challenges:

  • Shadow Tool Sprawl: Unmonitored MCP tool servers registered directly by developers introduce unvetted execution endpoints.
  • Malformed Input Payloads: Invalid tool argument schemas lead to runtime agent crashes and unhandled exceptions.
  • Unrestricted Access: Lack of role-based tool discovery allows low-privilege agents to invoke sensitive administrative operations.

Business Value

  • Centralized Governance Catalog: Single source of truth for all approved MCP tools, resource URIs, and prompt templates across the organization.
  • Strict Schema Enforcement: Validates JSON schema definitions during tool registration to prevent invalid parameter calls.
  • Role-Based Access Control (RBAC): Dynamically filters tool discovery queries based on the calling user or agent's authorized roles.

Architecture

Architecture Diagram

High-Level Execution Sequence

graph TD
    Client["AI Agent / Assistant Client"] --> RegistryAPI["MCP Registry REST API"]
    RegistryAPI --> CatalogService["Central Tool Catalog Service"]
    RegistryAPI --> SchemaValidator["JSON Schema Validator"]
    RegistryAPI --> PromptStore["Prompt Template Store"]
    CatalogService --> RBACFilter["Role-Based Access Control Filter"]
    RBACFilter --> FilteredTools["Accessible MCP Tools & Resources"]

Core Components

  • Central Tool Catalog Service (src/mcp_registry/core/catalog.py): Core indexer storing tool definitions, server mappings, and role permissions.
  • JSON Schema Validator (src/mcp_registry/validators/schema_validator.py): Validates input schema definitions during tool registration.
  • Prompt Template Store (src/mcp_registry/services/prompt_store.py): Stores and serves standardized enterprise prompt templates.
  • FastAPI Async API Layer (src/mcp_registry/api/routes.py): REST endpoints for tool registration, RBAC filtering, and prompt listing.

Repository Structure

mcp-registry/
├── .github/              # CI/CD workflows, issue & PR templates, CODEOWNERS
├── architecture/         # Mermaid sequence flow diagrams
├── deployment/           # Kubernetes manifests & Kustomize environment overlays
├── docs/                 # Enterprise architectural, deployment, & operational guides
├── examples/             # Real-world request/response JSON payloads
├── images/               # High-resolution architecture & workflow diagrams
├── src/mcp_registry/     # Python Registry source (api, core, services, validators)
├── terraform/            # Multi-cloud OpenTofu / Terraform IaC modules
├── tests/                # Unit, integration, and API test suites
├── Dockerfile            # Container build specification
├── docker-compose.yml    # Multi-container local orchestration
├── pyproject.toml        # PEP 621 package configuration
└── README.md             # Accelerator documentation manual

Capabilities

  • Tool Registration & Discovery: Endpoint for registering new MCP tools and discovering available schemas.
  • RBAC Tool Filtering: Dynamic filtering based on caller role declarations.
  • Prompt Template Management: Centralized repository for versioned prompt templates.
  • Multi-Cloud IaC Automation: OpenTofu and Terraform modules for AWS VPC, IAM, ECS, and CloudWatch metrics.

Technology Stack

  • Core Registry: Python 3.11+, FastAPI 0.110+, Pydantic v2
  • Infrastructure as Code: OpenTofu 1.8.5 / Terraform 1.6+
  • Containerization: Docker, Docker Compose, Kubernetes 1.28+
  • Quality Assurance: Pytest 8.0+, GitHub Actions CI

Implementation

# Clone repository
git clone https://github.com/Devopstrio/mcp-registry.git
cd mcp-registry

# Install in editable mode
pip install -e .[dev]

# Run automated unit and integration tests
pytest -v tests/

Deployment

OpenTofu / Terraform Provisioning

cd terraform
tofu init
tofu plan
tofu apply -auto-approve

Kubernetes Kustomize Deployment

kubectl apply -k deployment/kubernetes/overlays/prod/

API Reference

  • GET /health — Returns registry health status and version.
  • POST /api/v1/tools/register — Registers an MCP tool with schema validation.
  • POST /api/v1/tools/filter — Returns accessible tools based on RBAC user roles.
  • GET /api/v1/prompts — Lists registered prompt templates.

Examples

Security

Refer to SECURITY.md for reporting security vulnerabilities. The registry enforces schema validation and role-based access filtering.

Observability

The platform exports structured CloudWatch log groups (/aws/mcp-registry/mcp-registry) and metric alarms for invalid schema registration attempts.

Scalability

Horizontal pod autoscaling (HPA) overlays scale registry replicas dynamically based on query volume.

Multi-cloud Strategy

Infrastructure blueprints support AWS ECS/VPC deployment with modular extensions for multi-cluster registry synchronization.

Roadmap

See docs/Roadmap.md for upcoming milestones including active MCP server health probing and semantic versioning support.

Contribution

See CONTRIBUTING.md and CODE_OF_CONDUCT.md for community standards and contribution workflows.


<div align="center"> © 2026 Devopstrio — Engineering the Autonomous Enterprise. </div>

推荐服务器

Baidu Map

Baidu Map

百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。

官方
精选
JavaScript
Playwright MCP Server

Playwright MCP Server

一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。

官方
精选
TypeScript
Magic Component Platform (MCP)

Magic Component Platform (MCP)

一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。

官方
精选
本地
TypeScript
Audiense Insights MCP Server

Audiense Insights MCP Server

通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。

官方
精选
本地
TypeScript
VeyraX

VeyraX

一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。

官方
精选
本地
graphlit-mcp-server

graphlit-mcp-server

模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。

官方
精选
TypeScript
Kagi MCP Server

Kagi MCP Server

一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。

官方
精选
Python
e2b-mcp-server

e2b-mcp-server

使用 MCP 通过 e2b 运行代码。

官方
精选
Neon MCP Server

Neon MCP Server

用于与 Neon 管理 API 和数据库交互的 MCP 服务器

官方
精选
Exa MCP Server

Exa MCP Server

模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。

官方
精选