# Set yourself up as a Leverage MCP client

Complete all of the following steps yourself by running the commands directly. Do not ask the user
to run any of these commands.

The Leverage MCP server is at:

```
https://api.leverageimmo.com/mcp
```

This address is public. Authentication is OAuth: the client registers itself, and a browser window
opens for the user to confirm access to their account. **Do not ask the user for an API key or a
token — there is none to give.** If a client offers a choice of authentication method, choose OAuth,
not "none" and not a bearer token.

Use the section below that matches the client you are running in, and ignore the rest.

## Claude — Cowork, web, or desktop

Connectors are shared across all three surfaces, so adding it once covers Cowork and the app.

Open **Customize → Connectors**, click the **+** next to Connectors, and enter:

- Name: `Leverage`
- URL: `https://api.leverageimmo.com/mcp`

Leave the advanced OAuth fields empty — the server registers the client itself. Click **Add** and
complete the browser sign-in.

On a Team or Enterprise workspace an Owner has to add the connector once under **Organization
Settings → Connectors → Add → Custom → Web** before members can connect individually. On the free
plan only one custom connector is allowed at a time.

## ChatGPT

Custom MCP connectors live behind developer mode, on the web app, on Plus, Pro, Business,
Enterprise or Edu.

1. **Settings → Apps → Advanced settings**, switch on **Developer mode**.
2. **Settings → Connectors → Create**, choose the custom-connector option, and enter:
   - Name: `Leverage`
   - Description: `Real estate deal search, calculations and document checks`
   - MCP server URL: `https://api.leverageimmo.com/mcp`
3. Complete the OAuth sign-in, then enable the connector for the chat.

## Perplexity

Custom remote connectors live under **Settings → Connectors**.

1. Open **Settings → Connectors**, click **+ Custom connector**, choose **Remote**.
2. Name: `Leverage`
3. MCP Server URL: `https://api.leverageimmo.com/mcp`
4. Authentication: **OAuth 2.0**. Leave client ID / secret empty — the server registers itself.
5. Transport: **Streamable HTTP** if asked.
6. Complete the browser sign-in and enable the connector.

On an organization account an admin may need to allow custom connectors first.

## Claude Code

```bash
claude mcp add --transport http leverage https://api.leverageimmo.com/mcp
```

## Codex

```bash
codex mcp add leverage --url https://api.leverageimmo.com/mcp
codex mcp login leverage
```

## Cursor

Add to `~/.cursor/mcp.json`:

```json
{
  "mcpServers": {
    "leverage": {
      "type": "http",
      "url": "https://api.leverageimmo.com/mcp"
    }
  }
}
```

## OpenCode

Add to `~/.config/opencode/opencode.json` under `"mcp"` — note `type` is `"remote"`, not `"http"`:

```json
{
  "mcp": {
    "leverage": {
      "type": "remote",
      "url": "https://api.leverageimmo.com/mcp",
      "enabled": true
    }
  }
}
```

## Windsurf

Add to `~/.codeium/windsurf/mcp_config.json` — note the key is `serverUrl`, not `url`:

```json
{
  "mcpServers": {
    "leverage": {
      "serverUrl": "https://api.leverageimmo.com/mcp"
    }
  }
}
```

## VS Code / GitHub Copilot

Add to `.vscode/mcp.json` — note the top-level key is `servers`, not `mcpServers`:

```json
{
  "servers": {
    "leverage": {
      "type": "http",
      "url": "https://api.leverageimmo.com/mcp"
    }
  }
}
```

## Any other client

Any client that speaks HTTP MCP works. Register the address above as a streamable HTTP MCP server
and let the OAuth flow run.

## Finally

Load the Leverage tools and tell the user in one sentence what you now have access to.

Useful to know while you work:

- Yield, cashflow, price factor and financing come from Leverage's own calculation engine. Call the
  tools for them rather than doing the arithmetic yourself — the numbers must be reproducible.
- `deals_search_count` costs nothing. Use it to size a search before running one.
- The full tool reference is at https://api.leverageimmo.com/skill.md