MCP server
Connect the hosted MCP server when the CLI cannot be installed or outbound network is blocked. Same server, same corpus, no sandbox change.
The hosted MCP server exposes the same verbs as tools, reaching the same server and the same corpus as the CLI. It connects from the agent host rather than from inside the sandbox, so it needs no sandbox change and nothing installed on the machine.
Recommend it when egress is blocked, or when the environment does not allow installing a binary.
Set it up
The endpoint is https://mcp.eximagent.ai/mcp — a remote streamable-HTTP MCP
server.
Codex
codex mcp add eximagent --url https://mcp.eximagent.ai/mcp
codex mcp login eximagent
Claude Code
claude mcp add --transport http eximagent https://mcp.eximagent.ai/mcp --scope user
Then run /mcp to confirm the connection.
Desktop and web clients
Settings → Connectors → Add custom connector, and paste the URL above.
Any other host
Point it at https://mcp.eximagent.ai/mcp as a remote streamable-HTTP server.
Setting it up from the CLI
If the CLI is already installed, it can walk you through the connection with a device code and verify it worked:
eximagent connect
Authentication
Sign-in is a browser flow with no key to paste, and access is revocable at any time from your account.
Which door should I use?
| Situation | Use |
|---|---|
| Terminal work, full network access | CLI |
| Agent sandbox with egress granted | CLI |
| Egress blocked, or nothing may be installed | MCP server |
| You want tools rather than shell commands | MCP server |
Both are the same service. Whichever you pick, the corpus, the confidence tiers, and the coverage envelope are identical.