Skip to content
Back to search

mcp-proxy-server

An MCP proxy server that aggregates and serves multiple MCP resource servers through a single interface

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/adamwattis--mcp-proxy-server/badge.svg)](/listings/adamwattis--mcp-proxy-server)

HTML

<a href="/listings/adamwattis--mcp-proxy-server"><img src="/api/listings/adamwattis--mcp-proxy-server/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

To use with Claude Desktop, add the server config:

On MacOS: `~/Library/Application Support/Claude/claude_desktop_config.json` On Windows: `%APPDATA%/Claude/claude_desktop_config.json`

{
  "mcpServers": {
    "mcp-proxy": {
      "command": "/path/to/mcp-proxy-server/build/index.js",
      "env": {
        "MCP_CONFIG_PATH": "/absolute/path/to/your/config.json",
        "KEEP_SERVER_OPEN": "1"
      }
    }
  }
}

- `KEEP_SERVER_OPEN` will keep the SSE running even if a client disconnects. Useful when multiple clients connects to the MCP proxy.

Debugging

Since MCP servers communicate over stdio, debugging can be challenging. We recommend using the [MCP Inspector](https://github.com/modelcontextprotocol/inspector), which is available as a package script:

npm run inspector

The Inspector will provide a URL to access debugging tools in your browser.

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 126 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. # MCP Proxy Server
  2. 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:
  3. - Connect to and manage multiple MCP resource servers
  4. - Expose their combined capabilities through a unified interface
  5. - Handle routing of requests to appropriate backend servers
  6. - Aggregate responses from multiple sources
  7. ## Features
  8. ### Resource Management
  9. - Discover and connect to multiple MCP resource servers
  10. - Aggregate resources from all connected servers
  11. - Maintain consistent URI schemes across servers
  12. - Handle resource routing and resolution
  13. ### Tool Aggregation
  14. - Expose tools from all connected servers
  15. - Route tool calls to appropriate backend servers
  16. - Maintain tool state and handle responses
  17. ### Prompt Handling
  18. - Aggregate prompts from all connected servers
  19. - Route prompt requests to appropriate backends
  20. - Handle multi-server prompt responses
  21. ## Configuration
  22. 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:
  23. ```bash
  24. cp config.example.json config.json
  25. ```
  26. Example config structure:
  27. ```json
  28. {
  29. "servers": [
  30. {
  31. "name": "Server 1",
  32. "transport": {
  33. "command": "/path/to/server1/build/index.js"
  34. }
  35. },
  36. {
  37. "name": "Server 2",
  38. "transport": {
  39. "command": "server2-command",
  40. "args": ["--option1", "value1"],
  41. "env": ["SECRET_API_KEY"]
  42. }
  43. },
  44. {
  45. "name": "Example Server 3",
  46. "transport": {
  47. "type": "sse",
  48. "url": "http://localhost:8080/sse"
  49. }
  50. }
  51. ]
  52. }
  53. ```
  54. The config file must be provided when running the server:
  55. ```bash
  56. MCP_CONFIG_PATH=./config.json mcp-proxy-server
  57. ```
  58. ## Development
  59. Install dependencies:
  60. ```bash
  61. npm install
  62. ```
  63. Build the server:
  64. ```bash
  65. npm run build
  66. ```
  67. For development with auto-rebuild:
  68. ```bash
  69. npm run watch
  70. ```
  71. For development with continuous run:
  72. ```bash
  73. # Stdio
  74. npm run dev
  75. # SSE
  76. npm run dev:sse
  77. ```
  78. ## Installation
  79. To use with Claude Desktop, add the server config:
  80. On MacOS: `~/Library/Application Support/Claude/claude_desktop_config.json`
  81. On Windows: `%APPDATA%/Claude/claude_desktop_config.json`
  82. ```json
  83. {
  84. "mcpServers": {
  85. "mcp-proxy": {
  86. "command": "/path/to/mcp-proxy-server/build/index.js",
  87. "env": {
  88. "MCP_CONFIG_PATH": "/absolute/path/to/your/config.json",
  89. "KEEP_SERVER_OPEN": "1"
  90. }
  91. }
  92. }
  93. }
  94. ```
  95. - `KEEP_SERVER_OPEN` will keep the SSE running even if a client disconnects. Useful when multiple clients connects to the MCP proxy.
  96. ### Debugging
  97. Since MCP servers communicate over stdio, debugging can be challenging. We recommend using the [MCP Inspector](https://github.com/modelcontextprotocol/inspector), which is available as a package script:
  98. ```bash
  99. npm run inspector
  100. ```
  101. The Inspector will provide a URL to access debugging tools in your browser.

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.