Skip to main content
Glama
Dexter-DAO

opendexter

Official
by Dexter-DAO

OpenDexter starts with the job, not the provider. Ask for an image model, a market-data feed, an address validator, or another paid capability. It searches the current catalog, explains why each result matches, checks the selected endpoint's current terms, and can make the call from a wallet whose authority you chose.

Choose how it runs

OpenDexter has two deliberately different ways to hold payment authority.

Hosted connector

Local package

Best for

Chat clients with remote MCP and OAuth

Codex, Claude Code, Cursor, VS Code, Windsurf, Gemini CLI, scripts

Runs

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

On your machine through npm/stdio

Wallet

Passkey-protected Dexter Wallet, bound to the authenticated session

Solana and EVM keys stored locally, or keys supplied through environment variables

Networks

Solana

Solana plus configured EVM networks

Setup

Add one MCP URL; the client handles OAuth when a protected tool needs it

Run the setup command below

Spending policy

Managed by the hosted wallet experience

Default per-call limit and optional rolling 24-hour budget stored on this machine

The Codex and Claude Code plugins connect to the hosted service. The local npm package runs a separate stdio MCP and uses an explicitly configured local signer for payments.

Local: start in one command

npx @dexterai/opendexter@latest setup

setup creates or loads the local wallet, detects supported AI clients, configures the clients it can edit safely, and prints any remaining manual step plus the shortest path to a first search. To target one client:

npx @dexterai/opendexter@latest install --client cursor

Use claude-code, codex, vscode, windsurf, or gemini-cli in place of cursor. The Claude Code route adds only the local stdio MCP. To add that connection directly:

claude mcp add --scope user opendexter -- npx -y @dexterai/opendexter@latest

This local installer never adds the repository's hosted Claude Code plugin. For a manual stdio MCP configuration in another client:

{
  "mcpServers": {
    "opendexter": {
      "command": "npx",
      "args": ["-y", "@dexterai/opendexter@latest"]
    }
  }
}

See the local package guide for wallet, policy, client, CLI, and seller workflows.

Hosted connector

Clients with remote MCP and OAuth use this URL:

{
  "mcpServers": {
    "opendexter": {
      "url": "https://open.dexter.cash/mcp"
    }
  }
}

The release contract uses native client sign-in when a protected tool requires it. Connector sign-in, wallet enrollment, and a paid call are three separate events:

  • signing in lets the client call account-protected tools;

  • enrolling the passkey wallet creates or resumes the user's payment authority;

  • calling x402_fetch can move USDC under that wallet's limits.

Connecting does not itself approve a payment. Never paste a bearer token into the MCP configuration.

The connector and OAuth identities are related but deliberately not interchangeable:

  • MCP resource and connector: https://open.dexter.cash/mcp

  • authorization-server issuer: https://mcp.dexter.cash/mcp

  • access-token issuer: https://dexter.cash

Install the hosted plugins

Codex:

codex plugin marketplace add Dexter-DAO/opendexter-ide --ref main
codex plugin add opendexter@dexter
codex mcp login opendexter

Claude Code:

claude plugin marketplace add Dexter-DAO/opendexter-ide --scope user
claude plugin install opendexter@opendexter --scope user
claude mcp login opendexter

Start a fresh task so the client can discover the package. Protected hosted tools then use the client's native MCP OAuth action. The local npm package and the hosted plugin should not both register an opendexter server in one client.

Related MCP server: GenTech Agent Kit

From request to result

OpenDexter keeps discovery and spending separate:

  1. Find. x402_search searches the live catalog using the user's actual request. Results include strong and related matches, ranking reasons, quality evidence, structured input guidance when available, and advertised payment routes.

  2. Inspect. x402_check probes the exact URL and method without paying. It returns current per-chain pricing, accepted assets, schemas when published, and whether the endpoint is paid, identity-gated, API-key protected, or unprotected.

  3. Call. x402_fetch makes one exact prepared request and, when required, settles a compatible payment within the active policy.

  4. Receive. The tool returns the provider response with settlement detail when payment succeeds.

Search cards are leads, not payment authorization. Check the selected route again before spending. If a dispatched payment has an uncertain outcome, do not blindly retry it; reconcile the first attempt before another payment can be safe.

What the local package exposes

The local product documentation routes agents through seven tools:

Tool

What it does

Moves money?

x402_search

Finds services by capability in the OpenDexter catalog

No

x402_check

Reads current price, route, schema, and authentication requirements

No

x402_access

Uses a wallet signature for Sign-In-With-X access

No payment

x402_fetch

Calls an endpoint and settles a compatible x402 charge when required

Yes

x402_wallet

Shows local addresses and verified balance reads

No

x402_settings

Reads or changes this installation's spending policy

No

dexter_portfolio

Reads the governed portfolio from an explicitly linked Dexter account

No

The hosted product deliberately differs. It does not expose the filesystem-backed x402_settings tool. It presents six model-facing tools, including a session-bound governed portfolio read. Five app-only compatibility endpoints remain raw-callable for a dated transition but are not product routes. The server's advertised visibility is authoritative.

Wallets and authority

Local wallet

The npm package creates a Solana keypair and an EVM keypair at:

~/.dexterai-mcp/wallet.json

The directory and file are created with owner-only permissions. You can supply DEXTER_PRIVATE_KEY or SOLANA_PRIVATE_KEY for Solana and EVM_PRIVATE_KEY for EVM instead; environment variables take precedence over the wallet file.

Local balance and signing support is configured for Solana, Base, Polygon, Arbitrum, Optimism, Avalanche, BNB Chain, and SKALE. An endpoint still decides which network and asset it accepts; x402_check shows the actual options before a paid call.

Local connect

npx @dexterai/opendexter@latest connect creates a read-only account link for hosted wallet and portfolio views. It labels that account separately from local payment authority.

It does not change the payment signer used by the local MCP server, fetch, or pay. Local paid calls still use the local wallet file or configured environment keys. See Connect your Dexter wallet for the exact boundary.

Spending policy

The local package stores a default per-call USDC limit and can enforce an optional rolling 24-hour budget. A caller can supply a different limit for one call, so the stored value is not an immutable wallet ceiling. The rolling budget counts only x402 spending witnessed by this installation on this machine; it is not a complete view of the wallet's on-chain activity.

npx @dexterai/opendexter@latest settings
npx @dexterai/opendexter@latest settings --max-amount 2.50 --daily-budget 20

Build or sell

  • Build an x402 client or server: use @dexterai/x402.

  • Prepare a compatible service for discovery: run npx @dexterai/opendexter@latest audition https://your-service.example. Audition performs real paid test calls, so use a testable endpoint and fund only the amount you intend those tests to spend.

  • Inspect the protocol: read the x402 specification.

Repository map

Path

Audience

packages/mcp

Published local CLI and stdio MCP package

plugins/opendexter

Developer-distributed Codex package for the hosted MCP

opendexter-plugin

Developer-distributed Claude Code package for the hosted MCP

chatgpt-app-binding

Publisher-side ChatGPT app identity; not a portable plugin

packages/x402-mcp-tools

Shared MCP tool implementations

packages/mcp-instructions

Roster-aware agent instructions

License

MIT

A
license - permissive license
-
quality - not tested
C
maintenance

Maintenance

Maintainers
Response time
Release cycle
Releases (12mo)
Commit activity
Issues opened vs closed

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Servers

  • F
    license
    A
    quality
    -
    maintenance
    An MCP server that transforms SKILL.md files into executable tools for AI agents, allowing them to discover and pay for services via the x402 protocol. It supports automatic payments on Stellar and EVM networks, enabling seamless integration of premium API skills.
    Last updated
    6
    5
    1
  • A
    license
    -
    quality
    D
    maintenance
    MCP server for the x402 protocol that lets AI agents discover and call payment-gated HTTP APIs automatically.
    Last updated
    122
    Apache 2.0

View all related MCP servers

Related MCP Connectors

  • MCP server connecting AI agents to non-custodial staking data across 130+ networks.

  • Agent-commerce MCP server for x402/USDC payments and affiliate splits on Base.

  • MCP server for AI agents to plan, verify, and deploy Cloudflare-native apps.

View all MCP Connectors

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Dexter-DAO/opendexter-ide'

If you have feedback or need assistance with the MCP directory API, please join our Discord server