
Agent Payment MCP
- Apoth3osis-ai/agent-payment-mcp
Agent Payment MCP is a MCP server that securely routes agent tool calls to AgentPMT’s pay-per-use AI tools marketplace with API-key auth and budget keys.
About
Agent Payment MCP is a secure stdio router that connects Claude Code, Cursor, and similar agents to AgentPMT’s pay-per-use AI tools marketplace. developers use it when they want agents to call commercial or metered tools without hand-rolling payment flows or losing track of spend. You register the server in your MCP config, set x-api-key for authentication and x-budget-key for budget enforcement, and point agents at marketplace capabilities through one consistent protocol surface. It ships as release binaries (Linux/macOS amd64) rather than a loose script, which suits teams that want reproducible installs. It is an integration layer, not a skill that teaches workflow—pair it with your own prompts or skills that define which marketplace tools to invoke and when.
- stdio MCP router to AgentPMT’s pay-per-use AI tools marketplace (v1.1.0)
- Required secrets: x-api-key and x-budget-key for auth plus spending control
- Linux and macOS amd64 binary packages with pinned fileSha256 releases
- Budget key lets you cap agent spend before marketplace tools execute
Agent Payment MCP by the numbers
- Data as of Aug 10, 2026 (Skillselion catalog sync)
Add your badge
Show developers this MCP server is listed on Skillselion. Paste this into your README.
| Repository | Apoth3osis-ai/agent-payment-mcp ↗ |
|---|
What it does
Route your coding agent through AgentPMT so paid third-party AI tools run with API-key auth and budget caps instead of one-off billing chaos.
Who is it for?
Best when you're running Claude Code or Cursor and want metered third-party AI tools inside agent workflows with explicit budget keys.
Skip if: Skip if you only use free local tools, self-host everything without AgentPMT, or need water-engineering or database-native MCP—not a payment router.
What you get
After registration, your agent reaches marketplace tools through one MCP surface with authentication and budget-key spending control configured up front.
- stdio MCP connection to AgentPMT marketplace tools
- Authenticated agent calls with budget-enforced spend
By the numbers
- Server version 1.1.0
- 2 required secret environment variables (x-api-key, x-budget-key)
- stdio transport with binary runtimeHint (mcpb registry)
Recommended MCP Servers
How it compares
MCP payment router to a tool marketplace, not an agent skill or local CLI generator.
FAQ
Who is agent-payment-mcp for?
and small-team developers who use MCP-enabled agents and want pay-per-use AI marketplace tools with API keys and budget limits.
When should I use agent-payment-mcp?
When you are integrating external paid AI capabilities into your agent and need AgentPMT auth plus x-budget-key spending control before those tools run.
How do I add agent-payment-mcp to my agent?
Add the stdio MCP entry pointing at the release binary for your OS, set x-api-key and x-budget-key in the server environment, then restart Claude Code or Cursor.