The client launches a local process and exchanges MCP messages through its input and output streams.
AGENT HUB MCP SETUP
Connect the client, bridge, and tool—on purpose.
Pick your AI client, use the matching transport, and verify one safe action before expanding access. Every path below says whether the client or bridge is first-party, independent, or only an example.
The client connects to a compatible remote endpoint. Authentication and server trust matter.
Claude Code treats SSE as deprecated. Prefer the current HTTP transport for new remote setups.
Codex
Codex supports local stdio servers and remote Streamable HTTP servers. Its CLI and IDE extension use the same MCP configuration.
Open the shared config
On Windows, use $env:USERPROFILE\.codex\config.toml. Back it up before editing.
Add one server
Use a local command for stdio or a URL for Streamable HTTP. Keep names short and unique.
Restart and inspect
Restart the active Codex surface, confirm the server appears, and begin with a read-only tool call.
[mcp_servers.my_local_server]
command = "npx"
args = ["-y", "@publisher/server-package"][mcp_servers.my_remote_server]
url = "https://mcp.example.com/mcp"Example placeholders: replace the package and URL only with values supplied by a server publisher you trust.
ChatGPT desktop
The ChatGPT desktop app supports stdio and Streamable HTTP MCP servers. On the same host, it shares MCP configuration with Codex CLI and the Codex IDE extension.
- 1Open Settings
In the ChatGPT desktop app, open MCP servers.
- 2Add the server
Choose Add server, then enter its stdio command or Streamable HTTP URL.
- 3Restart the app
Fully restart ChatGPT so the desktop host reloads the shared MCP configuration.
- 4Verify with /mcp
Open a chat, enter
/mcp, and confirm the intended server and tools are visible.
ChatGPT web is a separate connection surface.
The browser version does not read your local desktop or Codex configuration. ChatGPT web integrations use plugins and remote tools, so a local stdio bridge must run through the desktop app or another supported local client.
Claude Code
Register servers from the command line. Use stdio for local processes and HTTP for new remote servers; SSE is deprecated.
claude mcp add --transport stdio my-local-server -- npx -y @publisher/server-packageclaude mcp add --transport http my-remote-server https://mcp.example.com/mcpRun claude mcp list after registration. If a server exits immediately, run its command by itself and read the local error before changing the client config.
Claude Desktop
On Windows, local stdio servers are configured in %APPDATA%\Claude\claude_desktop_config.json. JSON requires doubled backslashes inside Windows paths.
{
"mcpServers": {
"my-local-server": {
"command": "npx",
"args": ["-y", "@publisher/server-package"]
}
}
}- 1Close Claude Desktop completely.
- 2Edit valid JSON—one missing comma can stop every server from loading.
- 3Start Claude Desktop again and review the tools it exposes.
Unity 6+ official MCP relay
Supported Unity MCP tooling installs a Windows relay at %USERPROFILE%\.unity\relay\relay_win.exe. It runs with --mcp, and Unity asks you to approve the first connection.
CHECK THE RELAY
Confirm the executable exists.
If the check returns False, update the supported Unity 6 setup and complete Unity's current official MCP installation flow before configuring a client.
Test-Path "$env:USERPROFILE\.unity\relay\relay_win.exe"FIRST CONNECTION
Approval happens inside Unity.
Keep the intended project open, connect from your configured AI client, and approve the prompt only when the displayed client matches. Do not launch the relay as a standalone test: it is a stdio server and will wait for client messages.
Register Unity in your client
[mcp_servers.unity]
command = 'C:\Users\YOUR_NAME\.unity\relay\relay_win.exe'
args = ["--mcp"]claude mcp add --transport stdio unity -- "$env:USERPROFILE\.unity\relay\relay_win.exe" --mcp{
"mcpServers": {
"unity": {
"command": "C:\\Users\\YOUR_NAME\\.unity\\relay\\relay_win.exe",
"args": ["--mcp"]
}
}
}Availability: the relay path and approval flow apply to supported Unity 6+ MCP installations. Older or unsupported editor versions may not include it.
Roblox Studio local bridge
This path uses the existing %LOCALAPPDATA%\Roblox\mcp.bat bridge. It is independent software and is not provided or endorsed by Roblox Corporation.
1 · CONFIRM INSTALLATION
Check the batch file before registering it.
Open and review the file if it came from anywhere other than your own Agent Hub installation.
Test-Path "$env:LOCALAPPDATA\Roblox\mcp.bat"[mcp_servers.roblox_studio]
command = "cmd.exe"
args = ["/c", "cd /d %LOCALAPPDATA%\\Roblox && .\\mcp.bat"]claude mcp add --transport stdio roblox-studio -- cmd.exe /c "cd /d %LOCALAPPDATA%\Roblox && .\mcp.bat"{
"mcpServers": {
"roblox-studio": {
"command": "cmd.exe",
"args": ["/c", "cd /d %LOCALAPPDATA%\\Roblox && .\\mcp.bat"]
}
}
}Keep Studio open only when you intend to use the bridge. Preserve Agent Hub's exclusive-writer rule when multiple agents share the same project.
Other compatible MCP servers
A protocol match is necessary, but it is not a security review. The server publisher owns its install command, permissions, updates, and data handling.
Use stdio
Your client starts a trusted executable or package on the same device. Confirm the exact command and working directory.
Use current HTTP
Your client connects to a URL. Confirm HTTPS, authentication, tenancy, logging, and the server's data policy.
Stop and inspect
Do not improvise a command from a package name. Find the publisher's current instructions and verify the source first.
This guide can help you configure compatible clients, but the current Windows app does not claim native lifecycle management, health checks, or permission control for every arbitrary MCP server.
Verify before the first real task
A server showing “connected” proves transport, not safety. Test the smallest useful capability and keep the result observable.
Confirm identity
Client name, server name, executable or URL, and target project are exactly what you intended.
Start read-only
List available tools or inspect project metadata before allowing any edit, delete, publish, or shell action.
Protect secrets
Keep tokens in the client's supported secret or environment mechanism. Never paste them into this website or a support ticket.
Know how to revoke
Remove the config entry, stop the local relay, revoke remote credentials, and close editor approval when the bridge is no longer needed.
OFFICIAL REFERENCES
Verify against the current source.
Client menus, package versions, and availability can change. These first-party references are the source of truth.