MCP overview

The Veil MCP server connects to Claude Desktop and Cursor through the Model Context Protocol. Once connected, you can log in, complete onboarding, run offramps, and check transaction status — all from inside a conversation. The same Veil account, KYC approval, and bank accounts you set up in the dashboard work here.

​

Who this is for

Anyone who has a Veil account and wants to trigger crypto-to-fiat conversions from inside an AI assistant. Developers and individuals both work; the onboarding steps are the same either way.

​

The five-step flow at a glance

Every offramp via MCP follows this sequence:

1. Check session — veil_get_session_status tells the assistant whether you are already logged in.
2. Log in — veil_request_otp + veil_verify_otp authenticate you with an email code.
3. Check onboarding — veil_get_account_status shows whether KYC and a bank account are in place.
4. Get a quote — veil_offramp_quote returns the exchange rate and estimated fiat amount.
5. Execute (and confirm if needed) — veil_offramp_execute creates the transaction; when a code is required it’s emailed and veil_offramp_confirm releases the funds, otherwise the offramp settles immediately.

For the full conversation walkthrough, see In-chat flow.

​

Sandbox vs. production

The MCP server supports both sandbox (test) and live (real money) modes. Sandbox offramps run against a test environment — no real funds move and settlement is instant. See Environments for how to switch modes in chat, or Sandbox vs. production for the full two-environment model.

​

Get started

​

See also

• Usernames — handle-routed offramps via @handle