Custom and unlisted connectors

Point OpenBot at an MCP server that is not in the directory — remote URL or local process.

Use a custom MCP entry when your server is private or still under review. Provide the command or remote URL, auth, and enable it for the agent.

Remote MCP: HTTPS endpoint the bridge or OpenClaw can reach (consider MCP tunnels for private networks).
Local: command + args registered in the MCP config (see catalog snapshot under bridge/openclaw-catalog).
Test with the same Test connection path as directory apps before relying on it in routines.

Do not commit OAuth client secrets or PATs. Put them in host ops/bridge.env or the encrypted connector store.