MCP Server for Clawallex payment API - Pay for anything with USDC virtual cards
Clawallex MCP server exists for a simple reason — assistants are far more useful when they can act on Clawallex directly instead of describing what you should do. MCP Server for Clawallex payment API - Pay for anything with USDC virtual cards.
MCP Server for the Clawallex payment API. Pay for anything with USDC — Clawallex converts your stablecoin balance into virtual cards that work at any online checkout.
Once Clawallex is connected, these are the calls the assistant has available:
OpenCode — The OpenCode tool exposed by this serverAuthentication — The Authentication tool exposed by this server@clawallex/mcp-server on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
You will need 4 environment variables: CLAWALLEX_API_KEY, CLAWALLEX_API_SECRET, CLAWALLEX_BASE_URL, CLAWALLEX_CLIENT_ID. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Plenty of payments and commerce servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Clawallex's toolset — OpenCode, Authentication — is a fair guide to whether it matches your workflow. It is maintained by Clawallex-Tech; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| OpenCode | The OpenCode tool exposed by this server. |
| Authentication | The Authentication tool exposed by this server. |
{
"mcpServers": {
"clawallex": {
"command": "npx",
"args": ["-y", "@clawallex/mcp-server"],
"env": {
"CLAWALLEX_API_KEY": "your-value",
"CLAWALLEX_API_SECRET": "your-value",
"CLAWALLEX_BASE_URL": "your-value",
"CLAWALLEX_CLIENT_ID": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| CLAWALLEX_API_KEY | Credential the server authenticates with. | Yes |
| CLAWALLEX_API_SECRET | Credential the server authenticates with. | Yes |
| CLAWALLEX_BASE_URL | Endpoint or connection string the server talks to. | Yes |
| CLAWALLEX_CLIENT_ID | Configuration value read at startup. | Optional |
Payments infrastructure meets AI — customers, invoices, subscriptions and current API docs from Stripe's server.
Build for Shopify with current APIs — the official Dev MCP server for schema-accurate storefront and admin code.
Give your AI assistant a supervised window into your Interactive Brokers account — balances, positions, live quotes and orders.
Invoices, payments and disputes through PayPal's official server — commerce operations by conversation.
Enables querying and listing Azure resources and costs directly from an MCP client.
Empowers LLMs with Bitcoin Lightning Network payment capabilities via the ZBD API.