Connect your AI Agents to Unify in minutes

What is a Unify MCP?

It's an MCP server that lets your agents access data and functionality from Unify via tools. Your agents can invoke these tools to pull intent signals for an account, look up a company's buying stage, enroll a contact in a play, check enrichment data, and more.

Unify doesn't offer an MCP server purpose built for Unify, but you can use one from a third-party platform, like Merge Agent Handler.

How can I use the Unify MCP server?

The use cases naturally depend on the agent you've built, but here are a few common ones:

• Intent-signal-triggered outreach: an agent watches an events query for a spike in an account's intent signals, like repeated G2 category page visits, and kicks off a personalized outbound sequence the moment the signal crosses a threshold

• Account scoring and prioritization: an agent pulls attribute values across a list of target accounts and ranks them by buying-stage signal strength, then flags the top movers for the sales team each morning

• Sales play automation: an agent detects a new signal match on a contact, creates the record to enroll them in the right play, and confirms the enrollment without anyone touching Unify directly

• Cross-tool GTM data correlation: an agent joins Unify account records with open opportunities in the CRM to surface accounts showing rising intent but no active pipeline, then routes them to the right rep

What are popular tools for Unify's MCP server?

Here are some of the most commonly used tools:

• list_objects: returns the object types defined in a Unify workspace, including custom objects built on top of companies and contacts. Useful for agents that need to discover the data model before querying records

• find_record: searches for a record matching a set of filter conditions, like a company domain or a contact's email. Call this when an agent needs to check whether a record already exists before creating one

• upsert_record: creates a record if it doesn't exist or updates it if it does, in a single call. Good for workflows that sync account or contact data from another system without a separate lookup step

• get_record: retrieves a single record by ID, returning its current attribute values. Helpful when an agent needs the latest state of an account before deciding on a next action

• create_events_query: kicks off a query against Unify's event data, like intent signals or page visits, scoped to a time window and set of accounts. Use this when an agent needs to detect a signal spike rather than pull a single record

• get_events_query_results: fetches the results of a previously submitted events query once it's finished processing. Agents typically call this right after create_events_query to pull the actual signal data

What makes Merge Agent Handler's Unify MCP server better than alternative Unify MCP servers?

There are several reasons to use Merge Agent Handler's Unify MCP server over building or maintaining your own:

• Enterprise-grade security and DLP: Merge Agent Handler includes built-in data loss prevention controls that let you block or redact sensitive fields before they reach an agent. For Unify, this means you can prevent account-level intent scores and contact-level signal data from being exposed even when the agent has broad read access

• Managed authentication and credentials: Merge stores and refreshes Unify credentials on your behalf. You never expose raw API keys or OAuth tokens to an agent or manage token rotation manually

• Real-time observability and audit trail: every tool call made against Unify is logged with timestamp, tool name, input parameters, and response metadata. You can audit exactly what an agent read or wrote without instrumenting anything yourself

• Tool Packs and controlled access: bundle specific Unify tools with tools from other connectors into a single MCP endpoint, scoped to a specific use case. An agent gets exactly the tools it needs, nothing more

How can I start using Merge Agent Handler's Unify MCP server?

You can take the following steps:

1. Create or log into your Merge Agent Handler account.

2. Install the Merge CLI by running pipx install merge-api, then run merge configure to link the CLI to your Merge account and merge login to authenticate your session.

3. Register the Agent Handler MCP server with Claude Code by running claude mcp add --transport http agent-handler https://ah-api.merge.dev/mcp, then open Claude Code and run /mcp to confirm agent-handler appears with a connected status.

4. Select agent-handler from the MCP list. This opens a browser window where you select which integrations to authenticate. Choose Unify and complete the auth flow. Merge stores and manages the credentials going forward.

5. Open a Claude Code session and start querying Unify data directly. The first time you use a Unify tool, a Magic Link may appear to complete connector authentication.

If you want to connect Merge Agent Handler's Unify MCP with internal or customer-facing agentic products, you can follow the steps in our docs.

Can employees use Merge Agent Handler to connect their AI tools to Unify?

Yes, Agent Handler for Employees lets your employees connect Claude, ChatGPT, Microsoft Copilot, Cursor, and other MCP-compatible AI tools to Unify without bypassing IT governance.

IT can provision access by role or group via SCIM. A sales development rep, for example, gets Unify access to check an account's latest intent signals, Salesforce to log outreach, and Slack to alert their manager; while a demand generation marketer gets Unify access to monitor signal spikes across target accounts, HubSpot to update campaign audiences, and Google Sheets to track weekly signal reports.

Every tool call an employee's AI makes to Unify is also inspected against your DLP rules and logged to a searchable audit trail, giving security teams full visibility into what data was accessed and by whom.