# Install the acquiresure MCP server

You are an AI agent. Your user wants you to connect the **acquiresure** MCP server so you can search for leads, find and verify work emails, list the people at a company, look up who is behind an email, resolve IPs to companies, and send emails and follow-up campaigns from your user's own connected inbox. Follow this guide end to end.

## What you need

- **Server URL:** `https://api.acquiresure.cloud/mcp` (Streamable HTTP, POST only)
- **Auth:** either the header `x-api-key: <API_KEY>`, or OAuth sign-in. Apps that support MCP OAuth (claude.ai, ChatGPT, Claude Code) can connect with just the URL: the user signs in and approves, no key needed.
- **API key** (for config-file clients): starts with `as_live_`. Use the key your user gave you. If they didn't give one, ask them for it. They can create one at https://app.acquiresure.cloud/app/keys. Never invent a key.

In every snippet below, replace `API_KEY` with the real key. Server name is always `acquiresure`.

## Steps

1. Work out which client you are running in (list below). If unsure, ask your user.
2. Apply the matching config. If the config file already exists, **merge** the `acquiresure` entry into it. Never delete other servers or settings.
3. If an `acquiresure` entry already exists, replace it with the new one.
4. Tell your user to restart or reload the client if it needs it (noted below).
5. Verify (see the end of this guide).

---

### Claude Code

Run:

```bash
claude mcp add --scope user --transport http acquiresure https://api.acquiresure.cloud/mcp --header "x-api-key: API_KEY"
```

If it says the server already exists, run `claude mcp remove --scope user acquiresure` first. Available in new sessions; `/mcp` shows its status.

### Codex (CLI and IDE extension)

Add to `~/.codex/config.toml` (remove any existing `[mcp_servers.acquiresure]` table first):

```toml
[mcp_servers.acquiresure]
url = "https://api.acquiresure.cloud/mcp"
http_headers = { "x-api-key" = "API_KEY" }
```

Restart Codex.

### Cursor

Merge into `~/.cursor/mcp.json` (global) or `.cursor/mcp.json` (this project only):

```json
{
  "mcpServers": {
    "acquiresure": {
      "url": "https://api.acquiresure.cloud/mcp",
      "headers": { "x-api-key": "API_KEY" }
    }
  }
}
```

Cursor picks it up automatically; check Settings → MCP.

### VS Code (GitHub Copilot agent mode)

Merge into `.vscode/mcp.json` in the workspace (or the user-level `mcp.json` via "MCP: Open User Configuration"). Note the top-level key is `servers`:

```json
{
  "servers": {
    "acquiresure": {
      "type": "http",
      "url": "https://api.acquiresure.cloud/mcp",
      "headers": { "x-api-key": "API_KEY" }
    }
  }
}
```

### Windsurf

Merge into `~/.codeium/windsurf/mcp_config.json`. Windsurf uses `serverUrl`:

```json
{
  "mcpServers": {
    "acquiresure": {
      "serverUrl": "https://api.acquiresure.cloud/mcp",
      "headers": { "x-api-key": "API_KEY" }
    }
  }
}
```

Press refresh in the MCP panel.

### Gemini CLI

Merge into `~/.gemini/settings.json`. Gemini uses `httpUrl`:

```json
{
  "mcpServers": {
    "acquiresure": {
      "httpUrl": "https://api.acquiresure.cloud/mcp",
      "headers": { "x-api-key": "API_KEY" }
    }
  }
}
```

Restart Gemini CLI; `/mcp` lists it.

### Claude Desktop

Claude Desktop's JSON config only runs local (stdio) servers, so bridge with `mcp-remote` (needs Node.js). Merge into:

- macOS: `~/Library/Application Support/Claude/claude_desktop_config.json`
- Windows: `%APPDATA%\Claude\claude_desktop_config.json`

```json
{
  "mcpServers": {
    "acquiresure": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://api.acquiresure.cloud/mcp", "--header", "x-api-key:API_KEY"]
    }
  }
}
```

Fully quit and reopen Claude Desktop.

### Claude on the web (claude.ai), desktop and mobile

Claude's website can't run commands or edit files, so your user adds acquiresure themselves. No API key is needed. Tell them:

1. Open **Settings → Connectors** on claude.ai and click **Add custom connector**.
2. Name: `acquiresure`. Remote MCP server URL: `https://api.acquiresure.cloud/mcp`. Leave **Advanced settings** (OAuth Client ID and OAuth Client Secret) empty: acquiresure registers Claude automatically. Click **Add**.
3. Click **Connect** next to acquiresure. An acquiresure page opens: sign in (we email a link; it can be opened on any device), then click **Allow**.
4. In a chat, open the **+** menu and switch acquiresure on. The connector also works in the Claude desktop and mobile apps.

On Team and Enterprise plans, an owner adds the connector once under Organization settings → Connectors.

### ChatGPT (chatgpt.com)

Your user adds it themselves, on a paid ChatGPT plan. Tell them:

1. Open **Settings → Apps & Connectors → Advanced settings** and turn on **Developer mode**.
2. Back in **Apps & Connectors**, click **Create**. Name: `acquiresure`. MCP Server URL: `https://api.acquiresure.cloud/mcp`. Authentication: **OAuth**, with the client ID and secret left empty (acquiresure registers ChatGPT automatically). Tick that they trust the app, then **Create**.
3. An acquiresure page opens: sign in, then click **Allow**.
4. In a chat, open **+ → Developer mode** and switch acquiresure on.

Either app can be disconnected any time from the acquiresure dashboard (Overview → Connected apps).

### Hermes Agent

Merge into `~/.hermes/config.yaml`:

```yaml
mcp_servers:
  acquiresure:
    url: "https://api.acquiresure.cloud/mcp"
    headers:
      x-api-key: "API_KEY"
```

Run `/reload-mcp` (or restart Hermes).

### Any other MCP client

Add a remote server using Streamable HTTP with URL `https://api.acquiresure.cloud/mcp` and header `x-api-key: API_KEY`. If the client only supports stdio, use `npx -y mcp-remote https://api.acquiresure.cloud/mcp --header x-api-key:API_KEY` as the command.

---

## Tools you get

**Prospecting and lookups** (credits; lookups with no result are never charged)

| Tool | What it does | Cost |
| --- | --- | --- |
| `count_leads`, `lead_filter_options`, `suggest_companies` | Size a search, list accepted filter values, autocomplete companies | Free |
| `preview_leads` | Match count plus the first 10 leads (no emails) | 0.1 per lead shown |
| `search_leads` | Search people by title, seniority, skills, location, company, funding and 100+ filters | 0.1 per lead |
| `reveal_emails` | Work emails for up to 25 leads from a search | 1 per email found |
| `find_email` | Work email from first name, last name and company domain | 1 (free if not found) |
| `find_people_at_company` | People at a company, with verified emails | 0.1 per person + 1 per email |
| `validate_email`, `validate_emails_batch`, `get_batch_results` | Verify one address, or up to 100 in the background | 0.1 each (risky refunded) |
| `lookup_person` | Professional profile behind an email | 1 (free if none) |
| `company_tech` | A company's tech stack | 0.5 (free if nothing found) |
| `ip_to_company` | The company behind an IP | 10 (free if none) |
| `save_search`, `list_saved_searches`, `delete_saved_search` | Watch a search; your user is emailed when new people match | Free |
| `list_website_visitors` | Companies that visited your user's site (needs the acquiresure tag) | 10 per company found |
| `get_upgrade_link` | A checkout link for your user when credits run low | Free |

**Sending** (from your user's own connected inboxes; included in paid plans)

| Tool | What it does |
| --- | --- |
| `list_inboxes` | Connected inboxes. Your user connects them in the dashboard under Email; several inboxes add up their daily caps |
| `send_email` | One email now or at a set time |
| `create_campaign`, `add_campaign_recipients` | Email a list with up to 9 follow-ups that stop on reply |
| `list_campaigns`, `get_campaign`, `update_campaign` | Progress, pause, resume, stop or edit |
| `list_emails`, `cancel_email`, `email_stats` | Sent and scheduled emails, cancel one, reply, bounce and booking rates |
| `contact_history`, `add_to_do_not_contact` | Who was already emailed; never email certain people or domains |

Always show your user the drafted emails and recipients and get their OK before calling `send_email` or `create_campaign`.

## Verify

After the client reloads (or after the user clicks Allow), confirm the tools above appear in your tool list. Then tell your user: "acquiresure is connected. Try asking me to find 10 heads of growth in Austin."

If a call returns `401`, the key is wrong or was rotated (ask your user for a current key), or the app was disconnected (connect it again). `402` means the account is out of credits or sending needs a plan; your user can upgrade at https://app.acquiresure.cloud/app/billing.

## Keep the key private

Only write the key into the client's config. Don't echo it back in full, commit it to git, or put it in a shared project file your user didn't ask for.