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.

Merge (Unified Integration API) MCP Server for CrewAI 8 tools — connect in under 2 minutes

Name: Merge (Unified Integration API)
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 8 Tools Framework

Connect your CrewAI agents to Merge (Unified Integration API) through the Vinkius — pass the Edge URL in the `mcps` parameter and every Merge (Unified Integration API) tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

python

from crewai import Agent, Task, Crew

agent = Agent(
    role="Merge (Unified Integration API) Specialist",
    goal="Help users interact with Merge (Unified Integration API) effectively",
    backstory=(
        "You are an expert at leveraging Merge (Unified Integration API) tools "
        "for automation and data analysis."
    ),
    # Your Vinkius token — get it at cloud.vinkius.com
    mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)

task = Task(
    description=(
        "Explore all available tools in Merge (Unified Integration API) "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 8 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About Merge (Unified Integration API) MCP Server

Connect your Merge.dev account to any AI agent and take full control of your unified B2B integrations across HRIS, ATS, CRM, and Ticketing through natural conversation.

When paired with CrewAI, Merge (Unified Integration API) becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Merge (Unified Integration API) tools autonomously — one agent queries data, another analyzes results, a third compiles reports — all orchestrated through the Vinkius with zero configuration overhead.

What you can do

HRIS Orchestration — List all active employees and organizational companies from your connected HRIS (e.g., BambooHR, Workday, HiBob) directly from your agent
ATS Talent Pipeline — Retrieve recruited candidates and tracked job applications from your ATS integration (e.g., Greenhouse, Lever, Ashby) to monitor hiring workflows
CRM Contact Management — Access external sales contacts and customer accounts from your CRM (e.g., Salesforce, HubSpot, Pipedrive) to manage your business directory securely
Ticketing & Support — List inbound and outbound support tickets from your issue-tracking boards (e.g., Zendesk, Jira, Front) to stay updated on customer issues
Unified Data Access — Retrieve standardized data structures across hundreds of different integrations using a single set of API tools natively handled by Merge
Integration Audit — Inspect linked account details and meta-configurations to understand the current state and boundaries of your connected workspace securely

The Merge (Unified Integration API) MCP Server exposes 8 tools through the Vinkius. Connect it to CrewAI in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Merge (Unified Integration API) to CrewAI via MCP

Follow these steps to integrate the Merge (Unified Integration API) MCP Server with CrewAI.

Install CrewAI

Run pip install crewai

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com

Customize the agent

Adjust the role, goal, and backstory to fit your use case

Run the crew

Run python crew.py — CrewAI auto-discovers 8 tools from Merge (Unified Integration API)

Why Use CrewAI with the Merge (Unified Integration API) MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with Merge (Unified Integration API) through the Model Context Protocol.

Multi-agent collaboration lets you decompose complex workflows into specialized roles — one agent researches, another analyzes, a third generates reports — each with access to MCP tools

CrewAI's native MCP integration requires zero adapter code: pass the Vinkius Edge URL directly in the `mcps` parameter and agents auto-discover every available tool at runtime

Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls

Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

Merge (Unified Integration API) + CrewAI Use Cases

Practical scenarios where CrewAI combined with the Merge (Unified Integration API) MCP Server delivers measurable value.

Automated multi-step research: a reconnaissance agent queries Merge (Unified Integration API) for raw data, then a second analyst agent cross-references findings and flags anomalies — all without human handoff

Scheduled intelligence reports: set up a crew that periodically queries Merge (Unified Integration API), analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain Merge (Unified Integration API) tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

Compliance and audit automation: a compliance agent queries Merge (Unified Integration API) against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

Merge (Unified Integration API) MCP Tools for CrewAI (8)

These 8 tools become available when you connect Merge (Unified Integration API) to CrewAI via MCP:

get_account_details

dev. Retrieve linked Account Details exposing integration boundaries

list_accounts

List customer accounts parsed from the CRM integration

list_applications

List job applications inside the ATS integration

list_candidates

List recruited candidates across the ATS integration

list_companies

List companies mapped inside the HRIS integration

list_contacts

List external contacts mapped in the CRM integration

list_employees

Be aware the list might be paginated or heavy. List employees from the linked HRIS integration

list_tickets

List inbound/outbound support tickets inside the Ticketing integration

Example Prompts for Merge (Unified Integration API) in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with Merge (Unified Integration API) immediately.

"List all active employees from our linked HRIS"

"Show me the last 5 candidates in our ATS talent pipeline"

"List all open support tickets in our ticketing integration"

Troubleshooting Merge (Unified Integration API) MCP Server with CrewAI

Common issues when connecting Merge (Unified Integration API) to CrewAI through the Vinkius, and how to resolve them.

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts — check console output.

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.

Rate limiting or 429 errors

The Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

Merge (Unified Integration API) + CrewAI FAQ

Common questions about integrating Merge (Unified Integration API) MCP Server with CrewAI.

How does CrewAI discover and connect to MCP tools?

CrewAI connects to MCP servers lazily — when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.

Can different agents in the same crew use different MCP servers?

Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.

What happens when an MCP tool call fails during a crew run?

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.

Can CrewAI agents call multiple MCP tools in parallel?

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.

Can I run CrewAI crews on a schedule (cron)?

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.