Bring Attendance Tracking
to Google ADK
Learn how to connect Lamha to Google ADK and start using 8 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the Lamha MCP Server?
Connect your Lamha account to any AI agent and manage HR operations through natural conversation.
What you can do
- Employee Management — List employees, inspect profiles, and track status
- Attendance Tracking — Monitor check-in/out times and attendance records
- Department Browsing — Navigate organizational structure and departments
- Leave Management — Track leave requests, balances, and approvals
- Payroll Access — View payroll data and compensation details
How it works
1. Subscribe to this server
2. Enter your Lamha API Token
3. Start managing HR from Claude, Cursor, or any MCP-compatible client
Who is this for?
- HR Teams — manage employee records and attendance
- Managers — track leave requests and team attendance
- Payroll — access compensation data and reports
Built-in capabilities (8)
Cancel an existing order
Check delivery coverage for a city
Create a new logistics order
Get details for a specific order
List delivery carriers
List product inventory
List Lamha orders
List warehouses
Why Google ADK?
Google ADK natively supports Lamha as an MCP tool provider. declare Vinkius Edge URL and the framework handles discovery, validation, and execution automatically. Combine 8 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 Lamha
- —
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 Lamha tools with BigQuery, Vertex AI, and Cloud Functions
Lamha in Google ADK
Lamha and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Lamha 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 Lamha in Google ADK
The Lamha 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 8 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
Lamha for Google ADK
Every tool call from Google ADK to the Lamha MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I track employee attendance and leave?
Yes. Monitor check-in/out records, view attendance summaries, and track leave balances, requests, and approvals for any employee.
How does Lamha authentication work?
Lamha uses a Token header (not Bearer) for authentication against app.lamha.sa/api/v2. This is a custom token format.
Can I browse the organizational structure?
Yes. Navigate departments, teams, and reporting hierarchies within the organization.
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