Bring Employee Management
to CrewAI
Learn how to connect WebHR 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 WebHR MCP Server?
Connect your WebHR account to any AI agent to automate your human resource management and personnel tracking. WebHR provides a comprehensive cloud-based HRMS for managing the entire employee lifecycle—from recruitment and onboarding to attendance monitoring and leave management.
What you can do
- Employee Orchestration — List and retrieve detailed metadata for all staff records, including personal profiles and department hierarchies.
- Attendance Monitoring — Access real-time clock-in/out records and retrieve aggregated attendance summaries for your organization.
- Leave Management — Track leave requests, monitor balance details, and list different leave types available in your system.
- Recruitment Control — Monitor open job postings, list active candidates, and manage the recruitment pipeline programmatically.
- Structural Oversight — Access company locations and department definitions to maintain a clear overview of your organizational structure.
How it works
1. Subscribe to this server
2. Enter your WebHR API Key from your Setup settings
3. Start managing your human resources from Claude, Cursor, or any MCP-compatible client
Who is this for?
- HR Managers — automate the monitoring of staff attendance and recruitment progress via natural language.
- Operations Leads — quickly retrieve employee details and department structures without switching applications.
- Business Owners — get instant summaries of organizational health and personnel metrics straight through the chat.
Built-in capabilities (11)
Get aggregated attendance metrics
Get details for an employee
List clock-in/out records
List categories of leave
g. Sales, Engineering). List organizational departments
List organization employees
List applicants for positions
List open job positions
List internal job requisitions
List employee leave history
List company offices
Why CrewAI?
When paired with CrewAI, WebHR becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call WebHR 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
WebHR in CrewAI
WebHR and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect WebHR 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 WebHR in CrewAI
The WebHR 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
WebHR for CrewAI
Every tool call from CrewAI to the WebHR MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
How do I find my WebHR API Key?
Log in to your WebHR portal, navigate to Setup > API Settings, and generate a new key for your integration.
Can the agent check employee leave balances?
Yes! Use the list_leaves tool to retrieve current leave applications and balance details for employees in your system.
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.