Bring Recruspace
to CrewAI
Learn how to connect RecruSpace to CrewAI and start using 11 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the RecruSpace MCP Server?
Connect your RecruSpace account to any AI agent to streamline your hiring and talent orchestration through natural conversation. RecruSpace provides a modern recruitment platform for programmatically managing candidates, organizing talent pools, and tracking job post statuses through its robust API.
What you can do
- Candidate & Applicant Orchestration — List all managed candidates and add new potential hires with detailed profile metadata programmatically.
- Talent Pool Intelligence — Access and monitor your talent pools and create new collections to organize your recruitment pipeline directly from the AI interface.
- Job Post Lifecycle Management — List all active job posts and retrieve detailed metadata to maintain a clear overview of your hiring needs via natural language.
- Candidate Deep-Dive — Retrieve granular details for specific candidates to understand full context and qualification metrics.
- Operational Monitoring — Track system activity and manage recruitment metadata using simple AI commands.
How it works
1. Subscribe to this server
2. Enter your RecruSpace API Key from your account settings
3. Start managing your recruitment pipeline from Claude, Cursor, or any MCP-compatible client
No more manual status checking or spreadsheet candidate tracking. Your AI acts as a dedicated recruitment coordinator or HR lead.
Who is this for?
- HR Managers & Recruiters — quickly retrieve candidate summaries and monitor talent pool growth without switching apps.
- Hiring Operations Teams — automate the ingestion of new candidates and track qualification stages via natural conversation.
- Developers — integrate real-time recruitment data and talent intelligence into custom business dashboards.
Built-in capabilities (11)
Pass data as a JSON string. Add a new candidate
Create a new talent pool
Get specific candidate details
Get details for a specific job posting
Get details for a talent pool
List all candidates
List all scheduled interviews
List all job posts
List all hiring pipelines
List all talent pools
Update candidate information
Why CrewAI?
When paired with CrewAI, RecruSpace becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call RecruSpace 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
mcpsparameter 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
RecruSpace in CrewAI
RecruSpace and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect RecruSpace 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.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 3,400+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for RecruSpace in CrewAI
The RecruSpace 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 11 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.
* 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
How Vinkius secures
RecruSpace for CrewAI
Every tool call from CrewAI to the RecruSpace MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can my AI automatically find the details for a specific candidate by providing their ID?
Yes! Use the get_candidate_details tool with the Candidate ID. Your agent will respond with the complete metadata for the profile, including qualifications and status in seconds.
How do I find my RecruSpace API Key?
Log in to your RecruSpace account, navigate to the Settings or API section, and you will find your unique secret API key there.
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.
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
Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.