by asashiki · MCP Server · ★ 21
MCP Switch One MCP endpoint to rule them all. Web- or app-based AIs are limited to remote MCP servers and typically offer only a single custom connector slot. In contrast, half of the most useful MCP servers run locally via standard I/O (like npx or uvx), making them accessible only to Claude Desktop or CLI tools. English · 简体中文 · 日本語 🔗 Live console demo · 📖 User manual Why Web/app AIs can only connect to remote MCP servers, and most of them give you just one custom connector slot.
| Stars | 21 |
| Forks | 1 |
| Language | TypeScript |
| Category | MCP Server |
| License | MIT |
| Quality Score | 75.6804499186811/100 |
| Last Updated | 2026-07-07 |
| Created | 2026-06-13 |
| Platforms | claude-code, mcp, node |
| Est. Tokens | ~15k |
Explore other popular mcp server tools:
mcp-switch is Self-hosted gateway that aggregates local stdio and remote HTTP MCP servers behind one OAuth endpoint — connect once, reach all your tools from any AI.. It is categorized as a MCP Server with 21 GitHub stars.
mcp-switch is primarily written in TypeScript. It covers topics such as aggregator, ai, chatgpt.
You can find installation instructions and usage details in the mcp-switch GitHub repository at github.com/asashiki/mcp-switch. The project has 21 stars and 1 forks, indicating an active community.
mcp-switch is released under the MIT license, making it free to use and modify according to the license terms.