Mcp Pagar Me
Wire Pagar.me orders, charges, recipients, and transfers into your agent so you can automate Brazilian payment flows without hand-crafting API calls.
Overview
io.github.codespar/mcp-pagar-me is a MCP server for the Build phase that exposes Pagar.me orders, charges, recipients, and transfers to your coding agent.
What is this MCP server?
- stdio MCP via npm package @codespar/mcp-pagar-me (v0.1.2)
- Covers four Pagar.me domains: orders, charges, recipients, and transfers
- Requires PAGARME_API_KEY secret env var before the server starts
- Part of codespar mcp-dev-brasil payments monorepo on GitHub
- Agent-callable tools instead of one-off REST scripts for recurring ops
- Server version 0.1.2 on MCP schema 2025-12-11
- 1 required secret env var: PAGARME_API_KEY
- 4 documented capability areas: orders, charges, recipients, transfers
Community signal: 252 GitHub stars.
What problem does it solve?
Manually juggling Pagar.me REST docs while building checkout and payouts slows solo builders who want payments wired from the same chat where they ship code.
Who is it for?
Indie builders integrating Pagar.me into a Brazilian SaaS, marketplace, or API product who already have a Pagar.me account and API key.
Skip if: Teams that only need Stripe or global processors, or anyone without a Pagar.me merchant setup and secret key.
What do I get? / Deliverables
After you add the stdio server and API key, your agent can invoke Pagar.me operations as tools while you implement billing and marketplace payouts.
- Running stdio MCP bridge to Pagar.me APIs
- Agent-accessible workflows for orders, charges, recipients, and transfers
- Repeatable payment ops without leaving the coding agent session
Recommended MCP Servers
Journey fit
How it compares
Pagar.me payment MCP integration, not a checkout UI skill or generic payment abstraction layer.
Common Questions / FAQ
Who is io.github.codespar/mcp-pagar-me for?
Solo builders and small teams using Claude Code, Cursor, or Codex who need agent-driven access to Pagar.me for Brazilian orders, charges, recipients, and transfers.
When should I use io.github.codespar/mcp-pagar-me?
Use it during Build integrations when you are connecting real Pagar.me billing, charging customers, or paying recipients—not for market research alone.
How do I add io.github.codespar/mcp-pagar-me to my agent?
Install @codespar/mcp-pagar-me from npm, configure stdio transport in your MCP client, and set the required PAGARME_API_KEY environment variable before launching the server.