EximAgent

npx add-mcp 'https://mcp.eximagent.ai/mcp'

Connect an assistant to EximAgent with OAuth, understand tool permissions and usage, and complete sign-in when a browser cannot open.

Connect EximAgent to an assistant you already use. The hosted MCP server exposes trade tools backed by the same service and corpus as the CLI, without installing the CLI or changing its sandbox permissions.

What you can ask

• Find importers or exporters for a product and market
• Research a company's trade activity and counterparties
• Compare trade corridors, volumes, and market signals
• Enrich a shortlist and screen names before outreach

For example: "Which companies import green coffee into Germany? Show the scope and evidence behind the ranking." Read the returned coverage and confidence labels before drawing a conclusion.

Set it up

Setting	Value
Server URL	https://mcp.eximagent.ai/mcp
Transport	Streamable HTTP
Authentication	OAuth 2.1 with dynamic client registration and PKCE; Google sign-in
Account setup	The same endpoint for everyone; no per-user URL or API key to paste

Your assistant must support remote HTTP MCP servers and OAuth sign-in.

Codex

codex mcp add eximagent --url https://mcp.eximagent.ai/mcp
codex mcp login eximagent
codex mcp list

In a Codex session, use /mcp to check the server's status. See the official MCP configuration guide for host-specific settings.

Claude Code

claude mcp add --transport http eximagent https://mcp.eximagent.ai/mcp --scope user

Then run /mcp inside Claude Code, select EximAgent, and complete sign-in.

Claude desktop and web

Open Customize → Connectors → Add → Add custom connector and paste the server URL. Choose OAuth sign-in and automatic client registration, then complete authorization. On Team and Enterprise workspaces, the connector must first be added in Organization settings → Connectors by someone with permission to manage it. See Claude's custom connector guide for client-specific settings.

Any other host

Add the URL as a remote Streamable HTTP server, then follow the host's OAuth sign-in flow. Do not configure it as a local stdio command.

Signing in when a browser cannot open

For Claude Code, use an interactive terminal:

claude mcp login eximagent --no-browser

Open the printed authorization URL in a browser, complete sign-in, and paste the full redirect URL back into the terminal when prompted. This does not require weakening the assistant's sandbox. See Claude Code's authentication guide.

If you already use the CLI, sign in first and let it configure the Claude Code connector instead:

eximagent login
eximagent connect

connect defaults to Claude Code, writes the host configuration, and verifies the connection by listing tools and resolving the account. It requires an existing CLI credential; it is not itself a login command. For a headless CLI environment, see authentication.

Authentication

The connector acts as the account you authorize. Check that you signed in to the intended account before reading private collections or starting paid work.

Use your host's sign-out or clear-authentication control to disconnect. Removing a connector does not delete collections or other saved EximAgent data.

What it reads and writes

The server labels tools with read-only and destructive-action annotations. Trade lookups are read-only; saving collections, preparing drafts, and starting paid discovery runs change state. Deleting data and sending outreach need particular care. Your host's approval policy determines when it prompts you; annotations are not a substitute for reviewing the requested action.

Preview billable work and approve external actions explicitly. Outreach still passes the service's sending checks, including sanctions screening. See previews and confirmation and outreach.

The connector uses the authorized account's data and the trade corpus. Connecting it does not automatically grant access to your local files, mailbox, or other connectors. Content you explicitly supply to a tool is part of that request.

Usage and troubleshooting

MCP is another way to call EximAgent, not a separate free allowance. Paid work uses the account's applicable usage limits and credits.

• Server added but unavailable: check its status in the host and finish OAuth sign-in; adding the URL alone does not authenticate the account.
• Browser cannot launch: use the Claude Code URL-prompt flow above, or configure the connector from a terminal outside the restricted environment.
• Authentication expired or revoked: sign in again through the host.
• An action is refused: check account permissions, usage limits, and the returned error before retrying. See errors and recovery.

Do not retry an uncertain paid or sending action blindly. Read its returned state before starting another run.

Scripts and API keys

For your own backend or a scheduled script, use a scoped credential rather than copying an assistant's OAuth token. See API keys for collection access, expiry, and revocation.

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.

Privacy and terms

• Privacy policy
• Terms of service
• Contact and support