@ardensh/mcp
v0.1.5
Published
Give your AI agents a wallet, a budget, and the ability to pay — from Claude, Cursor, or any MCP client. Provision agents, execute payments, enforce budgets, and manage vendor allowlists via natural language.
Readme
@ardensh/mcp
Your AI agents can now pay for things — provision wallets, set budgets, and execute payments without leaving your AI assistant.
Arden gives each agent its own wallet and a budget. When the agent needs to pay, Arden checks the budget and vendor allowlist, then executes the payment on Base. This MCP server exposes the full payment lifecycle via natural language in Claude Desktop, Cursor, Claude Code, or any MCP-compatible client.
"Pay $0.01 to exa.ai from my researcher agent"
Tools
| Tool | Description |
|---|---|
| arden_provision_agent | Create a new agent with a wallet, budget limits, and vendor restrictions |
| arden_list_agents | List all agents with spend and budget usage |
| arden_agent_status | Detailed status and budget breakdown for a specific agent |
| arden_update_agent | Adjust an agent's budgets, allowed vendors, or pause it |
| arden_fund_agent | Get wallet address and USDC funding instructions |
| arden_pay | Execute a payment from an agent wallet with budget enforcement |
| arden_check_payment | Dry-run a payment check without moving money |
| arden_check_balance | Read an agent's live USDC balance on Base |
Setup
1. Add to Claude Desktop
Add this to ~/Library/Application Support/Claude/claude_desktop_config.json:
{
"mcpServers": {
"arden": {
"command": "npx",
"args": ["-y", "@ardensh/mcp"],
"env": {
"ARDEN_API_KEY": "arden_live_..."
}
}
}
}Get your ARDEN_API_KEY by running arden login (see below), or find it at arden.sh.
2. Add to Claude Code
claude mcp add arden -- npx -y @ardensh/mcpIf you haven't run arden login on this machine, pass your key explicitly:
claude mcp add arden -e ARDEN_API_KEY=arden_live_... -- npx -y @ardensh/mcp3. Add to Cursor
Add the same block as the Claude Desktop config above to Settings → MCP.
Authentication
The server looks for credentials in this order:
ARDEN_API_KEYenvironment variable~/.arden/config.json(written byarden login)
If you've already installed the Arden CLI and run arden login, no env var is needed.
npm install -g @ardensh/cli
arden loginDevelopment
npm install
npm run dev # run with tsx (no build step)
npm run build # compile to dist/