@yativo/mcp-server
The Yativo MCP Server exposes Agentic Wallet operations as Model Context Protocol tools. Any MCP-compatible AI agent (Claude, GPT, custom agents) can manage crypto wallets, send payments, and interact with x402-paywalled APIs through a standardized tool interface.Package:
@yativo/mcp-server on npmInstallation
Configuration
The MCP server is configured via environment variables:| Variable | Required | Default | Description |
|---|---|---|---|
YATIVO_API_KEY | Yes | — | Connector API key (starts with yac_) from your agentic wallet |
YATIVO_WALLET_ID | No | — | Default wallet ID (starts with aw_). Can be overridden per tool call |
YATIVO_API_URL | No | https://crypto-api.yativo.com/api/v1 | API base URL. Change for sandbox testing |
Setup with Claude Desktop
Add to your Claude Desktop config (claude_desktop_config.json):
Available Tools
get_balance
Check the balance and address of your agentic wallet.
| Parameter | Type | Required | Description |
|---|---|---|---|
wallet_id | string | No | Wallet ID (uses YATIVO_WALLET_ID default) |
send_payment
Send a crypto payment with full audit trail fields.
| Parameter | Type | Required | Description |
|---|---|---|---|
recipient_address | string | Yes | Destination wallet address |
amount | number | Yes | Amount in USD |
asset | string | No | Asset to send (default: USDC) |
chain | string | No | Chain override (e.g., base, ethereum) |
service_name | string | Yes | Name of the service being paid |
service_url | string | No | URL of the service |
payment_reason | string | Yes | Why this payment is being made |
payment_category | string | No | Category: ai_service, subscription, purchase, transfer, etc. |
wallet_id | string | No | Wallet ID (uses default) |
x402_fetch
Fetch a URL with automatic x402 payment support. If the URL returns HTTP 402 (Payment Required), the wallet auto-pays and retries.
| Parameter | Type | Required | Description |
|---|---|---|---|
url | string | Yes | URL to fetch |
method | string | No | HTTP method (default: GET) |
headers | object | No | Additional request headers |
body | any | No | Request body for POST/PUT/PATCH |
wallet_id | string | No | Wallet ID (uses default) |
get_transactions
Get recent transaction history for the wallet.
| Parameter | Type | Required | Description |
|---|---|---|---|
wallet_id | string | No | Wallet ID (uses default) |
page | number | No | Page number (default: 1) |
limit | number | No | Results per page (default: 10, max: 100) |
Resources
The server exposes an MCP resource for wallet information:| Resource URI | Description |
|---|---|
wallet://info | JSON snapshot of the default wallet’s balance and address |
Running Directly
Prerequisites
Before using the MCP server, you need:- A Yativo account with an agentic wallet
- An activated wallet with at least one connector
- The connector’s API key (
yac_...) - Funds (USDC) in the wallet
Next Steps
Agentic Wallets
Create and configure agentic wallets via the API.
x402 Protocol
Learn more about HTTP-native micropayments.
TypeScript SDK
For programmatic (non-MCP) integration, use the TypeScript SDK.
Sandbox
Test the MCP server against the sandbox environment.

