Custom MCP Tunneling
Need to connect internal Postgres databases, internal search indices, or on-premise microservices to Plannix? Use Custom MCP Tunneling to securely expose Model Context Protocol tools without punching holes in your corporate firewall.
Model Context Protocol overview
Standardized Tool Calling
Compatible with any MCP server built in TypeScript, Python, Go, or Rust.
Zero Inbound Ports
Outbound-only secure WebSocket/TLS tunnel keeps your network perimeter secure.
Secure tunneling architecture
The Plannix MCP Bridge daemon connects outbound to tunnel.plannix.web.id on port 443. When a user prompts Plannix with a task requiring your custom tool, the model dispatches a JSON-RPC invocation through the tunnel, and your local server processes it within your perimeter.
Running the plannix-mcp daemon
Install and run the bridge binary on your private host or within a container:
# Install Plannix MCP bridge
npm install -g @plannix/mcp-bridge
# Launch encrypted tunnel pointing to local Postgres MCP server
plannix-mcp tunnel \
--target=http://127.0.0.1:8080/mcp \
--name=internal-postgres \
--token=${PLANNIX_MCP_TUNNEL_KEY}Registering tools and resources
Once connected, your server automatically advertises its tool schema (function signatures, input arguments, and descriptions) to your Plannix workspace chat engine.
Mutual TLS & audit logs
All tunnel payloads are encrypted with mTLS. Every request and response payload is logged locally on your daemon machine, giving your security team full visibility into queries.