Bring Employee Directory
to Google ADK
Learn how to connect Hurma to Google ADK 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 Google ADK?
Google ADK natively supports Hurma as an MCP tool provider. declare Vinkius Edge URL and the framework handles discovery, validation, and execution automatically. Combine 12 tools with Gemini's long-context reasoning for complex multi-tool workflows, with production-ready session management and evaluation built in.
- —
Google ADK natively supports MCP tool servers. declare a tool provider and the framework handles discovery, validation, and execution
- —
Built on Gemini models, ADK provides long-context reasoning ideal for complex multi-tool workflows with Hurma
- —
Production-ready features like session management, evaluation, and deployment come built-in. not bolted on
- —
Seamless integration with Google Cloud services means you can combine Hurma tools with BigQuery, Vertex AI, and Cloud Functions
Hurma in Google ADK
Hurma and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Hurma to Google ADK 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 Google ADK
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 Google ADK 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 Google ADK
Every tool call from Google ADK 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.
How does Google ADK connect to MCP servers?
Import the MCP toolset class and pass the server URL. ADK discovers and registers all tools automatically, making them available to your agent's tool-use loop.
Can ADK agents use multiple MCP servers?
Yes. Declare multiple MCP tool providers in your agent configuration. ADK merges all tool schemas and the agent can call tools from any server in a single turn.
Which Gemini models work best with MCP tools?
Gemini 2.0 Flash and Pro models both support function calling required for MCP tools. Flash is recommended for latency-sensitive use cases, Pro for complex reasoning.
McpToolset not found
Update: pip install --upgrade google-adk