How to Use the Merge (Unified Integration API) MCP in CrewAI

Deploy autonomous CrewAI teams to manage your HRIS, ATS, and CRM data using a unified interface.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Merge (Unified Integration API) MCP to CrewAI

Create your Vinkius account to connect Merge (Unified Integration API) to CrewAI and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup Merge (Unified Integration API) with CrewAI

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Role-based agent data access

Assign specific tools like `list_employees` to a research agent and `list_tickets` to a support agent. They share the context and act as a coordinated unit. This specialization prevents a single agent from getting overwhelmed. Your crew handles the heavy lifting while maintaining distinct responsibilities for different data sets.

Coordinate with Merge (Unified Integration API)

Give your CrewAI agents access to the Merge (Unified Integration API) MCP Server to gather intel across your entire stack. The agents use the same tool set to stay aligned. It removes the friction of managing individual vendor APIs. The agents just ask for the data they need and the server handles the translation.

Autonomous operations and monitoring

Set up a monitor agent to watch your CRM and ATS status using `list_companies` and `list_applications`. It alerts the crew when it detects changes. You build an automated feedback loop that works 24/7. It keeps your operations running without you needing to manually trigger every sync.

Setup guide

Set up Merge (Unified Integration API) MCP in CrewAI

Prerequisites

Python 3.10+ installed
crewai package (pip install crewai)
Active Vinkius subscription with a valid endpoint token

1

Install CrewAI
Run pip install crewai to install the framework. MCP support is built-in via the mcps parameter.
2

Add the MCP URL to your agent
Pass your Vinkius endpoint directly to the mcps list. Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. CrewAI handles tool discovery and caching automatically.
3

Kick off your crew
Create a Crew with your agent and tasks. Call crew.kickoff() — the agent will automatically invoke Merge (Unified Integration API) tools as needed.

crew.py

from crewai import Agent, Task, Crew

agent = Agent(
    role="Merge (Unified Integration API) Analyst",
    goal="Access and analyze Merge (Unified Integration API) data via MCP.",
    backstory="Expert analyst with direct Merge (Unified Integration API) access.",
    mcps=[
        "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    ],
)

task = Task(
    description="List recent Merge (Unified Integration API) transactions",
    agent=agent,
    expected_output="A summary of recent activity",
)

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

Get your connection token →

Prerequisites

Python 3.10+ installed
crewai + crewai-tools packages
Active Vinkius subscription with a valid endpoint token

1

Install dependencies
Run pip install crewai crewai-tools. The MCPServerAdapter handles lifecycle management and tool conversion.
2

Connect with MCPServerAdapter
Use MCPServerAdapter as a context manager with SseServerParameters pointing to your Vinkius endpoint. The adapter automatically manages connection lifecycle.
3

Assign tools and run
Pass the returned mcp_tools to your agent's tools parameter. The adapter converts MCP tools to native BaseTool objects compatible with all CrewAI agents.

crew.py

from crewai import Agent, Task, Crew
from crewai_tools import MCPServerAdapter
from mcp import SseServerParameters

server_params = SseServerParameters(
    url="https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
)

with MCPServerAdapter(server_params) as mcp_tools:
    agent = Agent(
        role="Merge (Unified Integration API) Analyst",
        goal="Access and analyze Merge (Unified Integration API) data via MCP.",
        backstory="Expert analyst with direct Merge (Unified Integration API) access.",
        tools=mcp_tools,
    )

    task = Task(
        description="List recent Merge (Unified Integration API) transactions",
        agent=agent,
        expected_output="A summary of recent activity",
    )

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

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Merge. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect Merge (Unified Integration API) now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about Merge (Unified Integration API) MCP in CrewAI

Yes, agents within a crew share memory. When one agent retrieves data via the API, the rest of the team can use that information for their own tasks.

You can assign tools to specific agents based on their role. The server acts as the unified source of truth for all agents in the crew.

It is. The server supports concurrent access, meaning multiple agents can query different endpoints simultaneously without interfering with each other.

Each request is isolated. We use secure endpoints for all communications, ensuring that your HRIS and ATS information stays between you and the service.

The server only processes job applications and contact lists during active operations. We don't store your HRIS data, and we clear session memory immediately after use.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript