4,000+ servers built on vurb.ts
Vinkius
CrewAIFramework
Ashby MCP Server

Bring Applicant Tracking
to CrewAI

Learn how to connect Ashby to CrewAI and start using 10 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.

MCP Inspector GDPR Free for Subscribers
Create Ashby CandidateGet Ashby ApplicationGet Ashby CandidateGet Ashby JobList Ashby ApplicationsList Ashby CandidatesList Ashby FeedbackList Ashby InterviewsList Ashby JobsList Ashby Users

Compatible with every major AI agent and IDE

ClaudeClaude
ChatGPTChatGPT
CursorCursor
GeminiGemini
WindsurfWindsurf
VS CodeVS Code
JetBrainsJetBrains
VercelVercel
+ other MCP clients
Ashby

What is the Ashby MCP Server?

Connect your Ashby account to any AI agent and take full control of your recruiting pipeline and candidate experience through natural conversation.

What you can do

  • Candidate Orchestration — List and manage candidate profiles programmatically, including creating new records and retrieving high-fidelity profile metadata
  • Application Lifecycle Management — Monitor job applications and retrieve detailed status metrics for specific candidates to coordinate your hiring funnel in real-time
  • Interview Intelligence — Access scheduled interviews and retrieve submitted high-fidelity feedback reports to summarize performance and sentiment
  • Job & Department Visibility — Retrieve complete directories of open jobs, departments, and hiring managers to maintain a perfectly coordinated organizational view
  • User & Location Monitoring — Access your internal recruiter directory and physical office locations directly through your agent for instant operational reporting

How it works

  1. Subscribe to this server
  2. Retrieve your API Key from the Ashby dashboard (Admin > API Keys)
  3. Start managing your talent pipeline from Claude, Cursor, or any MCP client

No more manual toggling between browser tabs to check a candidate's status or feedback. Your AI acts as your dedicated talent coordinator and recruiting architect.

Who is this for?

  • Recruiters & Sourcers — instantly retrieve candidate summaries and update application stages using natural language commands
  • Hiring Managers — check interview feedback and pipeline health across departments without leaving your creative workspace
  • HR Operations — automate the oversight of job postings and user permissions through simple AI queries

Built-in capabilities (10)

create_ashby_candidate

Create candidate

get_ashby_application

Get application details

get_ashby_candidate

Get candidate details

get_ashby_job

Get job details

list_ashby_applications

List applications

list_ashby_candidates

List candidates

list_ashby_feedback

List feedback

list_ashby_interviews

List interviews

list_ashby_jobs

List jobs

list_ashby_users

List users

Why CrewAI?

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

  • 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 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

See it in action

Ashby in CrewAI

AI AgentVinkius
High Security·Kill Switch·Plug and Play
Why Vinkius

Ashby and 4,000+ other MCP servers. One platform. One governance layer.

Teams that connect Ashby to CrewAI through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.

4,000+MCP Servers ready
<40msCold start
60%Token savings
Raw MCP
Vinkius
Server catalogFind and host yourself4,000+ managed
InfrastructureSelf-hostedSandboxed V8 isolates
Credential handlingPlaintext in configVault + runtime injection
Data loss preventionNoneConfigurable DLP policies
Kill switchNoneGlobal instant shutdown
Financial circuit breakersNonePer-server limits + alerts
Audit trailNoneEd25519 signed logs
SIEM log streamingNoneSplunk, Datadog, Webhook
HoneytokensNoneCanary alerts on leak
Custom domainsNot applicableDNS challenge verified
GDPR complianceManual effortAutomated purge + export
Enterprise Security

Why teams choose Vinkius for Ashby in CrewAI

The Ashby 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. All 10 tools execute in hardened sandboxes optimized for native MCP execution.

Your AI agents in CrewAI only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.

Ashby
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

The Vinkius Advantage

How Vinkius secures Ashby for CrewAI

Every tool call from CrewAI to the Ashby MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.

< 40msCold start
Ed25519Signed audit chain
60%Token savings
FAQ

Frequently asked questions

01

How do I find my Ashby API Key?

Log in as an Admin, navigate to Admin > API Keys, and generate a new key for your integration.

02

Can I retrieve interview feedback via AI?

Yes! The list_ashby_feedback tool allows your agent to retrieve high-fidelity feedback reports submitted by interviewers.

03

How do I create a new candidate record?

Use the create_ashby_candidate tool and provide a JSON object with the candidate's name and contact details programmatically.

04

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.

05

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.

06

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.

07

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.

08

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.

09

MCP tools not discovered

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

10

Agent not using tools

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

11

Timeout errors

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

12

Rate limiting or 429 errors

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

Explore More MCP Servers

View all →