Skip to content

Braintree MCP by usefulapi

by usefulapi.io · remote · no sign-in to list tools · v1.16.3 · published by io.usefulapi

Search Braintree transactions, customers and payment methods, and refund or void charges.

Deletes · 2
CompareRegistry entry

7 tools: 2 can delete or cancel things and 5 only read.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http braintree https://braintree.usefulapi.io/mcp

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

7 tools

Deletes or cancels 2Claude Code: deny
  • braintree_refund_transactionDESTRUCTIVE.No findings

    Why it is in this group

    • The name "braintree_refund_transaction" says "refund": a word that usually means money moves, which cannot be taken back.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    DESTRUCTIVE. Refund a SETTLED (or settling) transaction, returning money to the customer. Use the GraphQL global transaction ID. Omit `amount` for a full refund, or pass a decimal string for a partial refund. GraphQL mutation `refundTransaction`. For transactions not yet settled, use braintree_void_transaction instead.

    Annotations the server declares

    • title: Refund a transaction
    • destructiveHint: true
  • braintree_void_transactionDESTRUCTIVE.No findings

    Why it is in this group

    • The name "braintree_void_transaction" says "void": a word for removing or ending something.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    DESTRUCTIVE. Void (cancel) a transaction that has NOT yet settled — e.g. an authorization or one submitted-for-settlement. Use the GraphQL global transaction ID. GraphQL mutation `voidTransaction`. For already-settled transactions use braintree_refund_transaction instead.

    Annotations the server declares

    • title: Void a transaction
    • destructiveHint: true
Only reads 5Claude Code: allow
  • braintree_customer_payment_methodsList the vaulted payment methods (credit cards, PayPal accounts, etc.) for one customer, by GraphQL global Customer ID.No findings

    Why it is in this group

    • The description's first verb is "list": a word for reading.
    Description, as the server wrote it
    List the vaulted payment methods (credit cards, PayPal accounts, etc.) for one customer, by GraphQL global Customer ID. Returns each method's id, legacyId, usage, created-at, and detail type. GraphQL `node { ... on Customer { paymentMethods } }`.

    Annotations the server declares

    • title: List a customer's payment methods
    • readOnlyHint: true
  • braintree_find_customerFetch one customer by GraphQL global Customer ID via the `node` query.No findings

    Why it is in this group

    • The name "braintree_find_customer" says "find": a word for reading.
    Description, as the server wrote it
    Fetch one customer by GraphQL global Customer ID via the `node` query. Returns id, legacyId, name, company, and created-at. To also enumerate stored cards/PayPal accounts use braintree_customer_payment_methods.

    Annotations the server declares

    • title: Find a customer
    • readOnlyHint: true
  • braintree_find_transactionFetch one transaction by its GraphQL global ID (the opaque `id` returned by braintree_search_transactions, NOT the short legacy id).No findings

    Why it is in this group

    • The name "braintree_find_transaction" says "find": a word for reading.
    Description, as the server wrote it
    Fetch one transaction by its GraphQL global ID (the opaque `id` returned by braintree_search_transactions, NOT the short legacy id). Uses the GraphQL `node` query. Returns amount, status, timestamps, order id, and the linked customer.

    Annotations the server declares

    • title: Find a transaction
    • readOnlyHint: true
  • braintree_list_subscriptionsList a customer's recurring / subscription payment activity.No findings

    Why it is in this group

    • The name "braintree_list_subscriptions" says "list": a word for reading.
    Description, as the server wrote it
    List a customer's recurring / subscription payment activity. IMPORTANT: Braintree's GraphQL API does NOT expose native Subscription objects (recurring-billing management is still legacy-API only — see braintree/graphql-api issue #1). This tool therefore returns the customer's transactions (the observable evidence of subscription charges) via a TransactionSearchInput scoped to the customer; inspect each node's status/amount/createdAt to trace recurring charges. For full subscription CRUD you must use Braintree's legacy server SDK / REST API.

    Annotations the server declares

    • title: List a customer's subscription activity
    • readOnlyHint: true
  • braintree_search_transactionsSearch transactions by created-at date range, status, and/or customer.No findings

    Why it is in this group

    • The name "braintree_search_transactions" says "search": a word for reading.
    Description, as the server wrote it
    Search transactions by created-at date range, status, and/or customer. Builds a TransactionSearchInput (operators: status `in`, createdAt `greaterThanOrEqualTo`/`lessThanOrEqualTo`, customer.id `is`). Returns a page of transaction nodes (id, legacyId, amount, status, createdAt). GraphQL `search { transactions }`.

    Annotations the server declares

    • title: Search transactions
    • readOnlyHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 1.16.3. Values in angle brackets are yours to fill in.

claude mcp add --transport http braintree https://braintree.usefulapi.io/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__braintree__braintree_find_transaction",
      "mcp__braintree__braintree_search_transactions",
      "mcp__braintree__braintree_find_customer",
      "mcp__braintree__braintree_customer_payment_methods",
      "mcp__braintree__braintree_list_subscriptions"
    ],
    "ask": [],
    "deny": [
      "mcp__braintree__braintree_refund_transaction",
      "mcp__braintree__braintree_void_transaction"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as braintree. Review it before you use it.