Access modes

New hosted connections use one address:

https://open.dexter.cash/mcp

Add that address to Grok Bot, ChatGPT, Claude, Cursor, or another remote MCP client. The connection starts in guest mode and upgrades in place after Dexter authorization. You keep the same plugin entry and conversation.

Hosted OpenDexter

The hosted address lists these tools in guest mode:

• x402_search
• x402_check
• x402_access
• x402_wallet
• dexter_portfolio

Search, quote inspection, and wallet-proof access can begin without a wallet connection. A wallet or portfolio call asks the host to open Dexter authorization. Approve that request with your passkey to bind your Dexter Wallet.

After authorization, OpenDexter adds payment status, execution, asset actions, reconciliation, and wallet history. Wallet data and spending authority come from the passkey-bound Dexter account.

Use hosted OpenDexter when the agent runs in a remote app or when you want the same Dexter Wallet available across clients.

Local OpenDexter

Run the maintained package on a machine you control:

npx @dexterai/opendexter@latest setup

The setup command configures supported local clients such as Codex, Claude Code, Cursor, VS Code, Windsurf, and Gemini CLI. Follow the wallet and sign-in instructions it prints, then start a new client session.

Use one OpenDexter registration per client. A hosted registration in one client and a local installation in another can share the same Dexter account.

Existing Dexter MCP integrations

https://mcp.dexter.cash/mcp remains available for older account-linked integrations. New Grok Bot and remote MCP setups use https://open.dexter.cash/mcp, which combines guest discovery with passkey OAuth on one connection.

Connection check

Guest access and an authorized wallet are separate states:

1. The plugin appears under the client's installed connections.
2. x402_search returns public results without Dexter sign-in.
3. A wallet request opens Authorize or Authenticate.
4. You approve the connection with your Dexter passkey.
5. x402_wallet returns the wallet bound to that connection.

Steps 2 and 5 prove the guest and wallet states separately. A Connected label by itself only confirms that the client can reach the server.