
Mcp Braintree
io.github.codesparPublished by GitHub account codesparv0.2.2Updated Oct 24, 2026
MCP server for Braintree (PayPal) — global card processing via GraphQL: charge, refund, vault
Overview
MCP server for Braintree (PayPal) card payments: authorize, charge, refund, vault payment methods and manage customers and disputes via GraphQL.
- What you can do
- Authorize, charge, capture, void, refund and submit transactions for settlement
- Vault, update, verify and delete stored payment methods
- Create, update, search and delete customers
- Look up and search transactions, customers, disputes and merchant accounts
- Mint client tokens for browser or mobile tokenization
- When to use it
- Useful when you already hold a Braintree merchant account and want an assistant to handle payment operations, vaulting and customer management, for example a SaaS selling to US or EU buyers. Start in the sandbox environment to test flows before touching production.
- Requirements
- Runs locally over stdio via the npm package (npx), or over HTTP when MCP_HTTP and MCP_PORT are set. Needs a Braintree merchant account and the environment variables BRAINTREE_MERCHANT_ID, BRAINTREE_PUBLIC_KEY and BRAINTREE_PRIVATE_KEY, plus optional BRAINTREE_ENV (sandbox by default) and BRAINTREE_API_VERSION. Network access to the Braintree GraphQL endpoint.
Installation
In SourceWeft
- Open Mcp Braintree in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
@codespar/mcp-braintree
MCP server for Braintree (PayPal) — global card processing via the Braintree GraphQL API.
Target customer: LatAm SaaS selling to US/EU buyers who already hold a Braintree merchant account and want agent-driven payments, vaulting, and customer management.
Tools (22)
Install
Environment
Endpoints:
sandbox→https://payments.sandbox.braintree-api.com/graphqlproduction→https://payments.braintree-api.com/graphql
Authentication
Braintree's GraphQL endpoint accepts HTTP Basic auth with PUBLIC_KEY:PRIVATE_KEY base64-encoded. Every request also requires a Braintree-Version: YYYY-MM-DD header — the server defaults to 2019-01-01 and can be overridden with BRAINTREE_API_VERSION.
Payment method ids
Most mutations take a paymentMethodId. These come from client-side tokenization (Braintree Drop-in / Hosted Fields / SDKs) — the server does not accept raw PANs. Use create_client_token to mint a token for the browser or mobile SDK.
Run
Notes
- Amount is a string in Braintree GraphQL (e.g.
"10.50"), not a number. The server forwards whatever shape the agent passes; strings are the safe default. - Braintree's GraphQL schema evolves; some input fields not exposed in the MCP
inputSchemacan still be passed inadditional/ nested objects and will be forwarded.
Enterprise
Need governance, budget limits, and audit trails for agent payments? CodeSpar Enterprise adds policy engine, payment routing, and compliance templates on top of these MCP servers.
License
MIT
Source: packages/payments/braintree/README.md at commit d0a519a
Tools
0Version history
1- v0.2.2LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts