MCP Registry

Created By
modelcontextprotocol9 months ago
A community driven registry service for Model Context Protocol (MCP) servers.
Overview

What is MCP Registry?

MCP Registry is a community-driven registry service designed for Model Context Protocol (MCP) servers, providing a centralized repository for managing and discovering various MCP implementations.

How to use MCP Registry?

To use MCP Registry, you can run it locally using Docker or build it directly with Go. The service exposes a RESTful API for managing registry entries.

Key features of MCP Registry?

  • RESTful API for managing MCP registry entries (list, get, create, update, delete)
  • Health check endpoint for service monitoring
  • Support for various environment configurations
  • Graceful shutdown handling
  • MongoDB and in-memory database support
  • Comprehensive API documentation with Swagger/OpenAPI
  • Pagination support for listing registry entries

Use cases of MCP Registry?

  1. Centralized management of MCP server entries.
  2. Discovery of various MCP implementations and their metadata.
  3. Facilitating contributions and collaboration within the MCP community.

FAQ from MCP Registry?

  • What is the purpose of MCP Registry?

MCP Registry serves as a centralized repository for MCP server entries, enabling easier discovery and management.

  • How can I contribute to the project?

You can check the contributing guidelines in the repository to see how you can help.

  • Is there documentation available for the API?

Yes, the API is documented using Swagger/OpenAPI, accessible via the interactive Swagger UI.

Project Info
Created At
9 months ago
Updated At
9 months ago
Author Name
modelcontextprotocol
Star
1372
Language
Go
License
MIT license

Recommend Servers

View All
Instagit - Let Your Agents Instantly Understand Any Github Repo
@Instagit

Works with Claude Code, Claude Desktop, Cursor, OpenClaw, and any MCP-compatible client. The @latest tag ensures you always get the most recent version. Why Agents that integrate with external libraries are flying blind. They read docs (if they exist), guess at APIs, and hallucinate patterns that don't match the actual code. The result: broken integrations, wrong function signatures, outdated usage patterns, hours of debugging. When an agent can actually analyze the source code of a library or service it's integrating with, everything changes. It sees the real function signatures, the actual data flow, the patterns the maintainers intended. Integration becomes dramatically easier and less error-prone because the agent is working from ground truth, not guesses. What Agents Can Do With This - Integrate with any library correctly the first time — "How do I set up authentication with this SDK?" gets answered from the actual code, not outdated docs or training data. Your agent sees the real constructors, the real config options, the real error types. - Migrate between versions without the guesswork — Point your agent at both the old and new version of a library. It can diff the actual implementations and generate a migration plan that accounts for every breaking change. - Debug issues across repository boundaries — When a bug spans your code and a dependency, your agent can read both codebases and trace the issue to its root cause — even into libraries you've never opened. - Generate integration code that actually works — Instead of producing plausible-looking code that fails at runtime, your agent writes integration code based on the real API surface: actual method names, actual parameter types, actual return values. - Evaluate libraries before committing — "Should we use library A or B?" Your agent can analyze both implementations, compare their approaches to error handling, test coverage, and architectural quality, and give you a grounded recommendation. - Onboard to unfamiliar codebases in minutes — Point your agent at any repo and ask how things work. It answers from the code itself, with file paths and line numbers, not from memory that may be months out of date.

2 days ago
Agent Smith
@jpoindexter

Auto-generate AGENTS.md from your codebase Stop writing AGENTS.md by hand. Run agentsmith and it scans your codebase to generate a comprehensive context file that AI coding tools read automatically. What is AGENTS.md? AGENTS.md is an open standard for giving AI coding assistants context about your project. It's adopted by 60,000+ projects and supported by: Cursor GitHub Copilot Claude Code VS Code Gemini CLI And 20+ more tools AI tools automatically discover and read AGENTS.md files - no configuration needed. What agentsmith does Instead of writing AGENTS.md manually, agentsmith scans your codebase and generates it: npx @jpoindexter/agent-smith agentsmith Scanning /Users/you/my-project... ✓ Found 279 components ✓ Found 5 components with CVA variants ✓ Found 37 color tokens ✓ Found 14 custom hooks ✓ Found 46 API routes (8 with schemas) ✓ Found 87 environment variables ✓ Detected Next.js (App Router) ✓ Detected shadcn/ui (26 Radix packages) ✓ Found cn() utility ✓ Found mode/design-system ✓ Detected 6 code patterns ✓ Found existing CLAUDE.md ✓ Found .ai/ folder (12 files) ✓ Found prisma schema (28 models) ✓ Scanned 1572 files (11.0 MB, 365,599 lines) ✓ Found 17 barrel exports ✓ Found 15 hub files (most imported) ✓ Found 20 Props types ✓ Found 40 test files (12% component coverage) ✓ Generated AGENTS.md ~11K tokens (9% of 128K context) Install # Run directly (no install needed) npx @jpoindexter/agent-smith # Or install globally npm install -g @jpoindexter/agent-smith Usage # Generate AGENTS.md in current directory agentsmith # Generate for a specific directory agentsmith ./my-project # Preview without writing (dry run) agentsmith --dry-run # Custom output file agentsmith --output CONTEXT.md # Force overwrite existing file agentsmith --force Output Modes # Default - comprehensive output (~11K tokens) agentsmith # Compact - fewer details (~20% smaller) agentsmith --compact # Compress - signatures only (~40% smaller) agentsmith --compress # Minimal - ultra-compact (~3K tokens) agentsmith --minimal # XML format (industry standard, matches Repomix) agentsmith --xml # Include file tree visualization agentsmith --tree

2 days ago
Tavily Mcp
@tavily-ai

JavaScript
10 months ago