K
kaichen/mcp-local-router
Local proxy that aggregates several MCP servers
在 GitHub 查看 ↗链接已于 2026-11-12 核查 · HTTP 200 · 打开的是厂商自己的官网
安装与配置
客户端配置(取自该仓库的安装命令)
{
"mcpServers": {
"kaichen-mcp-local-router": {
"command": "npx",
"args": ["-y", "@modelcontextprotocol/server-filesystem", "/Users/username/Desktop"]
}
}
}解析自我们于 2026-11-05 抓取的该仓库 README;我们未执行过。
command/args 来自仓库写明的安装命令;不确定时请以该项目 README 为准。
VS Code(.vscode/mcp.json —— 键名是 servers)
{
"servers": {
"kaichen-mcp-local-router": {
"command": "npx",
"args": ["-y", "@modelcontextprotocol/server-filesystem", "/Users/username/Desktop"]
}
}
}VS Code 顶层键是 <code>servers</code>,其余与上面那份相同。
Claude Code(命令行)
claude mcp add --transport stdio kaichen-mcp-local-router -- npx -y @modelcontextprotocol/server-filesystem /Users/username/Desktop
Claude Code 不收 JSON 文件,用这条命令直接加。
配置项的键名以你的客户端为准:客户端与 CLI
- 来源明细
- 收录自 abordage/awesome-mcp 榜单(我们从中收集的条目之一) · 条目类型:MCP 服务
- 收录与活跃
- 收录于 2026-11-05 · 最近见到 2026-11-14 · 共见到 10 次 · 被 10 个来源列出
- 评分构成
- 综合分 1,003 · 10 个来源 · mcp
- 安装
npx -y @modelcontextprotocol/server-filesystem /Users/username/Desktop
常见问题(答案都来自我们的记录)
怎么安装?
该仓库给出的安装命令是
npx -y @modelcontextprotocol/server-filesystem /Users/username/Desktop。我们的记录里它是仓库自己提供的;不保证在你的客户端上直接可用。它适合谁 / 用来做什么?
我们把它归在这些标签下: MCP 服务。标签来自条目自身,不是我们强加的分类。
谁维护它、还在更新吗?
我们收录于 2026-11-05;最近见到 2026-11-14。这里没有"官方认证"或"质量评级"——我们只记录来源与时间。
# MCP Local Router
以下摘录自该仓库的 README(片段) · 在 GitHub 读完整 README →
This project is an MCP (Model Context Protocol) local router that serves as an aggregation proxy for MCP servers. It can connect to multiple upstream MCP servers and aggregate their functionalities into a single interface for downstream clients.
## Features
Supports specifying a configuration file via command line arguments
Supports configuring multiple upstream MCP servers
Supports stdio transport
Supports injecting environment variables into stdio transport
Supports SSE transport with aggregated /sse and per-upstream /sse/{serverName} endpoints
## Usage
### Running
It must be run with a configuration file:
bash
cargo run -- --config mcp-config.json --transport sse
#### SSE Routing
When the router runs with --transport sse, it exposes two kinds of endpoints:
/sse streams the aggregated tool surface area from every configured upstream server.
/sse/{serverName} streams only the tools from a single upstream. The {serverName} segment must match the key from mcpServers in your configuration file (for example /sse/filesystem or /sse/workspace-search).
The server name keys should be URL-safe because they are used directly as path segments.
Each SSE connection emits an initial endpoint event containing the HTTP path clients should use for POST requests. All streaming endpoints share the same POST /message?sessionId=… channel.
### Configuration File Format
The configuration file is in JSON format; an example is shown below:
json
"mcpServers": {
"filesystem": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-filesystem",
"/Users/username/Desktop"
],
"env": {
"LINEARACCESSTOKEN": "yourpersonalaccesstoken"
},
"workspace-search": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-everything"
],
"env": {}
Description:
mcpServers: a mapping of multiple server configurations
Each key is the server's name (used for logging and the /sse/{serverName} path)
Each value is an object containing the following fields:
command: the command to execute
args: an array of command arguments
## Features
Supports specifying a configuration file via command line arguments
Supports configuring multiple upstream MCP servers
Supports stdio transport
Supports injecting environment variables into stdio transport
Supports SSE transport with aggregated /sse and per-upstream /sse/{serverName} endpoints
## Usage
### Running
It must be run with a configuration file:
bash
cargo run -- --config mcp-config.json --transport sse
#### SSE Routing
When the router runs with --transport sse, it exposes two kinds of endpoints:
/sse streams the aggregated tool surface area from every configured upstream server.
/sse/{serverName} streams only the tools from a single upstream. The {serverName} segment must match the key from mcpServers in your configuration file (for example /sse/filesystem or /sse/workspace-search).
The server name keys should be URL-safe because they are used directly as path segments.
Each SSE connection emits an initial endpoint event containing the HTTP path clients should use for POST requests. All streaming endpoints share the same POST /message?sessionId=… channel.
### Configuration File Format
The configuration file is in JSON format; an example is shown below:
json
"mcpServers": {
"filesystem": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-filesystem",
"/Users/username/Desktop"
],
"env": {
"LINEARACCESSTOKEN": "yourpersonalaccesstoken"
},
"workspace-search": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-everything"
],
"env": {}
Description:
mcpServers: a mapping of multiple server configurations
Each key is the server's name (used for logging and the /sse/{serverName} path)
Each value is an object containing the following fields:
command: the command to execute
args: an array of command arguments
收录徽章(可选)
想把收录标记放进 README 就复制这行,可选,不影响收录。
[](https://anclum.com/zh/s/kaichen-mcp-local-router/)
- 来源
- awesome · https://github.com/kaichen/mcp-local-router
- 按领域浏览
- MCP 服务
- 收录来源
- 10 个独立来源
- 收录于
- 今天
同类推荐
所属领域与标签
每个标签都能点进去看同类的全部条目。数字是当前库里的真实条数。