Clawallex Mcp
Enable agents to issue and spend via Clawallex USDC-backed virtual cards through HMAC-signed API calls over MCP.
Overview
Clawallex MCP is an MCP server for the Build phase that lets agents interact with Clawallex USDC virtual card payments via a signed API.
What is this MCP server?
- npm stdio server @clawallex/mcp-server (v1.0.9) for Clawallex payment API
- USDC virtual cards—pay for goods and services without exposing primary card numbers in prompts
- Required CLAWALLEX_API_KEY and CLAWALLEX_API_SECRET for HMAC-SHA256 request signing
- Designed for agent-initiated procurement, subscriptions, or automated billing experiments
- Open-source repo at github.com/clawallex/clawallex-mcp
- MCP server version 1.0.9
- npm package @clawallex/mcp-server
- Two required secret env vars: API key and API secret for HMAC-SHA256
What problem does it solve?
Letting an agent pay for services safely means wrestling with HMAC signing, card APIs, and tool schemas instead of shipping your core product.
Who is it for?
Indie hackers automating small-dollar agent spend, virtual card demos, or USDC-treasury experiments tied to MCP workflows.
Skip if: Teams that cannot hold crypto-backed balances, need traditional merchant onboarding only, or want payments without agent access to secrets.
What do I get? / Deliverables
After configuring API key and secret, your agent can invoke Clawallex payment tools through MCP without you rewriting the signing layer each sprint.
- MCP-accessible Clawallex payment and virtual card operations
- HMAC-SHA256 signed requests handled by the server package
- Agent workflows that can pay for external services with scoped cards
Recommended MCP Servers
Journey fit
Payment rails are integrated during Build when your agent or backend needs programmatic spend, not during passive idea research. Clawallex MCP is a signed payment API adapter—classic agent-tooling integration with secrets in environment variables.
How it compares
Fintech payment MCP connector, not a budgeting skill or standalone neobank app.
Common Questions / FAQ
Who is Clawallex MCP for?
Clawallex MCP is for developers building agent-driven checkout or spend flows who want USDC virtual cards exposed as MCP tools with HMAC-signed API access.
When should I use Clawallex MCP?
Use it during Build when your agent must pay third parties programmatically and you already use Clawallex for USDC virtual card issuance and charges.
How do I add Clawallex MCP to my agent?
Install @clawallex/mcp-server, add the stdio MCP server in your client, and set required environment variables CLAWALLEX_API_KEY and CLAWALLEX_API_SECRET.