How to Use the Ashby MCP in CrewAI

Q: Is it easy to set up Ashby with CrewAI?

Yes, it's very simple. Just install the crewaitools package and pass your Vinkius MCP URL directly into the mcps parameter when you define your Agent. For more control, you can use MCPServerHTTP to filter which tools the agent can access.

Q: How do I give different agents in my crew different permissions for Ashby?

When defining your agents, use the MCPServerHTTP class from crewai.mcp. It has a toolfilter argument that lets you specify exactly which tools from the Ashby server that particular agent is allowed to use.

Deploy a crew of AI agents to autonomously manage your Ashby recruiting pipeline with CrewAI.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Ashby MCP to CrewAI

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

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Assign Recruiting Roles to Agents

Give your CrewAI agents specialized jobs using these Ashby tools. One agent's role can be 'Sourcer,' using `list_ashby_candidates` and `get_ashby_candidate` to find profiles that match certain criteria. Its only job is to find people. A second agent, the 'Coordinator,' can then take the Sourcer's findings and use `list_ashby_interviews` to check availability or `get_ashby_application` to review status. Each agent focuses on one task, making your operation more organized.

Autonomous Pipeline Management

Build a crew that runs your hiring process for you. A 'Job Monitor' agent can periodically run `list_ashby_jobs` to watch for new openings. When it finds one, it passes the info to a 'Candidate Search' agent. That search agent then uses `list_ashby_candidates` with specific filters. The results are passed to an 'Analyst' agent that reviews their details. This entire sequence runs without you lifting a finger, all powered by this MCP Server.

Filter Tools for Agent Specialization

CrewAI's `tool_filter` lets you give each agent only the tools they need. Your 'Scheduler' agent might only have access to `list_ashby_interviews`, while a 'Reviewer' agent only gets `list_ashby_feedback`. This prevents agents from performing actions outside their defined role. This is how you build safe, autonomous systems. You can even have a 'Creator' agent that is the only one with permission to use `create_ashby_candidate`, adding a layer of control to your multi-agent setup.

Setup guide

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

crew.py

from crewai import Agent, Task, Crew

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

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

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

It's a perfect fit. You can assign different Ashby tools to different agents in your crew. For example, one agent can be responsible for finding candidates with `list_ashby_candidates`, while another handles scheduling using `list_ashby_interviews`.

Yes, it's very simple. Just install the `crewai[tools]` package and pass your Vinkius MCP URL directly into the `mcps` parameter when you define your Agent. For more control, you can use `MCPServerHTTP` to filter which tools the agent can access.

That's exactly what this combination is for. You can create a 'sourcing' agent, a 'screening' agent, and a 'scheduling' agent that collaborate to move candidates through your Ashby pipeline automatically.

When defining your agents, use the `MCPServerHTTP` class from `crewai.mcp`. It has a `tool_filter` argument that lets you specify exactly which tools from the Ashby server that particular agent is allowed to use.

The system is designed for security. When an agent in your crew calls a tool, it only requests the specific data it needs, like a list of jobs or candidate details. Vinkius isolates each MCP Server run in a zero-trust sandbox, and all data transmission is encrypted. No recruiting data is ever persisted on the server.

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