The intended Toby Hired resource is https://mcp.tobyhired.com/mcp. Do not put a Supabase key, dashboard JWT, or API token in client configuration: none is an MCP token and none fixes missing OAuth.
Anthropic documents remote MCP connectors in Claude web and Claude Desktop for Free, Pro, Max, Team, and Enterprise plans; Free has one connector. Claude Desktop adds them through Settings → Connectors, not direct claude_desktop_config.json editing. A Team or Enterprise owner or administrator first enables the connector, then each user completes their own OAuth. A remote connector request comes from the cloud even in Claude Desktop, so WARP on a laptop alone is insufficient. See Anthropic’s custom-connector guide.
Do not perform these steps for Toby Hired until its owner confirms working OAuth and private-network host access.
The official Claude Code CLI supports remote HTTP MCP. Once Toby Hired access is ready, the native user configuration can be:
claude mcp add --transport http tobyhired --scope user https://mcp.tobyhired.com/mcp claude mcp get tobyhired
Then /mcp guides the user through browser OAuth. This is a future example, not a working connection today. Only a private local fixture has been verified in Claude Code: two organization connections, five synthetic reads, and a cross-organization read denial. It used separate development-only authentication over loopback; it is not a recruiter configuration or proof of production OAuth, DNS/TLS, or hosted-client access. Check the current Claude Code MCP documentation first. Do not add an Authorization header or a local wrapper process.
ChatGPT connects to remote MCP servers. In current developer mode, a workspace administrator or owner can create a custom app, provide the endpoint, choose authentication, scan tools, and complete OAuth. Availability depends on plan and workspace permissions: current documentation describes full MCP for Business and Enterprise/Edu, while Pro has limited read/search MCP in developer mode. See OpenAI’s developer-mode and custom-MCP guide.
Toby Hired has not yet proven a private-network route for hosted ChatGPT, so this is not currently advertised as a working ChatGPT connector. OpenAI provides Secure MCP Tunnel as a future private-transport option, but it is not enabled or tested here; it needs the correct organization/workspace association and permissions, a running client inside the private network, and separately reachable OAuth AS. It is not an access-control workaround or a tunnel setup instruction.
Proceed only when its official documentation explicitly supports remote HTTPS MCP and OAuth. Preserve the client’s native configuration, use the exact resource URL, and let the user complete OAuth. Otherwise stop with the client name and the missing prerequisite.
tobyhired