You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+6-1Lines changed: 6 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -31,6 +31,11 @@ go install github.com/TBXark/mcp-proxy@latest
31
31
```bash
32
32
docker run -d -p 9090:9090 -v /path/to/config.json:/config/config.json ghcr.io/tbxark/mcp-proxy:latest
33
33
```
34
+
or
35
+
36
+
```bash
37
+
docker run -d -p 9090:9090 ghcr.io/tbxark/mcp-proxy:latest --config https://example.com/path/to/config.json
38
+
```
34
39
35
40
## Configuration
36
41
@@ -100,7 +105,7 @@ Usage of mcp-proxy:
100
105
print version and exit
101
106
```
102
107
1. The server will start and aggregate the tools and capabilities of the configured MCP clients.
103
-
2. You can access the server at the specified address (e.g., `http://localhost:9090/fetch/sse`).
108
+
2. You can access the server at `http(s)://{baseURL}/{clientName}/sse`. (e.g., `https://my-mcp.example.com/fetch/sse`, based on the example configuration)
104
109
3. If your MCP client does not support custom request headers., you can change the key in `clients` such as `fetch` to a random string, and then access it via `/random-string/sse`.
0 commit comments