WebHR MCP Server for CursorGive Cursor instant access to 11 tools to Get Attendance Summary, Get Employee Details, List Attendance Logs, and more
Cursor is an AI-first code editor built on VS Code that integrates LLM-powered coding assistance directly into the development workflow. Its Agent mode enables autonomous multi-step coding tasks, and MCP support lets agents access external data sources and APIs during code generation.
Ask AI about this App Connector for Cursor
The WebHR app connector for Cursor is a standout in the Industry Titans category — giving your AI agent 11 tools to work with, ready to go from day one.
Vinkius delivers Streamable HTTP and SSE to any MCP client
Vinkius Desktop App
The modern way to manage MCP Servers — no config files, no terminal commands. Install WebHR and 3,400+ MCP Servers from a single visual interface.
{
"mcpServers": {
"webhr": {
"url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
}
}
}
* 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
About 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.
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.
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.
The WebHR MCP Server exposes 11 tools through the Vinkius. Connect it to Cursor in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.
All 11 WebHR tools available for Cursor
When Cursor connects to WebHR through Vinkius, your AI agent gets direct access to every tool listed below — spanning employee-management, attendance-tracking, recruitment, and more. Every call is secured with network, filesystem, subprocess, and code evaluation entitlements inside a sandboxed runtime. Beyond a simple connection, you get a full AI Gateway with real-time visibility into agent activity, enterprise governance, and optimized token usage.
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
Connect WebHR to Cursor via MCP
Follow these steps to wire WebHR into Cursor. The entire setup takes under two minutes — your credentials stay safe behind the Vinkius.
Open MCP Settings
Cmd+Shift+P (macOS) or Ctrl+Shift+P (Windows/Linux) → search "MCP Settings"Add the server config
mcp.json file that opensSave the file
Start using WebHR
Why Use Cursor with the WebHR MCP Server
Cursor AI Code Editor provides unique advantages when paired with WebHR through the Model Context Protocol.
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 + Cursor Use Cases
Practical scenarios where Cursor combined with the WebHR MCP Server delivers measurable value.
Code generation with live data: ask Cursor to generate a security report module using live DNS and subdomain data fetched through MCP
Automated documentation: have Cursor query your API's tool schemas and generate TypeScript interfaces or OpenAPI specs automatically
Infrastructure-as-code: Cursor can fetch domain configurations and generate corresponding Terraform or CloudFormation templates
Test scaffolding: ask Cursor to pull real API responses via MCP and generate unit test fixtures from actual data
Example Prompts for WebHR in Cursor
Ready-to-use prompts you can give your Cursor agent to start working with WebHR immediately.
"Check the status of our open 'Senior Frontend Engineer' job posting and list all the active candidates currently in the pipeline."
"Retrieve all pending leave requests for the Engineering department and check the available vacation balance for 'Marcus Johnson'."
"Generate an attendance summary for the New York office to see how many employees clocked in late this week."
Troubleshooting WebHR MCP Server with Cursor
Common issues when connecting WebHR to Cursor through the Vinkius, and how to resolve them.
Tools not appearing in Cursor
Server shows as disconnected
WebHR + Cursor FAQ
Common questions about integrating WebHR MCP Server with Cursor.
What is Agent mode and why does it matter for MCP?
Where does Cursor store MCP configuration?
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.