Agent Payment Mcp
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.
Overview
Agent Payment MCP is a MCP server for the Build phase that securely routes agent tool calls to AgentPMT’s pay-per-use AI tools marketplace with API-key auth and budget keys.
What is this MCP server?
- 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
- Server version 1.1.0
- 2 required secret environment variables (x-api-key, x-budget-key)
- stdio transport with binary runtimeHint (mcpb registry)
What problem does it solve?
Agents that call paid external AI tools without a single router leave you juggling API keys, surprise charges, and no unified spending guardrails.
Who is it for?
Indie builders running Claude Code or Cursor who want metered third-party AI tools inside agent workflows with explicit budget keys.
Skip if: Teams that only use free local tools, self-host everything without AgentPMT, or need water-engineering or database-native MCP—not a payment router.
What do I get? / Deliverables
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
Recommended MCP Servers
Journey fit
Pay-per-use tool access is wired into the agent stack during integration work, before you rely on external capabilities in production workflows. This MCP server is a transport router to a marketplace—classic build-phase external service hookup, not launch or ops monitoring.
How it compares
MCP payment router to a tool marketplace, not an agent skill or local CLI generator.
Common Questions / FAQ
Who is agent-payment-mcp for?
Solo and small-team builders 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.