Skip to main content
Unify MCP is in early access and under active development. Available tools and behavior may change before general availability.
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 (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:
“Research acme.com and tell me if they look like a good fit for our ICP.”
“Find VP of Sales at Series B SaaS companies in the Bay Area, then create a 4-step sequence and enroll them.”
“Build me a list of Series B fintech companies in the US with 50-200 employees.”
“Update these accounts in Salesforce with our latest ICP tier.”
“Which of my active sequences have the highest reply rate this month?”
“How many touches has each rep logged this week, and who’s below pace?”
“Every Monday at 9am, find companies that raised funding in the last week and send me the list.”
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, which bundles the Unify skills and MCP configuration.
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
    You must also enter this OAuth Client ID. The connector will fail to connect without it:
  3. Save. Unify now shows up as an available connector for everyone in the workspace.
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.
Once that’s done, each person connects individually:
  1. Go to Settings → Connectors and search for Unify.
  2. Click Connect, then log in with your Unify account when prompted.
  3. Go to Settings → Plugins and click Add marketplace.
  4. Enter: https://github.com/unifygtm/agent-plugins
  5. Click Sync.
  6. Click Install.
You’re now connected, with Unify’s skills and MCP tools available.

​
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:
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

Yes. Unify MCP runs the exact same Agent. Nothing is different except how you’re talking to it.
No. It uses your existing Unify Chat credits/usage.
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.
Yes. Ask your assistant to set up a recurring prompt (a “scheduled chat”), and it’ll run automatically on the schedule you give it.
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.

​
Next steps

Tools reference

The complete, technical tool-by-tool reference.