> ## Documentation Index
> Fetch the complete documentation index at: https://docs.useveil.co/llms.txt
> Use this file to discover all available pages before exploring further.

# Connect

> Add the Veil MCP server to Claude Desktop or Cursor and complete the OAuth handshake.

Adding Veil to an MCP client takes about two minutes. The steps below cover Claude Desktop and Cursor. Other MCP-compatible clients follow the same pattern.

<Note>
  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.
</Note>

## Claude Desktop

<Steps>
  <Step title="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.
  </Step>

  <Step title="Enter the server URL">
    Paste the MCP server URL:

    ```
    https://veil-mcp-staging-193185291080.us-east4.run.app/mcp
    ```

    Give it a name like **Veil** and save.
  </Step>

  <Step title="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.
  </Step>

  <Step title="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.
  </Step>
</Steps>

## Cursor

<Steps>
  <Step title="Open MCP settings">
    In Cursor, go to **Settings → MCP** (or open `.cursor/mcp.json` directly in your project).
  </Step>

  <Step title="Add the server entry">
    Add an entry pointing to the Veil MCP URL:

    ```json theme={null}
    {
      "veil": {
        "url": "https://veil-mcp-staging-193185291080.us-east4.run.app/mcp"
      }
    }
    ```

    Save the file. Cursor picks up the change without a restart.
  </Step>

  <Step title="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.
  </Step>

  <Step title="Confirm the connection">
    In a Cursor chat, ask "Check my Veil status." The assistant calls `veil_get_session_status` and shows your login state.
  </Step>
</Steps>

## 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.

<Note>
  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.
</Note>

## First-run quirks

* Sandbox mode is the default. Switch to live mode with `veil_set_mode` once you are ready for real transactions.

## See also

* [In-chat flow](/mcp/in-chat-flow) — walkthrough of a complete offramp conversation
* [Tool reference](/mcp/tools) — every Veil MCP tool with inputs and outputs