Prerequisites
- A Machines account with identity verification complete
- An AI app that supports remote MCP servers (Claude, ChatGPT, Copilot, Clawdbot, etc.)
Connect with OAuth
Add a remote MCP server
Open your AI app’s settings and add a new remote MCP server (sometimes called a connector or integration).
Connect with API key
Use this if your app does not support OAuth and asks for manual credentials instead.Add the key to your AI app
Paste your API key where your app asks for a token, API key, or credential.
Transport type
Use remote Streamable HTTP as the connection type with the URL above. Do not use localhost or stdio — this is a hosted server.Example prompts
Once connected, try these:- “list my cards”
- “show my balances”
- “start a USDC deposit on Base”
- “check my active deposits”
- “reveal full details for my newest card”
- “search apple airpods pro on amazon”
- “buy these apple airpods pro on amazon using my default card”
- “check the status of my latest purchase”
Troubleshooting
| Problem | Fix |
|---|---|
| Connection fails | Verify you’re using exactly https://mcp.machines.cash/mcp |
| ”Missing bearer token” error | Reconnect with OAuth, or add your API key manually |
| Labels look raw or unfriendly | Ask for machines.user.cards.list or set presentation: "end_user" |
| Card numbers refused by host | Ask the AI to use reveal_card_details instead |
| Still not working | Remove the Machines MCP connection and add it again |
Keep your account safe
- Only approve access on trusted Machines pages (
machines.cashdomain) - Reveal full card details only when you explicitly need them
- Do not paste keys into shared documents or public channels
Next steps
- Machines CLI — terminal commands for login, cards, and deposits
- Agentic Payments — one shared search, buy, status, confirm, and 3DS flow
- Raw Knowledge File — paste context into your AI for better responses