MCP.so — Open-Source MCP Server Directory

What it is

MCP.so is an open-source directory for Model Context Protocol servers. Built with Next.js and Supabase, it lets users browse, search, and submit community MCP servers. The project powers the mcp.so website and can be self-hosted for private MCP server directories. It ships under the Apache-2.0 license.

This tool is for developers looking for MCP servers to use with Claude, and for organizations that want to maintain a private catalog of approved MCP integrations.

How it saves time or tokens

Finding MCP servers scattered across GitHub repositories is time-consuming. MCP.so centralizes discovery with search, categorization, and metadata. Each listing includes installation instructions, configuration snippets, and compatibility information. For organizations, a self-hosted instance serves as a vetted catalog of approved MCP servers.

How to use

1. Browse mcp.so or self-host your own instance.
2. Search for MCP servers by function or keyword.
3. Copy the configuration snippet for your MCP client.
4. Submit new servers to the directory.

# Self-host MCP.so
git clone https://github.com/chatmcp/mcp.so.git
cd mcp.so

# Set up environment variables
cp .env.example .env.local
# Edit .env.local with your Supabase credentials

# Install and run
npm install
npm run dev

# Access at http://localhost:3000

Example

A typical MCP server listing on the directory:

{
  "name": "filesystem",
  "description": "Read, write, and manage files on the local filesystem",
  "repository": "https://github.com/modelcontextprotocol/servers",
  "category": "filesystem",
  "config": {
    "command": "npx",
    "args": ["-y", "@modelcontextprotocol/server-filesystem", "/path/to/dir"]
  },
  "compatible_clients": ["Claude Desktop", "Claude Code"]
}

Copy the config object directly into your MCP client settings.

Related on TokRepo

• MCP filesystem — File system MCP server
• AI agent tools — More agent tool integrations

Common pitfalls

• Community-submitted servers are not vetted for security. Review server code before granting access to sensitive resources.
• Self-hosting requires Supabase (or a PostgreSQL database with Supabase client). The setup has a learning curve.
• MCP server compatibility varies across clients. A server that works with Claude Desktop may need adjustments for other clients.
• The directory is a catalog, not a package manager. You still need to install MCP servers separately.
• Listings may become outdated as servers evolve. Check the linked repository for the latest version.
• Review the official documentation before deploying to production to ensure compatibility with your specific environment and requirements.
• Start with default settings and customize incrementally. Changing too many configuration options at once makes debugging harder.