Skip to content

Commit 136777c

Browse files
Specify --target-port on docs and match port on quickstart guide
AFAIK we have 2 ports: the proxy port in which ToolHive runs and a hardcoded port that may be used by an MCP server. For the second one, the current flag should be `--target-port` instead of `--port`. Changed the only reference I could find in docs. Also, there was a small typo in the quickstart guide in the ports. The text was talking about port `49226` but the port shown in the example was port `15266`.
1 parent 9097b16 commit 136777c

File tree

2 files changed

+3
-3
lines changed

2 files changed

+3
-3
lines changed

docs/toolhive/guides-cli/run-mcp-servers.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -146,7 +146,7 @@ ToolHive creates a reverse proxy on a random port that forwards requests to the
146146
container. To specify the port for an MCP server:
147147

148148
```bash
149-
thv run --port <port-number> <server-name>
149+
thv run --target-port <port-number> <server-name>
150150
```
151151

152152
## Run a custom MCP server

docs/toolhive/tutorials/quickstart.mdx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -187,7 +187,7 @@ Image [mcp/fetch:latest] has 'latest' tag, pulling to ensure we have the most re
187187
Pulling image: [mcp/fetch:latest]
188188
...
189189
Successfully pulled image: [mcp/fetch:latest]
190-
Using host port: [49226]
190+
Using host port: [15266]
191191
Logging to: [~/Library/Application Support/toolhive/logs/fetch.log]
192192
MCP server is running in the background (PID: [80087])
193193
Use 'thv stop [fetch]' to stop the server
@@ -217,7 +217,7 @@ NAME PACKAGE STATUS URL PORT
217217
fetch mcp/fetch:latest running http://127.0.0.1:15266/sse#fetch 15266 mcp 2025-06-30 09:12:53 -0400 EDT
218218
```
219219

220-
This confirms that the fetch server is running and available on port 49226.
220+
This confirms that the fetch server is running and available on port 15266.
221221

222222
:::info What's happening?
223223

0 commit comments

Comments
 (0)