mcpmux/mcp-servers
Developer tools이 페이지는 AI로 자동 번역되었습니다. 기술적인 세부 사항은 원문을 확인하세요. 원문 보기
Community MCP server definitions for McpMux
개요
Community-maintained registry of MCP (Model Context Protocol) server definitions for McpMux — the desktop gateway that lets AI clients (Cursor, Claude Desktop, VS Code, Windsurf) share MCP servers through a single endpoint. Each server is defined as a single JSON file. When merged to main, definitions are bundled and published to the McpMux discovery API so every McpMux user can install them in one click. Every file in examples/ is a copy of a real definition from servers/ and passes validation (enforced by pnpm test). Pick the row that matches : examples/README.md explains what each one demonstrates and what to change when you copy it. 1. You add a JSON file to servers/. 2. CI validates it against the schema and checks for ID/alias conflicts. 3. On merge, the bundler aggregates every definition into a single bundle.json, enriches it with platform metadata, and uploads it to Cloudflare R2. 4. McpMux desktop app and the discover web UI read from that bundle. Visit mcpmux.
README
원문 README의 일부입니다. 원문 보기.
McpMux Server Registry
Community-maintained registry of MCP (Model Context Protocol) server definitions for McpMux — the desktop gateway that lets AI clients (Cursor, Claude Desktop, VS Code, Windsurf) share MCP servers through a single endpoint.
Each server is defined as a single JSON file. When merged to main, definitions are bundled and published to the McpMux discovery API so every McpMux user can install them in one click.
Browse servers on mcpmux.com · Download McpMux · Explore features · Join our Discord
Contents
- Quick Start
- Pick a Starting Example
- Server Definition Format
- Transport Types
- Auth, Inputs & Placeholders — How They Fit Together
- Defining Inputs
- Examples Cookbook
- Common Mistakes
- ID Naming Convention
- Categories · Capabilities
- Contributing a New Server
- Working With an AI Coding Agent
- Commands Reference
Quick Start
# 1. Fork & clone
git clone https://github.com//mcp-servers.git
cd mcp-servers && pnpm install # or: npm ci
# 2. Copy the example closest to your server (see the table below)
cp examples/stdio-api-key.json servers/.json
# 3. Edit it, then validate
pnpm validate servers/.json
pnpm check-conflicts
pnpm test
# 4. Submit
git add servers/.json
git commit -s -m "Add "
# Open a Pull Request
Pick a Starting Example
Every file in examples/ is a copy of a real definition from servers/ and passes validation (enforced by pnpm test). Pick the row that matches what the server needs from the user:
| The server needs… | Transport | auth.type |
Start from |
|---|---|---|---|
| Nothing — it just runs | stdio | none |
stdio-no-auth.json |
| A folder or file path (not a secret) | stdio | none |
stdio-local-path.json |
| A few settings — a dropdown, a toggle | stdio | none |
stdio-select-toggle.json |
| An API key it can’t work without | stdio | api_key |
stdio-api-key.json |
| A token, run through Docker | stdio | api_key |
complete-example.json |
| Connection details (host, port, user, password) | stdio | optional_api_key |
stdio-multi-input.json |
설치
npx -y @brave/brave-search-mcp-server