Skip to main content

Plugged.in Registry Features

The Plugged.in Registry is a comprehensive system for discovering, sharing, and managing Model Context Protocol (MCP) servers. It provides a unified platform for the MCP ecosystem.

Overview

The registry consists of three main components:

Official Registry

registry.plugged.inCurated and verified MCP servers with GitHub ownership verification

Community Servers

User-submitted servers pending verification with quick sharing capabilities

Local Servers

Private servers for individual use with full customization

Key Features

1. Add Server to Registry

Submit your MCP server to the official registry for global discovery.
1

Navigate

Go to MCP Servers → Add to Registry
2

Enter Repository

Enter your GitHub repository URL
3

Auto-Detection

System automatically detects:
  • Package type (npm, docker, pypi)
  • Environment variables
  • Available transports (STDIO, SSE, Streamable HTTP)
4

Review

Review and confirm details
5

Submit

Submit for registry publication
Requirements:
  • GitHub repository ownership
  • Valid package.json/Dockerfile/setup.py
  • Connected GitHub account

2. Community Servers

Share servers with the community before official registry approval. Features:
  • Quick sharing without verification
  • Public discovery through search
  • Can be claimed by repository owners
  • Automatic migration to registry upon claiming
Process:
  1. Navigate to Search → Add to Community
  2. Fill in server details
  3. Submit for immediate availability

3. Server Claiming

Claim ownership of community servers and publish to official registry.
  1. Find your server in community listings
  2. Click “Claim This Server”
  3. Verify GitHub ownership
  4. Server is automatically:
    • Published to official registry
    • Statistics migrated
    • Removed from community
  • Multi-source search: Registry, Community, or All
  • Package filters: npm, docker, pypi
  • Repository filters: GitHub, GitLab, etc.
  • Sort options: Relevance, Recent, Popular
  • Real-time results: Instant filtering
  • Rich metadata: Ratings, installations, descriptions

5. Server Statistics

Tracked Metrics:
  • Installation count
  • Average rating (1-5 stars)
  • Number of ratings
  • Activity logs
  • Trending status
Statistics automatically migrate when:
  • Community server is claimed
  • Server moves between sources
  • Duplicate servers are consolidated

API Endpoints

Public Search API

Query the registry without authentication. Parameters:
  • q - Search query
  • source - Filter by source (registry/community/all)
  • package - Filter by package type
  • repository - Filter by repository source
  • sort - Sort results (relevance/recent)
  • limit - Results per page
  • offset - Pagination offset
Example:

Add to Registry API

Submit a server to the registry (requires authentication). Body:

Server Statistics API

Get detailed statistics for a specific server. Response:

Database Schema

Registry Servers Table

Community Servers Table

Implementation Details

GitHub Verification

The system verifies GitHub ownership through:
  1. OAuth token validation
  2. Repository access check
  3. Collaborator status verification
  4. Organization membership check

Auto-Detection Logic

Statistics Migration

When a server is claimed:
  1. Copy installation_count from community to registry
  2. Migrate user ratings and reviews
  3. Transfer activity logs
  4. Update trending calculations
  5. Remove from community table

Best Practices

For Server Authors

1

Prepare Repository

  • Ensure clear README documentation
  • Add MCP configuration to package.json
  • Include example usage
2

Test Locally

  • Verify server works with MCP clients
  • Test all advertised features
  • Check environment variable handling
3

Submit to Registry

  • Use the Smart Server Wizard
  • Provide accurate metadata
  • Include helpful descriptions
4

Maintain

  • Respond to user feedback
  • Keep dependencies updated
  • Monitor usage statistics

For Users

  • Search effectively: Use filters to find specific server types
  • Check ratings: Review community feedback before installing
  • Report issues: Help improve servers by reporting problems
  • Rate servers: Provide feedback to help others

Troubleshooting

Common Issues:
  • GitHub verification fails: Ensure you’re logged in with the correct account
  • Auto-detection misses features: Check package.json MCP configuration
  • Statistics not updating: May take up to 5 minutes to reflect changes

Future Enhancements

  • Automated testing of submitted servers
  • Enhanced verification badges
  • Server categories and tags
  • Advanced analytics dashboard
  • API rate limiting tiers