The server is currently reachable at the staging URL
https://veil-mcp-staging-193185291080.us-east4.run.app/mcp. A permanent custom domain is coming in a later phase.Claude Desktop
1
Open the connectors panel
In Claude Desktop, go to Settings → Integrations (or the MCP / connectors panel in your version). Click Add server or the + button.
2
Enter the server URL
Paste the MCP server URL:Give it a name like Veil and save.
3
Authorize
Claude Desktop prompts you for your email and a one-time code. Enter your email, wait for the code in your inbox, and verify. The connector becomes active.
4
Confirm the connection
Back in Claude Desktop, the Veil connector should appear as connected. Start a new conversation and ask something like “What’s my Veil account status?” — the assistant will call
veil_get_session_status and return your account details.Cursor
1
Open MCP settings
In Cursor, go to Settings → MCP (or open
.cursor/mcp.json directly in your project).2
Add the server entry
Add an entry pointing to the Veil MCP URL:Save the file. Cursor picks up the change without a restart.
3
Authorize
When you next use a Veil tool in a Cursor conversation, Cursor prompts you to authorize. Enter your email, wait for the one-time code, and verify.
4
Confirm the connection
In a Cursor chat, ask “Check my Veil status.” The assistant calls
veil_get_session_status and shows your login state.What happens during authorization
Connecting Veil takes one click — no manual client-ID setup. About once a week your client will prompt you to re-authorize; the prompt takes about 30 seconds.No credential, token, or banking detail is ever returned in a tool result. The MCP server only exposes safe summaries — masked account suffixes, display names, and status strings.
First-run quirks
- Sandbox mode is the default. Switch to live mode with
veil_set_modeonce you are ready for real transactions.
See also
- In-chat flow — walkthrough of a complete offramp conversation
- Tool reference — every Veil MCP tool with inputs and outputs