Quickstart
Install, set the credentials, make the first call.
Pick your client. The server runs locally over stdio, with your own credentials.
Tools
What your agent can call.
22 tools, as the package's tools/list returns them.
Names and descriptions come from the package's tools/list (@codespar/mcp-pagar-me@0.2.2). A kind (read, write, delete) is shown only when the package annotates its tools or each tool was verified one by one; neither exists for this server yet.
Compatibility
MCP is a protocol. Any client that speaks it can mount this server.
codespar_discover lists this server's tools, but a project with a test key cannot call them yet: the runtime has not recorded what this provider does in test mode, and refuses rather than guess.
Questions
Before you install.
How do I install the Pagar.me MCP server?
Run npx -y @codespar/mcp-pagar-me@0.2.2 and add the config block above to your MCP client: Claude Code, Cursor, Claude Desktop, VS Code, or any MCP-compatible client. No build step, no SDK required.
What can my agent do with Pagar.me?
Pagar.me exposes 22 tools for payments. Your agent calls them directly; the full list is above.
How does Pagar.me authenticate, and how are credentials stored?
Pagar.me uses API Key. Self-hosted, you hold the credentials: the server reads them from its environment variables.
How does Pagar.me handle upstream API changes?
Every server is versioned independently on npm. The command on this page pins 0.2.2, the version whose tools are listed here; your agent keeps running it until you change the version.
Is Pagar.me open source? How do I report a bug?
Yes. Pagar.me is MIT-licensed and published on npm as @codespar/mcp-pagar-me, source on GitHub (link in the Details panel). Report issues on the package repository; security issues go to security@codespar.dev, and we respond within 24 hours.