braintree
Server Details
Search Braintree transactions, customers and payment methods, and refund or void charges.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- m190/usefulapi-mcp
- GitHub Stars
- 0
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Score is being calculated. Check back soon.
Available Tools
7 toolsbraintree_customer_payment_methodsList a customer's payment methodsRead-onlyInspect
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 } }.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | GraphQL global Customer ID (opaque). | |
| first | No | Max payment methods to return. Default 50. |
braintree_find_customerFind a customerRead-onlyInspect
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.
| 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 transactionRead-onlyInspect
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.
| 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 activityRead-onlyInspect
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.
| 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 transactionDestructiveInspect
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.
| 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 transactionsRead-onlyInspect
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 }.
| Name | Required | Description | Default |
|---|---|---|---|
| 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 transactionDestructiveInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| transactionId | Yes | GraphQL global transaction ID to void. |
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!