Payments for AI agents: gasless USDC on Base + JIT single-use virtual cards, PAN never in context.
Payments for AI agents: gasless USDC on Base + JIT single-use virtual cards, PAN never in context. The z mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 1 defined tool rather than through you.
Z-ZERO fixes that. One MCP server gives your agent (Claude, Cursor, any MCP-compatible client) two payment rails — gasless USDC on Base for crypto-native checkouts, and JIT single-use virtual cards for the 99% of the web that only takes cards — while the model never sees a real card number.
Everything the assistant can do here goes through one of these:
Double — check you copied the full key (e.g. zk_live_c0g3l)You will need one environment variable: Z_ZERO_API_KEY. 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.
zk_live_, get it from the dashboard above ---Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.
Among the payments and commerce options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Z's toolset — Double — is a fair guide to whether it matches your workflow. It is maintained by Dempty-glitch; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Z's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| Double | check you copied the full key (e.g. zk_live_c0g3l) |
{
"mcpServers": {
"z-zero": {
"command": "npx",
"args": ["-y", "z-zero-mcp-server"],
"env": {
"Z_ZERO_API_KEY": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
zk_live_, get it from the dashboard above ---| Variable | Description | Required |
|---|---|---|
| Z_ZERO_API_KEY | Credential the server authenticates with. | Yes |
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.