Bring Employee Directory
to Cursor
Learn how to connect Hurma to Cursor and start using 12 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the Hurma MCP Server?
Connect your Hurma instance to any AI agent and manage your HR operations through natural conversation.
What you can do
- Recruiting Pipeline — List all candidates, inspect profiles, create new candidate records, and track hiring progress
- Employee Directory — Browse all employees with department and position details
- Time-Off Management — Monitor out-of-office schedules and leave requests
- Department Structure — Browse organizational departments
- Position Management — List all job positions
- Onboarding Tracking — Monitor new hire checklists and progress
How it works
1. Subscribe to this server
2. Enter your Hurma domain name and API Key
3. Start managing HR from Claude, Cursor, or any MCP-compatible client
Who is this for?
- HR Teams — manage candidates, employees, and leave without switching to the dashboard
- Hiring Managers — track recruiting pipeline and review candidate profiles
- Team Leads — monitor team availability and time-off schedules
Built-in capabilities (12)
Create a new candidate
Create a new leave or absence request
Export overtime data
Get details for a specific candidate
Get details for a specific employee
Get employee vacation balance
List recruitment candidates
List custom field definitions
List all company departments
List all employees
List employees currently out of office
List recruitment stages
Why Cursor?
Cursor's Agent mode turns Hurma into an in-editor superpower. Ask Cursor to generate code using live data from Hurma and it fetches, processes, and writes. all in a single agentic loop. 12 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
Hurma in Cursor
Hurma and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Hurma 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 Hurma in Cursor
The Hurma 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 12 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
Hurma for Cursor
Every tool call from Cursor to the Hurma MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I manage the recruiting pipeline through the AI agent?
Yes. Use list_candidates to see all candidates with status, get_candidate_details for full profiles, and create_candidate to add new applicants.
Can I monitor who is out of office today?
Yes. list_out_of_office retrieves all current and upcoming time-off entries. Use list_leave_requests for pending approvals and get_leave_balances for remaining vacation days.
Does Hurma require a custom domain in addition to the API Key?
Yes. Each Hurma account has a unique subdomain. Provide the domain name and API Key. Requests go to https://{domain}.hurma.work/api/v1 with a Bearer token.
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.