Braintree MCP by usefulapi

Server Details

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

If you are the author of this connector, you can claim ownership by verifying the domain or GitHub account it belongs to. Claimed connector authors can inspect health checks, view analytics, and manage their listing.

Status: Healthy
Uptime: 79.3% over 55 days
Last Tested: 2026-10-11 23:21
Transport: Streamable HTTP · MCP 2025-06-18
URL
Repository: m190/usefulapi-mcp
GitHub Stars: 0

TDQS

A4.2/5.0

Scored 2026-07-28 18:40 across 7 tools

Disambiguation4/5

Tools are largely distinct, covering customers, payment methods, transactions, and subscriptions. However, 'list_subscriptions' uses transactions as a proxy, causing potential overlap with 'search_transactions' for customer-scoped searches.

Naming Consistency5/5

All tools follow a consistent 'braintree_verb_noun' pattern (e.g., find_customer, search_transactions, refund_transaction). Verbs are sensible and uniform, making the set predictable.

Tool Count5/5

With 7 tools, the server is well-scoped for a payment gateway. It covers core transaction and customer lookups, plus refund/void operations, without excessive bloat.

Completeness3/5

The set lacks essential CRUD operations like creating or updating customers, payment methods, or transactions. Subscriptions are only partially covered via a workaround, leaving notable gaps for a complete workflow.

Available Tools

7 tools

braintree_customer_payment_methodsList a customer's payment methods

Read-only

Inspect

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 } }.

ParametersJSON Schema

Name	Required	Description	Default
`id`	Yes	GraphQL global Customer ID (opaque).
`first`	No	Max payment methods to return. Default 50.

braintree_find_customerFind a customer

Read-only

Inspect

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.

ParametersJSON Schema

Name	Required	Description	Default
`id`	Yes	GraphQL global Customer ID (opaque). Legacy numeric ids differ — resolve them via a transaction search or the id-conversion query first.

braintree_find_transactionFind a transaction

Read-only

Inspect

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.

ParametersJSON Schema

Name	Required	Description	Default
`id`	Yes	GraphQL global transaction ID (opaque, base64-looking), e.g. from a search result's `node.id`.

braintree_list_subscriptionsList a customer's subscription activity

Read-only

Inspect

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.

ParametersJSON Schema

Name	Required	Description	Default
`first`	No	Max transactions to return. Default 50.
`customerId`	Yes	GraphQL global Customer ID whose recurring/subscription charges to list.

braintree_refund_transactionRefund a transaction

Destructive

Inspect

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.

ParametersJSON Schema

Name	Required	Description	Default
`amount`	No	Partial-refund amount as a decimal string (e.g. "10.00"). Omit for a full refund.
`transactionId`	Yes	GraphQL global transaction ID to refund.

braintree_search_transactionsSearch transactions

Read-only

Inspect

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 }.

ParametersJSON Schema

Name	Required	Description
`first`	No	Max transactions to return (page size). Default 25.
`status`	No	One or more transaction statuses to match (e.g. ["SETTLED","VOIDED"]).
`customerId`	No	GraphQL global Customer ID to filter to one customer's transactions.
`createdAfter`	No	Only transactions created at or after this ISO-8601 timestamp.
`createdBefore`	No	Only transactions created at or before this ISO-8601 timestamp.

braintree_void_transactionVoid a transaction

Destructive

Inspect

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.

ParametersJSON Schema

Name	Required	Description	Default
`transactionId`	Yes	GraphQL global transaction ID to void.