A
adamwattis/mcp-proxy-server
One proxy in front of several MCP resource servers
View on GitHub ↗Link checked 2026-11-12 · automated check blocked (HTTP 429), status unconfirmed
We have neither an install command nor a public remote endpoint from this repository, so we do not print a config. A made-up one is worse than none. How each client wires MCP up →
- Source
- collected from the abordage/awesome-mcp list · type: MCP server
- Harvest history
- first seen 2026-11-05 · last seen 2026-11-14 · seen 10× · listed by 10 sources
- Score
- score 1,003 · 10 sources · mcp
FAQ (answers come from our records)
Who is it for?
We filed it under these tags: MCP 服务. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
first catalogued 2026-11-05；last seen 2026-11-14。There is no official certification or quality rating here — we record sources and dates only.
# MCP Proxy Server
以下摘录自该仓库的 README（片段） · 在 GitHub 读完整 README →
An MCP proxy server that aggregates and serves multiple MCP resource servers through a single interface. This server acts as a central hub that can:
Connect to and manage multiple MCP resource servers
Expose their combined capabilities through a unified interface
Handle routing of requests to appropriate backend servers
Aggregate responses from multiple sources
## Features
### Resource Management
Discover and connect to multiple MCP resource servers
Aggregate resources from all connected servers
Maintain consistent URI schemes across servers
Handle resource routing and resolution
### Tool Aggregation
Expose tools from all connected servers
Route tool calls to appropriate backend servers
Maintain tool state and handle responses
### Prompt Handling
Aggregate prompts from all connected servers
Route prompt requests to appropriate backends
Handle multi-server prompt responses
## Configuration
The server requires a JSON configuration file that specifies the MCP servers to connect to. Copy the example config and modify it for your needs:
bash
cp config.example.json config.json
Example config structure:
json
"servers": [
"name": "Server 1",
"transport": {
"command": "/path/to/server1/build/index.js"
},
"name": "Server 2",
"transport": {
"command": "server2-command",
"args": ["--option1", "value1"],
"env": ["SECRETAPIKEY"]
},
"name": "Example Server 3",
"transport": {
"type": "sse",
"url": "http://localhost:8080/sse"
The config file must be provided when running the server:
bash
MCPCONFIGPATH=./config.json mcp-proxy-server
## Development
Install dependencies:
bash
npm install
Build the server:
bash
npm run build
For development with auto-rebuild:
bash
npm run watch
For development with continuous run:
bash
# Stdio
npm run dev
# SSE
npm run dev:sse
## Installation
To use with Claude Desktop, add the server config:
On MacOS: ~/Library/Application Support/Claude/claudedesktopconfig.json
On Windows: %APPDATA%/Claude/claudedesktopconfig.json
json
"mcpServers": {
"mcp-proxy": {
"command": "/path/to/mcp-proxy-server/build/index.js",
"env": {
"MCPCONFIGPATH": "/absolute/path/to/your/config.json",
"KEEPSERVEROPEN": "1"
KEEPSERVEROPEN will keep the SSE running even if a client disconnects. Useful when multiple clients connects to the MCP proxy.
Connect to and manage multiple MCP resource servers
Expose their combined capabilities through a unified interface
Handle routing of requests to appropriate backend servers
Aggregate responses from multiple sources
## Features
### Resource Management
Discover and connect to multiple MCP resource servers
Aggregate resources from all connected servers
Maintain consistent URI schemes across servers
Handle resource routing and resolution
### Tool Aggregation
Expose tools from all connected servers
Route tool calls to appropriate backend servers
Maintain tool state and handle responses
### Prompt Handling
Aggregate prompts from all connected servers
Route prompt requests to appropriate backends
Handle multi-server prompt responses
## Configuration
The server requires a JSON configuration file that specifies the MCP servers to connect to. Copy the example config and modify it for your needs:
bash
cp config.example.json config.json
Example config structure:
json
"servers": [
"name": "Server 1",
"transport": {
"command": "/path/to/server1/build/index.js"
},
"name": "Server 2",
"transport": {
"command": "server2-command",
"args": ["--option1", "value1"],
"env": ["SECRETAPIKEY"]
},
"name": "Example Server 3",
"transport": {
"type": "sse",
"url": "http://localhost:8080/sse"
The config file must be provided when running the server:
bash
MCPCONFIGPATH=./config.json mcp-proxy-server
## Development
Install dependencies:
bash
npm install
Build the server:
bash
npm run build
For development with auto-rebuild:
bash
npm run watch
For development with continuous run:
bash
# Stdio
npm run dev
# SSE
npm run dev:sse
## Installation
To use with Claude Desktop, add the server config:
On MacOS: ~/Library/Application Support/Claude/claudedesktopconfig.json
On Windows: %APPDATA%/Claude/claudedesktopconfig.json
json
"mcpServers": {
"mcp-proxy": {
"command": "/path/to/mcp-proxy-server/build/index.js",
"env": {
"MCPCONFIGPATH": "/absolute/path/to/your/config.json",
"KEEPSERVEROPEN": "1"
KEEPSERVEROPEN will keep the SSE running even if a client disconnects. Useful when multiple clients connects to the MCP proxy.
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[](https://anclum.com/en/s/adamwattis-mcp-proxy-server/)
- Source
- awesome · https://github.com/adamwattis/mcp-proxy-server
- Browse by field
- MCP servers
- Listed by
- 10 independent sources
- added
- today
More like this
Filed under
Every tag opens the full list for that filter. Counts are the live catalogue figures.