Bring Employee Management
to Cursor
Learn how to connect WebHR to Cursor 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 Cursor?
Cursor's Agent mode turns WebHR into an in-editor superpower. Ask Cursor to generate code using live data from WebHR and it fetches, processes, and writes. all in a single agentic loop. 11 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.
- —
Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context
- —
Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards
- —
MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment
- —
VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools
WebHR in Cursor
WebHR and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect WebHR to Cursor 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 Cursor
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 Cursor 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 Cursor
Every tool call from Cursor 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.
What is Agent mode and why does it matter for MCP?
Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.
Where does Cursor store MCP configuration?
Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.
Can Cursor use MCP tools in inline edits?
No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.
How do I verify MCP tools are loaded?
Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.
Tools not appearing in Cursor
Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.
Server shows as disconnected
Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.