How to Use the Checkr MCP in CrewAI

Q: How does a 'monitor' agent in CrewAI use Checkr tools differently than an 'action' agent?

A monitor agent would primarily use read-only tools like listbackgroundreports and getcandidatedetails in a loop. An action agent would use tools that change state, like createnewcandidate or startbackgroundcheck, usually triggered by the monitor agent.

Deploy an autonomous CrewAI team to manage your Checkr screening and compliance process.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Checkr MCP to CrewAI

Create your Vinkius account to connect Checkr 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 Checkr with CrewAI

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Specialize Agents for HR Roles

Don't build one giant agent. Build a team. Assign a "Recruiting Coordinator" agent the task of managing new applicants. It uses `create_new_candidate` to add people to Checkr as they come in from your applicant tracking system. This agent's only job is to manage the candidate list. It can periodically run `list_checkr_candidates` to ensure its internal state matches what's in Checkr. CrewAI lets you define this specific role and give it only the tools it needs for the job.

Autonomous Compliance Monitoring

A second agent, the "Compliance Officer," handles the actual checks. Once a candidate is created, this agent takes over. It uses `start_background_check` to begin the process. Its main loop consists of calling `list_background_reports` to monitor progress across all candidates. When a report is complete, this agent uses `get_report_details` to check the result. If it's anything but 'clear', it can assign a task back to a human or another agent for manual review. This MCP Server gives your crew the exact functions they need to do their jobs.

Collaborative Onboarding Handoffs

CrewAI agents work together. When the "Compliance Officer" agent finds a 'clear' report, it can pass the candidate ID to a third agent, the "Onboarding Specialist." This handoff is what makes a crew so effective. The Onboarding agent can then use `get_candidate_details` to pull the candidate's name and email to kick off the next phase of your company's process. The agents share context, but the tools from this MCP are what allow them to take specific, concrete actions.

Setup guide

Set up Checkr 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 Checkr tools as needed.

crew.py

from crewai import Agent, Task, Crew

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

task = Task(
    description="List recent Checkr 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="Checkr Analyst",
        goal="Access and analyze Checkr data via MCP.",
        backstory="Expert analyst with direct Checkr access.",
        tools=mcp_tools,
    )

    task = Task(
        description="List recent Checkr 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 Checkr. 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 Checkr 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 Checkr MCP in CrewAI

Assign different roles to your agents. One agent adds candidates using `create_new_candidate`. A second agent monitors them with `list_background_reports` and `get_report_details`. This division of labor lets you build a more robust and focused automation.

Yes. When you configure the Checkr MCP Server in CrewAI, you can use the `tool_filter` option. This lets you specify exactly which tools, like `start_background_check` or `get_report_details`, a particular agent is allowed to use.

The simplest method is to pass the Vinkius URL directly into the `mcps` list when you define your agent in Python. CrewAI will handle fetching the tools and making them available to your agent automatically.

A monitor agent would primarily use read-only tools like `list_background_reports` and `get_candidate_details` in a loop. An action agent would use tools that change state, like `create_new_candidate` or `start_background_check`, usually triggered by the monitor agent.

Data is handled within Vinkius's secure, single-tenant sandbox for each request. While CrewAI agents share a working context, the actual candidate PII from Checkr only exists for the lifecycle of the tool call. You can also use `tool_filter` during setup to ensure only specific agents can even see the tools that access sensitive data.

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