# Merge (Unified Integration API) MCP

> Merge connects your AI agent directly to HRIS, ATS, CRM, and ticketing platforms. You use a single conversation to list employees from Workday, check candidates in Greenhouse, or track support tickets in Zendesk. It unifies disparate business data sources—from employee records to customer issues—into one flow for immediate querying and analysis.

## Overview
- **Category:** developer-tools
- **Price:** Free
- **Tags:** unified-api, hris-integration, ats-integration, crm-integration, ticketing-api, data-synchronization

## Description

You connect your AI agent to Merge and it hooks you up with data from HRIS, ATS, CRM, and ticketing platforms. You use one chat window for everything—you list employees from Workday, check candidates in Greenhouse, or pull support tickets from Zendesk. It unifies all that messy business junk—from employee profiles to customer issues—so your agent can query it right away.

Getting started? Your AI client just needs to talk to the server. You don't gotta jump between dashboards or write complex API calls just to gather a report. The system handles routing and data standardization across all those systems.

**Account Setup & Boundaries:**
`get_account_details` retrieves metadata about the linked account, letting you review integration boundaries; `list_accounts` gets a list of customer accounts mapped inside your CRM integration.

**HRIS Data (Employees & Companies):**
You can check out all active employees using `list_employees`; it handles large data sets. You also get organizational company details by calling `list_companies`, pulling structured lists from your connected HR system.

**ATS Data (Candidates & Applications):**
Want to see who's in the pipeline? `list_candidates` pulls a list of all recruited candidates across the entire ATS integration. To check job applications, you run `list_applications`, getting every application currently stored within your ATS setup.

**CRM Data (Contacts & Accounts):**
You access external sales contacts using `list_contacts`, grabbing every contact defined in your CRM integration. You can also call `list_accounts` to get a list of customer accounts mapped inside the system.

**Ticketing Board:**
The server lets you pull support tickets, running `list_tickets` retrieves all inbound and outbound support issues from your issue-tracking board.

Your agent uses these tools together. You can ask it to find employees who are also listed as external contacts, or check the status of a candidate while pulling up related customer accounts—all in one go.

## Tools

### list_employees
Lists all employees from the connected HRIS integration. Be ready for large data sets.

### list_companies
Lists organizational companies mapped in the HRIS integration.

### list_candidates
Retrieves a list of recruited candidates across your entire ATS integration.

### list_applications
Lists job applications currently stored within the ATS integration.

### list_contacts
Gets a list of external contacts defined within your CRM integration.

### list_accounts
Gets a list of customer accounts mapped inside your CRM integration.

### list_tickets
Retrieves a list of inbound and outbound support tickets from your ticketing board.

### get_account_details
Retrieves metadata about the linked account, showing integration boundaries for review.

## Prompt Examples

**Prompt:** 
```
List all active employees from our linked HRIS
```

**Response:** 
```
Retrieving employee data… I've identified 125 active employees in your HRIS. Highlights include Alex Smith (Software Engineer), Sarah Johnson (Marketing Manager), and Mark Rivera (Product Designer). Would you like the full profile details for any department?
```

**Prompt:** 
```
Show me the last 5 candidates in our ATS talent pipeline
```

**Response:** 
```
Retrieving candidates… I've identified the 5 most recent additions: 1) Jamie Lann (Senior Dev), 2) Riley Vane (UX Lead), 3) Casey Wright, 4) Jordan Bell, and 5) Taylor Reed. I can check the status of their active applications if you'd like.
```

**Prompt:** 
```
List all open support tickets in our ticketing integration
```

**Response:** 
```
I've retrieved your open support tickets. There are 12 active issues, including 'Login Loop Bug' (Priority: High), 'Pricing Question' (Priority: Med), and 'API Auth Error'. Would you like me to extract the full metadata for the high-priority bug?
```

## Capabilities

### List Active Employee Data
Retrieves current employee lists and organizational company details from your linked HRIS system.

### Query Candidate Records
Lists job applicants and tracked candidates across the ATS integration to review hiring pipeline status.

### Retrieve CRM Contacts
Accesses external sales contacts and customer accounts stored in your connected CRM system.

### Check Support Tickets
Lists both inbound and outbound support tickets from your issue-tracking board.

### View Account Metadata
Retrieves specific details about the connected account to verify integration boundaries.

## Use Cases

### Checking candidate overlap
A recruiter needs to know if a high-potential job applicant (ATS) already exists as a sales contact in the CRM. They ask the agent, "Cross-reference candidates with our top contacts." The system runs `list_candidates` and compares results against `list_contacts`, solving the manual spreadsheet matching problem.

### Post-onboarding data audit
A Product Manager needs to verify that every new employee (HRIS) has a corresponding account record (CRM). They prompt, "Show me all employees without an associated CRM account." The agent runs `list_employees` and then checks for matches in `list_accounts`, instantly identifying gaps.

### Triaging a critical customer issue
A support lead receives a ticket (Ticketing). They ask the agent to look up the client's history. The system runs `list_tickets` and uses that account ID to pull related contact details from the CRM (`list_contacts`), giving immediate context.

### Reviewing company structure changes
An executive wants to see how many people (HRIS) are working for companies listed in the CRM. The agent executes `list_companies` and compares the resulting list against the data from `list_employees`, providing a clean headcount report.

## Benefits

- Correlate employee records and contacts. Instead of checking Workday, then Salesforce, you ask the agent for "all employees who are also key contacts." It runs `list_employees` and `list_contacts`, giving you a single list that cross-references both sources.
- Track candidates through the entire lifecycle. You can get status updates on applications (`list_applications`) and see which candidates are flagged as high potential (`list_candidates`), all without leaving your chat window.
- Get full visibility into customer issues. Running `list_tickets` provides a real-time snapshot of open support tickets, allowing you to immediately prioritize based on issue type or client account found in the CRM data.
- Verify integration health instantly. Use `get_account_details` to audit your linked workspace and see exactly which systems are connected and what boundaries the API can touch—no manual setup checks required.
- Standardize reporting across silos. By unifying access, you stop dealing with proprietary formats. You get a standardized data structure whether the information came from an HRIS or an ATS.

## How It Works

The bottom line is: You ask a question about your business data once, and the server handles connecting to all the right places to answer it.

1. Subscribe to the server and input your Merge API Key and dedicated Account Token.
2. Send a natural language prompt to your AI client (e.g., "Show me all high-priority tickets for contacts in the West region").
3. The agent runs the necessary tools, pulls data from HRIS, CRM, ATS, or Ticketing, and provides you with one unified response.

## Frequently Asked Questions

**Can I use list_employees to find people who are also CRM contacts?**
Yes. You ask your agent for a cross-reference query (e.g., "List employees who match any records in the CRM"). The server uses `list_employees` and compares that output against data pulled from `list_contacts`.

**Does list_tickets include historical or just open support tickets?**
The tool retrieves both inbound and outbound support tickets. You can refine your prompt to specify if you only want 'open' issues, helping the agent filter the data for you.

**What is the difference between list_candidates and list_applications?**
`list_candidates` gives a roster of people tracked in your ATS. `list_applications` provides specific records detailing job submissions, showing which roles they applied for.

**Is getting account details the same as listing accounts?**
No. `get_account_details` checks the connection's overall configuration and boundaries. `list_accounts` actually retrieves a list of specific customer records from the CRM integration.

**If I update my credentials, how do I verify changes using get_account_details?**
You must use `get_account_details` after updating your API key or token. This tool lets you inspect the current integration boundaries and ensures your agent is pointing to the correct data source immediately.

**When I run list_employees, how does the system handle pagination for large organizations?**
The MCP server handles pagination automatically. If there are thousands of records, your AI client doesn't just get the first page; it loops through all necessary API calls to pull every available employee record.

**Does list_candidates have visibility into rejected applicants or only active ones?**
The `list_candidates` tool pulls data based on what your ATS integration exposes, typically including both active and historical records. You can filter the results within your AI client to focus only on specific statuses.

**If list_contacts fails due to a CRM service outage, does it affect other tools?**
No. The MCP server isolates tool calls. If `list_contacts` throws an error, your agent will report that failure clearly without affecting the ability to run commands like `list_tickets` or `list_companies`.

**Which integrations does Merge support through the unified API?**
Merge supports over 150+ integrations across HRIS (BambooHR, Workday), ATS (Lever, Greenhouse), CRM (Salesforce, HubSpot), and Ticketing (Zendesk, Jira). Your agent can access all of them using the same standardized tools once the accounts are linked in Merge.

**How do I target a specific customer's data through the agent?**
Each request requires a `MERGE_ACCOUNT_TOKEN` which uniquely identifies a linked account (e.g., a specific customer's integration). By providing this token along with your API key, your agent can retrieve data exclusively from that customer's connected platform.

**Can my agent list candidates from my ATS and support tickets from Zendesk at the same time?**
Yes. Since Merge unifies multiple categories, your agent can use the `list_candidates` and `list_tickets` tools in the same conversation to bridge data from different functional areas of your business instantly.