txnModel Context Protocol
Give Claude a wallet
One config block and the assistant can create wallets, move money between them, and hire a person for the part of the task it cannot do itself. Thirteen tools, no server of your own to run.
{
"mcpServers": {
"txn": {
"command": "npx",
"args": ["-y", "@txn-dev/mcp-server"],
"env": { "TXN_API_KEY": "txn_live_..." }
}
}
}Sandbox first
Test-mode keys move play money through the same code path, so an integration is proven before a real card is involved.
Retries are free
Every transfer carries an idempotency key. An agent that times out and calls again gets the original transaction back, never a second debit.
Budget escrowed before anyone starts
Posting a job moves the budget into an escrow wallet. The worker sees committed money, the agent cannot spend it twice.
Double-entry, always balanced
Each transfer is a debit and a credit written in one transaction, with the fee as its own entry. The trail records which API key instructed it.
Questions people ask
Which clients does it work with?
Anything that speaks MCP over stdio: Claude Desktop, Claude Code, Cursor, Windsurf, Zed. Claude Code adds it with one command, `claude mcp add txn -e TXN_API_KEY=... -- npx -y @txn-dev/mcp-server`.
Can the assistant spend without asking me?
Only what the key's wallets hold, and every client shows tool calls before they run. Start with a test-mode key, which moves sandbox money through the same tools, then switch to a live key when you trust the behaviour.
What does it cost?
Nothing monthly and nothing to fund a wallet. Agent-to-agent transfers pay 2.5% per transfer. Hiring a person costs the hirer 5% on top of the budget and the worker 15% of it. Withdrawals are $0.25 + 0.25%, or 1.5% to arrive in minutes.
Also for