Braintree MCP server

Read from the package source without running it. The installed server may list more.

• accept_dispute

  Accept liability for a dispute via acceptDispute — the merchant concedes and the disputed amount is refunded to the buyer. Terminal action, cannot be undone.

• authorize_transaction

  Authorize a transaction (reserve funds without capturing) via Braintree GraphQL authorizePaymentMethod. Pass a paymentMethodId obtained from client-side tokenization (Drop-in / Hosted Fields / SDK nonce). Capture later with capture_transaction.

• capture_transaction

  Capture a previously authorized transaction via captureTransaction. Amount defaults to full authorized amount when omitted (partial captures allowed up to the authorized total).

• charge_transactionwrite action

  Authorize and capture a transaction atomically via Braintree GraphQL chargePaymentMethod. Use for one-step sales. For auth-now-capture-later split, use authorize_transaction + capture_transaction.

• create_client_tokenwrite action

  Mint a Braintree client token via createClientToken for client-side tokenization (Drop-in, Hosted Fields, mobile SDKs). Pass a customerId to scope the token to a customer for vault-aware flows.

• create_customerwrite action

  Create a Braintree customer via createCustomer. Customers group multiple vaulted payment methods and transactions under one identity.

• delete_customerwrite action

  Delete a Braintree customer via deleteCustomer. Irreversible — also deletes any payment methods vaulted against the customer.

• delete_payment_methodwrite action

  Delete a vaulted payment method via deletePaymentMethodFromVault. Irreversible — the token cannot be used for future charges after deletion.

• finalize_dispute

  Finalize a dispute via finalizeDispute — submits previously added evidence to the card network for review. After finalization, no further evidence can be added.

• find_customer

  Search for customers via the GraphQL search.customers query. Pass one of email / firstName / lastName / company to filter; returns matching customer nodes. Leave all blank to list the first page of customers.

• find_dispute

  Fetch a dispute by id via the GraphQL node(id:) query. Returns id, status, reason, amountDisputed, receivedDate, replyByDate.

• find_merchant_account

  Fetch a merchant account by id via the GraphQL node(id:) query. Returns id, status, currencyCode, and default flag — useful for multi-currency / multi-entity merchants.

• get_customer

  Fetch a customer by id via the GraphQL node(id:) query. Returns customer scalars (id, firstName, lastName, email, company, phone).

• get_transaction

  Fetch a transaction by id via the GraphQL search.transactions query. Returns id, status, amount, orderId, createdAt, and the associated payment method.

• refund_transactionwrite action

  Refund a settled transaction via refundTransaction. Amount defaults to the full settled amount when omitted. For partial refunds, pass a smaller amount.

• search_transactions

  Search transactions via the GraphQL search.transactions query. Filter by status / customerId / orderId / createdAt range. Returns a page of transaction nodes with id, status, amount, orderId, createdAt.

• submit_for_settlementwrite action

  Submit a previously authorized transaction for settlement via submitTransactionForSettlement. Unlike capture_transaction (captureTransaction), this marks the transaction for the next settlement batch and supports optional order id / descriptor overrides.

• update_customerwrite action

  Update an existing Braintree customer via updateCustomer. Only fields present in the request are updated.

• update_payment_methodwrite action

  Update metadata on a vaulted payment method via updatePaymentMethod. Use to change billing address, cardholder name, expiration, or set-as-default flag without re-tokenizing.

• vault_payment_method

  Permanently store a tokenized payment method in the Braintree vault via vaultPaymentMethod. The input paymentMethodId must be a single-use nonce; the mutation returns a permanent vaulted payment method id that can be reused for future charges.

• verify_payment_methodwrite action

  Run a credit-card verification (zero-auth or $1 auth) on a tokenized payment method via verifyPaymentMethod. Returns a CreditCardVerification with status and processor response. Useful before vaulting or charging.

• void_transaction

  Void an unsettled transaction (reverse the authorization) via reverseTransaction. Use when funds are authorized but not yet captured — for captured/settled transactions use refund_transaction instead.

• Code scan5 source files scanned25/25
• –Live reliabilityno gateway calls yet and no remote to proben/a
• –Tool poisoningtools not inspected (local package is not executed); not countedn/a
• Auth qualitystatic API keys via environment variables6/15
• Maintenancelast push 29 days ago15/15
• Maintainer identityregistry namespace matches repository owner7/10

Safety score

82/100

higher than 63% of 48,255 servers

Tools

22

the typical server has 7

Tools that change things

45%

typical: 0%. Fewer write tools means less an agent can break

GitHub stars

271

more than 95% of 28,688 servers

Downloads a week

29

more than 16% of 12,191 servers with a package

Braintree: common questions

Is Braintree MCP server safe?

Mostly: it is graded B (82/100). Read the Braintree safety report

How do I install Braintree?

It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.

Does Braintree need an API key?

Yes. The registry entry asks for BRAINTREE_PRIVATE_KEY.

Is Braintree maintained?

The last commit was 67 days ago (2026-08-29). The latest release is v0.2.2.

How does Braintree compare with other MCP servers?

safety score 82/100 (higher than 63% of 48,255 servers); tools 22 (the typical server has 7); tools that change things 45% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.