mcpso
mcpso is a directory and web interface for discovering MCP (Model Context Protocol) servers. It provides a searchable catalog of available MCP server implementations with a live preview at mcp.so, helping developers find and integrate protocol servers for their applications.
Key facts
Objective fields from the source. Values we can't verify are shown as “Unknown” rather than guessed.
| Field | Value |
|---|---|
| Repository | chatmcp/mcpso |
| Owner | chatmcp |
| Primary language | TypeScript |
| License | Apache-2.0 — OSI-approved |
| Stars | 2k |
| Forks | 234 |
| Open issues | 2.4k |
| Latest release | Unknown |
| Last updated | 2025-03-26 |
| Source | https://github.com/chatmcp/mcpso |
What mcpso is
A TypeScript-based Next.js web application that indexes and displays MCP server listings, backed by a Supabase PostgreSQL database. The project acts as a central registry and discovery platform for MCP server implementations with community contribution support.
Get the mcpso source
Clone the repository and explore it locally.
git clone https://github.com/chatmcp/mcpso.gitcd mcpso# follow the project's README for install & configurationNeed it deployed, integrated, or customized instead? DEV.co ships production installs.
Best use cases
Implementation considerations
- Supabase PostgreSQL database required; infrastructure cost and dependency on external provider must be budgeted.
- Environment variables (SUPABASE_URL, SUPABASE_ANON_KEY) must be managed securely in production; no documented secrets rotation or key management guidance provided.
- High open-issue count (2376) suggests active development but also potential stability or completeness concerns; evaluate blocking issues before deployment.
- Requires TypeScript/Node.js runtime and pnpm dependency manager; team must maintain JavaScript ecosystem toolchain expertise.
- Data schema defined in `data/install.sql`; review schema for schema evolution and migration strategy for production upgrades.
When to avoid it — and what to weigh
- Requiring Production-Grade SLAs — This is a community-managed directory (2376 open issues, last push March 2025). No formal SLA, uptime guarantee, or commercial support model is evident.
- Needing Offline or Self-Contained Catalog — The project requires external Supabase hosting and internet connectivity to function. Fully air-gapped environments cannot use the live service.
- Looking for Vetted/Certified Servers Only — As a community directory, there is no documented security review, certification process, or vetting for listed MCP server implementations. Quality and security vary by contributor.
- Minimal Dependencies Preferred — Deployment requires Node.js/pnpm, Supabase account, environment configuration, and database setup. Not a lightweight single-binary tool.
License & commercial use
Licensed under Apache License 2.0 (Apache-2.0), a permissive OSI-approved license.
Apache-2.0 permits commercial use, modification, and distribution with attribution and liability disclaimer. No restrictions on commercial deployment identified. However, verify any dependencies (Next.js, Supabase SDK, etc.) for their own license constraints before committing to production commercial use.
DEV.co evaluation signals
Editorial assessment — not user reviews. Directional, with an explicit confidence level.
| Signal | Assessment |
|---|---|
| Maintenance | Active |
| Documentation | Adequate |
| License clarity | Clear |
| Deployment complexity | Moderate |
| DEV.co fit | Good |
| Assessment confidence | Medium |
Supabase database requires secure credential management (SUPABASE_ANON_KEY); no documented approach for key rotation, secret scanning, or access control. ANON_KEY suggests public read access; verify Row-Level Security (RLS) policies on Supabase tables to prevent unauthorized writes. No security audit, dependency scanning, or vulnerability disclosure process documented. Community-contributed MCP server listings are not vetted; users should independently verify server implementations before integration.
Alternatives to consider
Hugging Face Hub / Model Registry
If focus is discovering pre-built models/servers, HF Hub offers curated, documented, and versioned model/tool listings with built-in trust signals (downloads, ratings, org verification).
OpenAPI/AsyncAPI Registries
For API-first server discovery and protocol-agnostic integration discovery, established registries may offer better standardization and tooling than a custom MCP directory.
Custom Internal Catalog (Git + CI/CD)
Organizations needing tighter control, vetting, and offline access may prefer a self-hosted catalog built on version control and internal deployment pipelines.
Build on mcpso with DEV.co software developers
Visit mcp.so to browse available MCP server implementations, or deploy your own instance for team collaboration. Review architecture, security, and operational requirements before production use.
Talk to DEV.coRelated open-source tools
Surfaced by semantic similarity across the DEV.co open-source index.
Related on DEV.co
Explore the category and the services that help you build with it.
mcpso FAQ
Can I self-host mcpso instead of using mcp.so?
Is the MCP server data in the directory curated or validated?
What database schema is required?
Can I use mcpso in production for critical infrastructure?
Work with a software development agency
Adopting mcpso is usually one piece of a larger software development effort. As a software development agency, DEV.co provides software development services and web development expertise — pairing senior software developers and web developers with your team to design, build, and operate mcp servers software in production.
Ready to Explore MCP Servers?
Visit mcp.so to browse available MCP server implementations, or deploy your own instance for team collaboration. Review architecture, security, and operational requirements before production use.