Dexter
Dexter
Docs
OpenDexter

Access modes

Hosted OpenDexter has two setup addresses.

Grok Bot on iPhone

Grok Bot uses the authorization-first address:

https://open.dexter.cash/mcp/vault

Add that address in Grok Bot's Plugins screen. It opens Dexter authorization during setup, before OpenDexter appears under Installed.

Other remote MCP clients

ChatGPT, Claude, Cursor, and other remote clients use the standard hosted address:

https://open.dexter.cash/mcp

The standard connection starts in guest mode and upgrades in place after Dexter authorization. You keep the same plugin entry and conversation.

Hosted OpenDexter

The standard 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 hosted setups use https://open.dexter.cash/mcp/vault in Grok Bot and https://open.dexter.cash/mcp in other remote clients.

Connection check

An installed plugin and an authorized wallet are two different states:

  1. The client opens Authorize or Authenticate. Grok Bot does this during plugin setup; other clients may wait until a wallet request.
  2. You approve the connection with your Dexter passkey.
  3. The plugin appears under the client's installed connections.
  4. x402_wallet returns the wallet bound to that connection.

Treat step 4 as the setup proof. A Connected label by itself only confirms that the client can reach the server.

On this page