Bring Attendance Tracking
to Windsurf
Learn how to connect Lamha to Windsurf 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 Windsurf?
Windsurf's Cascade agent chains multiple Lamha tool calls autonomously. query data, analyze results, and generate code in a single agentic session. Paste Vinkius Edge URL, reload, and all 8 tools are immediately available. Real-time tool feedback appears inline, so you see API responses directly in your editor.
- —
Windsurf's Cascade agent autonomously chains multiple tool calls in sequence, solving complex multi-step tasks without manual intervention
- —
Purpose-built for agentic workflows. Cascade understands context across your entire codebase and integrates MCP tools natively
- —
JSON-based configuration means zero code changes: paste a URL, reload, and all 8 tools are immediately available
- —
Real-time tool feedback is displayed inline, so you see API responses directly in your editor without switching contexts
Lamha in Windsurf
Lamha and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Lamha to Windsurf 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 Windsurf
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 Windsurf 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 Windsurf
Every tool call from Windsurf 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 Windsurf discover MCP tools?
Windsurf reads the mcp_config.json file on startup and connects to each configured server via Streamable HTTP. Tools are listed in the MCP panel and available to Cascade automatically.
Can Cascade chain multiple MCP tool calls?
Yes. Cascade is an agentic system. it can plan and execute multi-step workflows, calling several tools in sequence to accomplish complex tasks without manual prompting between steps.
Does Windsurf support multiple MCP servers?
Yes. Add as many servers as needed in mcp_config.json. Each server's tools appear in the MCP panel and Cascade can use tools from different servers in a single flow.
Server not connecting
Check Settings → MCP for the server status. Try toggling it off and on.