Skip to main content
Glama
@txn-dev/mcp-server

@txn-dev/mcp-server

by polyxmedia

@txn-dev/mcp-server

MCP server for 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:

{
  "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. A txn_test_ key moves sandbox money through the same tools, so try it there first.

Claude Code, in one line:

claude mcp add txn -e TXN_API_KEY=txn_test_... -- npx -y @txn-dev/mcp-server

Related MCP server: AgentHire 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

Available Tools

13 tools
assign_jobA

Choose which applicant does a job you posted. Everyone else who applied is told no. If they asked for more than the posted budget, pass agreed_amount to accept their price and the extra is escrowed too.

Inputs: job_id (required), worker_id (required), agreed_amount, deliver_in_hours.

create_walletB

Create a new agent wallet for sending and receiving payments

Inputs: name (required), currency.

dispute_jobA

Reject delivered work and say what is wrong with it. The person can then fix it and resubmit. The money stays in escrow: it is neither paid out nor returned to you, because delivered work cannot be taken back for free.

Inputs: job_id (required), reason (required).

find_humansB

Find real people available for hire for work an AI cannot finish alone: anything needing physical presence, a legal signature, local knowledge, licensed expertise, a human judgement call, or an account only a person can open. Returns each person's skills, rate floor, rating, and completed job count.

Inputs: q, limit, skills, max_budget, +1 more.

fund_walletA

Generate a Stripe checkout link to add funds to an agent wallet. Returns a URL the user can open to complete payment.

Inputs: amount (required), wallet_id (required).

get_balanceC

Check the current balance of a specific agent wallet

Inputs: wallet_id (required).

get_jobA

Check on a job you posted or a person you hired: its status, who applied, what they delivered, and how much is still held in escrow. Call this before releasing payment so you can read the delivered work.

Inputs: job_id (required).

hire_humanA

Hire a specific person to do a piece of work. The budget is moved into escrow immediately and is only paid out when you release it, so the money is committed but not spent. Find someone with find_humans first. The person is told the work was commissioned by an AI agent.

Inputs: from (required), title (required), budget (required), worker_id (required), +4 more.

list_jobsA

List the jobs you have posted, newest first. Filter by status to find work waiting on you: 'delivered' is work you need to review and pay for.

Inputs: status.

list_walletsB

List all agent wallets in your organization

Inputs: no named parameters.

payA

Transfer funds from one agent wallet to another. Use when an agent needs to pay for a completed task or service.

Inputs: to (required), from (required), amount (required), memo, +1 more.

post_jobA

Post a job to the public board and let people apply, instead of picking someone yourself. The budget is escrowed when you post. Use this when you do not know who should do the work; use hire_human when you already do. Review applicants with get_job, then choose one with assign_job.

Inputs: from (required), title (required), budget (required), description (required), +3 more.

release_paymentA

Accept delivered work and pay the person. This releases the escrow and cannot be undone, so read the deliverable with get_job first. If the work is not right, use dispute_job instead and they get a chance to fix it.

Inputs: job_id (required), rating, comment.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.6/5.0

    Scored across 13 tools

    Disambiguation4/5

    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.

    Naming Consistency4/5

    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.

    Tool Count5/5

    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.

    Completeness3/5

    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.

    Maintenance

    ActivityStale
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      F
      maintenance
      Enables AI agents to perform financial transactions such as direct payments, escrows, and bounty management using natural language with zero code integration. It provides a comprehensive suite of tools for fund streaming, subscriptions, and reputation tracking to facilitate secure agent-to-agent commerce.
      15 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to hire verified humans for physical-world tasks by posting missions with budgets, managing claims and proof, and releasing escrow payments upon validation.
      1
      MIT