Skip to content

Commit ca056b2

Browse files
committed
add an example about accessing internal workloads
This is specifically for accessing containers on the same network when running network isolation
1 parent 9c545b0 commit ca056b2

File tree

1 file changed

+13
-0
lines changed

1 file changed

+13
-0
lines changed

docs/toolhive/guides-ui/network-isolation.mdx

Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -79,6 +79,19 @@ The configuration pictured below allows the MCP server to access
7979
/>
8080
<br />
8181

82+
### Accessing other workloads on the same network
83+
84+
To allow an MCP server to access other workloads on the same network, you need
85+
to configure network isolation to include the appropriate hostnames and ports.
86+
This is commonly needed when your MCP server needs to communicate with
87+
databases, APIs, or other services that are not publicly accessible.
88+
89+
For example, in Docker environments, you can add `host.docker.internal` to
90+
access services on the host:
91+
92+
- **Allowed hosts**: `host.docker.internal`
93+
- **Allowed ports**: `3000`
94+
8295
## Related information
8396

8497
- [Run MCP servers](./run-mcp-servers.md)

0 commit comments

Comments
 (0)