@xentfi/mcp-server is the official Model Context Protocol (MCP) server and SDK for XentFi. It exposes an agent’s XentFi wallet, spend policy, and payment capabilities as MCP tools, so any MCP-compatible client can call them directly — no custom integration code required.
Why MCP for agents
XentFi’s core API (see API Reference) is built for backends and dashboards. Agent workloads are different: an autonomous agent needs to discover what it can do, call tools with structured arguments, and get back errors it can reason about — all inside whatever chat or agent runtime it already lives in. MCP standardizes exactly that interface, and@xentfi/mcp-server wires it straight into the /v1/agent-self/* and /v1/assets/* surface of the XentFi API.
What you get
🔑 One credential
Your agent’s XentFi API key authenticates every tool call — no separate OAuth flow to build.
🛡️ Server-side guardrails
Every payment is checked against the agent’s XentFi Policy (limits, allowlists, allowed hours) before it executes — enforced by the API, not the client.
🔌 Two transports
xentfi-mcp (stdio) for local desktop clients, xentfi-mcp-http (Streamable HTTP) for remote and multi-tenant deployments.🧩 Programmatic SDK
Import
createXentfiMcpServer() or the raw XentfiClient to embed XentFi tools in your own MCP server or agent framework.The agent tool surface
@xentfi/mcp-server exposes 15 tools, all prefixed xentfi_, across four areas: Agent & Wallets, Policy, Payments, and Market Data. See the full Tools Reference for input/output details.
Get started
Quickstart
Get an API key and connect your first MCP client in a few minutes.
Tools Reference
Every
xentfi_* tool, its arguments, and what it returns.Claude Desktop / Code
The most common way people run this today.
Remote HTTP deployment
For ChatGPT connectors and shared/multi-tenant deployments.
Relationship to the core API
Agent tools call the same/v1/agent-self/* and /v1/assets/* routes documented in API Reference — @xentfi/mcp-server doesn’t add new backend behavior, it just exposes that surface as MCP tools with agent-friendly names, descriptions, and error messages. If you’re building an agent that needs to make payments through x402 rather than manage its own wallet directly, see the x402 Facilitator tab instead.