
Mcp Zoop
io.github.codesparPublished by GitHub account codesparv0.1.4Updated Oct 24, 2026
MCP server for Zoop — marketplace payments, splits, sellers, buyers, transfers
Overview
MCP server for the Zoop marketplace payments platform, letting an assistant create transactions, splits, sellers, buyers and transfers.
- What you can do
- Create and look up transactions, including Pix, boleto and credit card payments, with refunds and receivables
- Create and manage split rules that distribute payments between sellers
- Create, update and list sellers and buyers, and read seller or marketplace balances
- Create and list transfers to seller bank accounts, and tokenize cards and bank accounts
- Create, list, get and cancel recurring subscriptions
- List and inspect disputes and chargebacks, and read marketplace settings
- When to use it
- Useful when you work with the Zoop Brazilian marketplace payments platform and want an assistant to draft or inspect transactions, splits, sellers, transfers, subscriptions and disputes through conversation instead of the dashboard.
- Requirements
- Runs locally over stdio, typically launched with npx from the npm package, so Node.js is needed. Requires a Zoop developer account and two environment variables: ZOOP_API_KEY and ZOOP_MARKETPLACE_ID. A sandbox environment is available for testing.
Installation
In SourceWeft
- Open Mcp Zoop 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-zoop
MCP server for Zoop — marketplace payments with split rules
Quick Start
Claude Desktop
Add to ~/.config/claude/claude_desktop_config.json:
Claude Code
Cursor / VS Code
Add to .cursor/mcp.json or .vscode/mcp.json:
Tools (28)
Authentication
Zoop uses Basic Auth with the API key as username and empty password.
Sandbox / Testing
Zoop provides a sandbox environment accessible via the dashboard.
Get your credentials
- Go to Zoop Documentation
- Create a developer account
- Get your API key and marketplace ID from the dashboard
- Set the environment variables
Environment Variables
Roadmap
v0.2 (planned)
get_dispute— Get dispute details by IDrespond_dispute— Respond to a dispute with evidencelist_plans— List all subscription plansupdate_subscription— Update a subscription's detailscancel_subscription— Cancel an active subscription
v0.3 (planned)
batch_transfers— Process multiple transfers in a single requestdetailed_reports— Generate detailed financial reportswebhook_management— Register, list, and delete webhooks
Want to contribute? Open a PR or request a tool.
Links
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/zoop/README.md at commit d0a519a
Tools
0Version history
1- v0.1.4LatestSep 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