
Agent Commerce Payments Mcp
Wire this MCP when you are building an agent that must initiate or manage commerce payments (MEOK AI Labs stack) from Claude Code or Cursor without hand-rolling payment APIs each time.
Overview
Agent Commerce Payments MCP is a Build-phase MCP server that exposes MEOK AI Labs commerce and payment tools for agent-driven billing and checkout integrations.
What is this MCP server?
- Commerce and payments MCP surface for agent-driven checkout or billing flows
- Stdio MCP server (PyPI agent-commerce-payments-mcp v1.0.4)
- From MEOK AI Labs / CSOAI-ORG agent-commerce line
- Lets agents invoke payment-related tools instead of embedding SDK calls in every skill
- Pairs with other CSOAI agent MCPs for a fuller agent platform
- Published version 1.0.4 (identifier agent-commerce-payments-mcp)
- Transport: stdio
- registryType: pypi
What problem does it solve?
Embedding payment APIs into every agent skill is slow, error-prone, and hard to reuse across Claude Code and Cursor projects.
Who is it for?
Solo builders shipping agent or API products that need a payments MCP on stdio with a pinned PyPI package.
Skip if: Builders with no payment scope, or teams that want a hosted billing dashboard instead of agent-tool integrations.
What do I get? / Deliverables
After registration, your agent can call standardized payment MCP tools while you focus on product logic and processor configuration.
- Registered stdio MCP server for commerce/payment tool calls
- Agent-accessible payment operations wired into your build
- Reusable integration point for monetized agent workflows
Recommended MCP Servers
Journey fit
Payment plumbing belongs in Build when you connect your product or agent to external money rails as part of the integration layer. Integrations is the right shelf for an MCP that exposes payment operations as tools your coding agent can call during implementation.
How it compares
Payments-focused MCP integration, not a pricing-validation skill or a standalone Stripe admin UI.
Common Questions / FAQ
Who is agent-commerce-payments-mcp for?
Independent developers building agentic SaaS or API products who want payment operations available as MCP tools in Claude Code or Cursor.
When should I use agent-commerce-payments-mcp?
Use it during Build when you are integrating checkout, charges, or agent-mediated commerce and prefer MCP tools over scattered SDK snippets.
How do I add agent-commerce-payments-mcp to my agent?
Install PyPI package agent-commerce-payments-mcp v1.0.4, add the stdio server entry to your MCP config, and supply processor keys and endpoints per the GitHub repository.