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

# Getting started with Unify MCP

> Connect Unify to Claude, Cursor, or any MCP-compatible AI assistant.

<Note>
  Unify MCP is in early access and under active development. Available
  tools and behavior may change before general availability.
</Note>

Unify MCP lets you connect Unify to Claude, Cursor, or any other
MCP-compatible AI assistant. Once connected, your assistant can research
companies, build lists, write sequences, update your CRM, and more, all
from a normal conversation, using the same Agent that powers Unify Chat.

## What is MCP?

[MCP](https://modelcontextprotocol.io) (Model Context Protocol) is an open
standard that lets AI assistants like Claude or Cursor securely connect to
outside tools and data. Instead of copying information back and forth
between Unify and your AI assistant, you connect once. From there, your
assistant can call Unify directly, on your behalf, whenever it's useful.

## What you can do with Unify MCP

Because Unify MCP runs the exact same Agent as Unify Chat, anything you can
ask Unify Chat to do, you can ask your connected assistant to do too:

<AccordionGroup>
  <Accordion title="Research">
    "Research acme.com and tell me if they look like a good fit for our ICP."
  </Accordion>

  <Accordion title="Prospecting and creating sequences">
    "Find VP of Sales at Series B SaaS companies in the Bay Area, then
    create a 4-step sequence and enroll them."
  </Accordion>

  <Accordion title="List building">
    "Build me a list of Series B fintech companies in the US with 50-200
    employees."
  </Accordion>

  <Accordion title="CRM updates">
    "Update these accounts in Salesforce with our latest ICP tier."
  </Accordion>

  <Accordion title="Sequence performance">
    "Which of my active sequences have the highest reply rate this month?"
  </Accordion>

  <Accordion title="Rep activity and performance">
    "How many touches has each rep logged this week, and who's below
    pace?"
  </Accordion>

  <Accordion title="Recurring / scheduled work">
    "Every Monday at 9am, find companies that raised funding in the last
    week and send me the list."
  </Accordion>
</AccordionGroup>

Your assistant can also pull in supporting context as needed, like a
results table from a previous run, your outbound email voice profile, or
your company's business context, to make its answers more accurate.

If you have other MCP connectors set up too, like a call recording tool,
your assistant can combine that context with Unify in the same
conversation. For example, it can pull insights from a recent discovery
call and use them to help draft a more personalized sequence in Unify.

## Getting started

Pick your client below. Claude (Desktop / claude.ai) is the most common
starting point. For Claude Code, Cursor, and Codex, the recommended path is
installing [Unify's official plugin](https://github.com/unifygtm/agent-plugins),
which bundles the Unify skills and MCP configuration.

<Tabs>
  <Tab title="Claude (Desktop / claude.ai)">
    If your company is on a Claude **Team or Enterprise** plan, an admin
    usually needs to add Unify as a connector for the workspace first, since
    most people can't add a custom connector themselves on those plans.

    1. As a Claude workspace **admin**, go to **Settings → Connectors** (or
       **Integrations**, depending on your plan) and click **Add custom
       connector**.
    2. Enter:

       * **Name:** `Unify`
       * **Remote MCP server URL:** `https://mcp.unifygtm.com/mcp`

           <Warning>
             You must also enter this **OAuth Client ID**. The connector will
             fail to connect without it:

             ```
             WlCPDTjIzXkpsvxi5TwnkBQECGTL3dGE
             ```
           </Warning>
    3. Save. Unify now shows up as an available connector for everyone in
       the workspace, though each person still clicks **Connect** and logs
       in with their own Unify account individually.

    <Info>
      This Client ID identifies the Claude Desktop app to Unify. It's the
      same value for every organization and isn't specific to your
      company. Each person still logs in with their own Unify account, and
      only ever sees their own company's data.
    </Info>
  </Tab>

  <Tab title="Claude Code">
    Add the Unify plugin marketplace, then install the plugin at user scope:

    ```bash theme={null}
    claude plugin marketplace add unifygtm/agent-plugins --scope user
    claude plugin install unify@unify-plugins --scope user
    ```

    Fully restart Claude Code, then run `/mcp` and complete the Unify login
    when prompted.
  </Tab>

  <Tab title="Cursor">
    Cursor does not currently provide CLI commands for adding a marketplace
    and installing a plugin. If your organization uses team marketplaces:

    1. Ask a Cursor administrator to add `unifygtm/agent-plugins` as a team
       marketplace.
    2. Open **Settings → Plugins**, find **Unify**, and install it.
    3. Fully restart Cursor, then enable and sign in to Unify from **Settings
       → Plugins**.

    For an individual local installation, run the official setup script:

    ```bash theme={null}
    curl -fsSL https://raw.githubusercontent.com/unifygtm/agent-plugins/main/scripts/setup.sh | bash -s -- cursor
    ```

    If Unify does not appear after restarting, ask a Cursor administrator to
    allow user-local plugin imports.
  </Tab>

  <Tab title="Codex">
    Add the Unify plugin marketplace, then install the plugin:

    ```bash theme={null}
    codex plugin marketplace add unifygtm/agent-plugins
    codex plugin add unify@unify-plugins
    ```

    Fully restart Codex, then sign in to Unify:

    ```bash theme={null}
    codex mcp login unify
    ```
  </Tab>

  <Tab title="ChatGPT">
    <Note>
      Support for ChatGPT is still being finalized. Check with your Unify
      contact for current setup steps.
    </Note>
  </Tab>
</Tabs>

### Custom or other clients

If your client isn't listed above, or you'd rather authenticate with an API
key instead of logging in, connect manually with this configuration:

```json theme={null}
{
  "mcpServers": {
    "unify": {
      "url": "https://mcp.unifygtm.com/mcp",
      "headers": {
        "x-api-key": "<your-api-key>"
      }
    }
  }
}
```

Generate an API key from **Settings → Developers** in the Unify app. Every
action taken this way is scoped to whichever Unify user the key belongs to.

## Usage and credits

Unify MCP runs on the same Agent, and consumes the same usage/credits, as
messages sent directly in Unify Chat. There's no separate cost for
connecting through MCP.

## Best practices

**Use Unify's own terms when you prompt.** Your assistant understands
requests best when you use the same words Unify does, like "sequence,"
"enrich," "prospect," "play," and "audience," instead of a generic word
like "campaign" or "segment." That makes it far more likely your assistant
maps what you're asking for to the right Unify action.

It also helps to say so explicitly when you want something run as a
background Agent task you can check on later:

> "Start an Agent run to prospect a new list, and give me a link to check
> on it."

## FAQ

<AccordionGroup>
  <Accordion title="Is this the same AI as Unify Chat?">
    Yes. Unify MCP runs the exact same Agent. Nothing is different except
    how you're talking to it.
  </Accordion>

  <Accordion title="Does this cost extra?">
    No. It uses your existing Unify Chat credits/usage.
  </Accordion>

  <Accordion title="Is my data isolated from other users?">
    Yes. Every request is tied to the specific Unify user who connected, so
    your assistant only ever sees what that user can see in Unify.
  </Accordion>

  <Accordion title="Can I schedule recurring tasks?">
    Yes. Ask your assistant to set up a recurring prompt (a "scheduled
    chat"), and it'll run automatically on the schedule you give it.
  </Accordion>

  <Accordion title="Which AI clients are supported?">
    The official Unify plugin supports Claude Code, Cursor, and Codex. Claude
    Desktop/claude.ai and ChatGPT can connect without the plugin. Any other
    MCP-compatible client that supports remote/HTTP servers can use the custom
    configuration above.
  </Accordion>
</AccordionGroup>

## Next steps

<CardGroup cols={1}>
  <Card title="Tools reference" href="/developers/mcp/tools" icon="wrench" horizontal>
    The complete, technical tool-by-tool reference.
  </Card>
</CardGroup>