@txn-dev/mcp-server
# @txn-dev/mcp-server
MCP server for [txn.dev](https://txn.dev) - let any AI assistant manage agent payments.
Works with Claude Desktop, Cursor, Windsurf, and any MCP-compatible client.
## Setup
Add to your MCP client config:
```json
{
"mcpServers": {
"txn": {
"command": "npx",
"args": ["-y", "@txn-dev/mcp-server"],
"env": {
"TXN_API_KEY": "txn_live_..."
}
}
}
}
```
Get your API key at [txn.dev/dashboard/api-keys](https://txn.dev/dashboard/api-keys). A `txn_test_` key moves sandbox money through the same tools, so try it there first.
Claude Code, in one line:
```bash
claude mcp add txn -e TXN_API_KEY=txn_test_... -- npx -y @txn-dev/mcp-server
```
## Tools
| Tool | Description |
|---|---|
| `create_wallet` | Create a new agent wallet |
| `list_wallets` | List all wallets in your org |
| `pay` | Transfer funds between wallets, idempotently |
| `get_balance` | Check a wallet's balance |
| `fund_wallet` | Add money: a Stripe Checkout link for live wallets, sandbox credit for test wallets |
| `find_humans` | Search people available for hire by skill, rate and rating |
| `hire_human` | Escrow a budget and assign a person in one call |
| `post_job` | Post work to the public board and let people apply |
| `list_jobs` | List your jobs, optionally by status |
| `get_job` | A job's status, deliverable and escrow |
| `assign_job` | Pick an applicant for a posted job |
| `release_payment` | Accept delivered work and pay the person |
| `dispute_job` | Send work back with a reason before the acceptance window closes |
## What you can do
Once connected, ask your AI assistant things like:
- "Create a wallet called research-agent"
- "How much is in the translator wallet?"
- "Pay $0.50 from coordinator to summarizer for the report"
- "List all my agent wallets and their balances"
- "Fund the coordinator wallet with $20"
## Environment Variables
| Variable | Required | Description |
|---|---|---|
| `TXN_API_KEY` | Yes | Your txn.dev API key |
## License
MIT
TDQS
Scored across 13 tools
Tools are mostly distinct, but there is potential overlap between pay and release_payment (both move money), and between hire_human and post_job/assign_job (direct hire vs. job board). Descriptions clarify when to use each, but an agent may need to read carefully to avoid misselection.
Most tools follow a consistent verb_noun snake_case pattern (e.g., list_wallets, get_balance, create_wallet, find_humans, hire_human, post_job, release_payment, dispute_job). The single tool 'pay' is an outlier as a bare verb without a noun, slightly breaking the pattern.
With 13 tools, the set is well-scoped for a platform combining wallet management, payments, and human hiring with escrow. Each tool appears to earn its place without excessive redundancy.
Core workflows are covered: wallet creation/funding, payments, finding/hiring humans, job posting, escrow release, and dispute. However, notable gaps exist: no way to cancel a posted job or direct hire to reclaim escrow, no list of direct hires (only posted jobs), and no transaction history or wallet deletion, which could cause dead ends.