Prerequisites
- A XentFi account (Sign up)
- Node.js 18+ available wherever your MCP client spawns tools (most desktop clients bundle their own)
- One of the supported clients: Claude Desktop, Claude Code, Cursor, VS Code, ChatGPT, ElizaOS, CrewAI, or OpenAI Codex/Agents SDK
Step 1: Create an Agent and get its API key
1
Log into Dashboard
Navigate to dashboard.xentfi.com.
2
Create an Agent
Go to Agents → New Agent. This is the identity your AI will act as — separate from your own dashboard login.
3
Attach a Policy
Under Policies, create or attach a spend policy to the agent: per-transaction / daily / weekly / monthly USD limits, an allowed-recipients list, and (optionally) allowed hours. This is what keeps an autonomous agent from overspending or paying the wrong address — XentFi enforces it server-side on every payment.
4
Generate the API key
From the agent’s page, generate an new Agent. Copy the Agent key — it’s shown once.
Step 2: Set your environment variables
Step 3: Connect an MCP client
The fastest path is Claude Desktop. Add this to your MCP config (see Claude Desktop guide for the exact file path):xentfi server appears with 15 tools available.
Step 4: Make your first agent tool call
Ask your agent:“Check my XentFi agent info and list my wallets.”Behind the scenes this calls
xentfi_get_agent_info then xentfi_list_wallets:
data is empty, have the agent call xentfi_create_wallet first (see Tools Reference).
Step 5: Try a policy-checked payment
“Send 1 USDC to 0x… from my wallet.”This calls
xentfi_create_payment, which requires an explicit confirm: true and is evaluated against the agent’s Policy server-side:
POLICY_DENIED result instead of a silent failure — see Error Handling.
Next steps
Tools Reference
Every tool, its arguments, and what it returns.
Choose your client
Guides for Claude, Cursor, VS Code, ChatGPT, ElizaOS, CrewAI, and Codex.
Remote deployment
Run a shared, multi-tenant MCP endpoint instead of a local process.
Error handling
How policy denials and API errors surface to the agent.

