RemoteMCPList Servers Directory

🚀 The premier community-driven directory of remote Model Context Protocol (MCP) servers

This repository contains the data that powers RemoteMCPList.com, the #1 directory for discovering and learning about remote MCP servers.

🎯 Quick Links

• 🌐 Browse Servers: remotemcplist.com
• 📚 API Access: remotemcplist.com/api/servers.json
• 🤖 AI Discovery: remotemcplist.com/llms.txt
• 📋 Submit Server: Create Issue

🤝 Contributing a New Server

Option 1: GitHub Issue (Easiest)

1. Open a new issue
2. Fill out the form
3. Submit - we'll create the YAML file for you!

Option 2: Pull Request

1. Fork this repository
2. Create a new YAML file in servers/ directory
3. Follow the format below
4. Submit a pull request

📄 Server YAML Format

Each server must have a YAML file in the servers/ directory following this structure:

id: github-mcp                    # Unique identifier (lowercase, hyphens)
name: GitHub MCP Server           # Display name
category: development             # One of: development, data-analysis, communication, 
                                 # payments, cloud, productivity, security, database, 
                                 # ai-ml, monitoring
description: Complete GitHub integration for MCP  # 20-200 characters
long_description: |               # Detailed description (must be longer than description)
  The GitHub MCP Server provides comprehensive access to GitHub's API,
  enabling AI assistants to manage repositories, issues, pull requests,
  and automate development workflows through the Model Context Protocol.

maintainer:
  name: Anthropic                 # Your name or organization
  github: anthropic               # GitHub username
  website: anthropic.com          # Optional (domain or full URL)

authentication:
  type: oauth2                    # One of: oauth2, api-key, none
  provider: github                # e.g., github, google, custom
  instructions: |                 # How to get credentials
    1. Go to GitHub Settings > Developer settings
    2. Create a personal access token
    3. Configure in your MCP client

endpoints:
  production: https://github-mcp.example.com      # Required
  sandbox: https://sandbox.github-mcp.example.com # Optional

capabilities:                     # List what the server can do
  - id: repository.read
    name: Read Repositories
    description: Access repository contents and metadata
  - id: issues.manage
    name: Manage Issues  
    description: Create, update, and close issues

tags:                            # For search/filtering
  - github
  - version-control
  - development
  - mcp
  - remote

verification:
  status: pending                # verified, pending, or unverified
  tested_date: "2024-12-10T00:00:00Z"
  security_audit: false

featured: false                  # Show on homepage (only one should be true)

📁 Repository Structure

servers/
├── github-mcp.yaml      # Individual server files
├── stripe-mcp.yaml
├── slack-mcp.yaml
└── ...

scripts/
├── validate.py          # Validation script
└── check_urls.py        # URL checker

.github/
├── ISSUE_TEMPLATE/
│   └── new-server.yml   # Issue template for submissions
└── workflows/
    └── validate.yml     # Auto-validation on PRs

✅ Validation

All submissions are automatically validated for:

• Valid YAML syntax
• Required fields present
• Correct category values
• Valid URLs
• Proper date formats

Run validation locally:

python scripts/validate.py

🏷️ Categories

• development - Version control, CI/CD, code tools
• data-analysis - Data processing, analytics, BI tools
• communication - Chat, email, messaging platforms
• payments - Payment processing, billing, invoicing
• cloud - Cloud services, hosting, infrastructure
• productivity - Task management, notes, calendars
• security - Authentication, monitoring, compliance
• database - Database connections and management
• ai-ml - AI/ML services and model providers
• monitoring - Observability, logging, metrics

🔍 How It Works

1. Submit - Create a YAML file for your MCP server
2. Validate - Automatic checks ensure quality
3. Review - Community members review submissions
4. Merge - Approved servers are added
5. Deploy - Changes appear on remotemcplist.com within minutes

📊 API Access

Access the data programmatically:

# Get all servers
curl https://remotemcplist.com/api/servers.json

# Get specific server
curl https://remotemcplist.com/api/servers/github-mcp.json

# Search servers
curl "https://remotemcplist.com/api/search?q=github"

🤖 For AI Assistants

AI assistants can discover MCP servers via:

• llms.txt: https://remotemcplist.com/llms.txt
• API: Structured JSON data
• Sitemap: https://remotemcplist.com/sitemap.xml

📜 License

This repository is licensed under the MIT License. See LICENSE for details.

🙏 Acknowledgments

Inspired by awesome-lists and the MCP community. Special thanks to all contributors!

🔗 Links

• Website: remotemcplist.com
• API Docs: remotemcplist.com/api/docs
• Submit Server: New Issue
• Discussion: GitHub Discussions

---

Made with ❤️ for the MCP community
remotemcplist.com