Unify
by Unify
Run outbound from a chat: prospect, enrich, enrol people into email sequences and write back to your CRM. Fifty tools in Anthropic's listing, seventy-one in Unify's own reference, OAuth sign-in, and one tool that puts real email in front of real people.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Connect Unify via MCP
https://mcp.unifygtm.com/mcpWorks in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.
Use in Agentman
Connect Unify once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.
Open in Agentman StudioUnify Tools & Capabilities (50)
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
Limits
- Enrolment is unrecallable.
create_sequence_enrollmentresults in real email to a real person. Unify's guards — opt-out and Do Not Email blocks, exclusions, one active Sequence per person, re-enrolment waiting periods — are workspace configuration, not properties of the tool. An agent inherits whatever is configured. - No OAuth scopes separate reads from writes. The server's own RFC 9728 descriptor publishes no
scopes_supportedfield at all (verified live, 2026-09-08). Authorisation is therefore all-or-nothing at the protocol layer, and the only boundary is the connected user's Unify permissions. - Seven delete tools, no documented undo.
delete_object,delete_object_attribute,delete_object_attribute_option,delete_object_record,delete_sequence,delete_sequence_enrollmentanddelete_task. Unify's API reference describes none of them as soft or reversible. - No safety annotations were readable. The OAuth gate meant we could not run
tools/list, so noreadOnlyHintordestructiveHintvalues are known. Read/write labels on this page are documentation-derived. - Twenty-one documented tools are absent from the listing. Unify documents 71; Anthropic lists 50. Do not assume the query-job family is callable until you see it in your own client's tool list.
- Credits gate the agent, and enrichment is the expensive part. Unify prices phone-number enrichment at 4 to 15 credits per person and new-hire tracking at 15 per hire. A broad prospecting request is a billable one.
- Sending is rate-limited by design. Unify recommends 25 emails per mailbox per day, sends only on business days between 9 AM and 4 PM Pacific by default, and warms new mailboxes before normal sending. Bulk enrolment produces a queue, not a burst.
- Role-based and invalid addresses are excluded by default. Unify documents
info@-style role-based addresses as not eligible for sending by default, and addresses verified invalid as ineligible and not enablable. - Data provenance is asserted, not itemised. Unify says it requires data providers to certify lawful collection and consent, and that it may be deemed a data broker in certain states. It does not publish which of its 40+ providers supplied a given contact. Compliance with GDPR, CAN-SPAM or state privacy law remains the sender's responsibility; nothing on this page is legal advice.
- One agent run at a time per question.
answer_questionrequires answers matching the pending questions exactly aspoll_agentreturned them, andread_agent_resultserrors on a run that has not reached a terminal status.
Frequently asked questions
No. Unify states that its MCP server runs the same Agent as Unify Chat and consumes the same usage and credits, with no separate cost for connecting through MCP. Credits are still spent by the work itself: Unify's credit table prices person enrichment at 1 to 6 credits for a B2B email and 4 to 15 for a phone number, and Unify Chat at roughly 0.1 credits per query.
It can enrol a person into a Sequence, and Unify sends the email from there. The `create_sequence_enrollment` tool starts an enrolment; Unify's Sequence documentation then governs delivery, and its default posture is deliberately slow. Sends run business days between 9 AM and 4 PM Pacific, staggered roughly two to six minutes apart, with a recommended default of 25 emails per mailbox per day.
Yes. Unify states that every request is tied to the specific user who connected, so a connected assistant only sees what that user can already see in Unify. The tool reference repeats the rule per tool: `load_datatable` reaches only DataTables the authenticated user owns, and cannot load another user's tables even inside the same tenant. Permissions come from Unify, not from the client.
Yes, and Unify blocks it by default rather than leaving it to the caller. Its enrolment documentation lists opt-out and a Do Not Email status as conditions that prohibit new enrolments outright. Exclusion rules, one active Sequence per person, and configurable re-enrolment waiting periods are separate gates, and each surfaces as an enrolment failure rather than a silent send.
Claude Desktop and claude.ai connect directly through the connector directory, and Unify documents ChatGPT Desktop as reachable through the Codex path. Claude Code, Cursor and Codex use Unify's official plugin marketplace instead of a raw endpoint. Unify's own guidance for any client not on that list is to contact your Unify account team rather than improvise a configuration.
A blocked enrolment is still active; Unify has paused it rather than send a broken message. Its documented causes are missing or invalid template variables, a paused mailbox, or a mailbox needing reauthorisation. Unify states that once the underlying issue is fixed it automatically unblocks and reschedules the step, so the fix is in Unify's settings, not in the agent.
Partly, and the most precise statement is in its privacy policy rather than its product documentation. Unify writes that it may be deemed a data broker in certain applicable states, and that it requires its data providers to certify lawful collection and consent. Its directory description separately claims coverage of 1.1B+ people across 40+ data providers, which Unify does not enumerate.
Sources
- Unify MCP getting-started guide (fetched 2026-09-08; the directory's
https://docs.unifygtm.com/developers/mcpresolves here) · retrieved 2026-09-08 - Unify MCP tools reference (fetched 2026-09-08) · retrieved 2026-09-08
- Unify Sequence enrollments reference (fetched 2026-09-08) · retrieved 2026-09-08
- Unify mailbox operations reference (fetched 2026-09-08) · retrieved 2026-09-08
- Unify credit system reference (fetched 2026-09-08) · retrieved 2026-09-08
- Unify exclusions guide (fetched 2026-09-08) · retrieved 2026-09-08
- Unify privacy policy (fetched 2026-09-08) · retrieved 2026-09-08
- Unify machine-readable doc index (fetched 2026-09-08).
docs.unifygtm.com/robots.txtcarriesContent-Signal: ai-train=yes, search=yes, ai-input=yes, an explicit grant for AI synthesis;www.unifygtm.com/robots.txtcarriesai-train=no, search=yes, ai-input=yesand names ClaudeBot withAllow: /· retrieved 2026-09-08 - Live authentication probe against
https://mcp.unifygtm.com/mcp— anonymousinitializereturned HTTP 401 with awww-authenticateBearer challenge naminghttps://mcp.unifygtm.com/.well-known/oauth-protected-resource/mcp, whose RFC 9728 descriptor returned HTTP 200 withauthorization_servers: ["https://auth.unifygtm.com/"]and noscopes_supported(2026-09-08). No tool was ever called. · retrieved 2026-09-08 - Anthropic Connectors Directory entry (snapshot 2026-09-08). Tool names, the tool count of 50, the partner tier and the 1.1B+ people / 40+ providers coverage claim are Unify's and Anthropic's, not ours. · retrieved 2026-09-08
Server Info
- Category
- Sales & CRM
- Developer
- Unify
- Tools
- 50
- Domain
- mcp.unifygtm.com
Using Claude Desktop or another MCP client? Setup docs — the connection URL above works anywhere.
Similar MCP Servers for Sales & CRM
Related Resources
Ready to connect Unify?
Connect Unify once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.