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.

INSTANT PLUG AND PLAY

Lamha MCP Server for CrewAIGive CrewAI instant access to 8 tools to Cancel Order, Check City Coverage, Create Order, and more

Name: Lamha
Availability: InStock
Author: Vinkius

Built by Vinkius GDPR 8 Tools Framework

Connect your CrewAI agents to Lamha through Vinkius, pass the Edge URL in the `mcps` parameter and every Lamha tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

Use with Your AI Agent

Ask AI about this App Connector for CrewAI

Open in ChatGPT Open in Claude Open in Perplexity

The Lamha app connector for CrewAI is a standout in the Productivity category — giving your AI agent 8 tools to work with, ready to go from day one.

Vinkius delivers Streamable HTTP and SSE to any MCP client

python

from crewai import Agent, Task, Crew

agent = Agent(
    role="Lamha Specialist",
    goal="Help users interact with Lamha effectively",
    backstory=(
        "You are an expert at leveraging Lamha tools "
        "for automation and data analysis."
    ),
    # Your Vinkius token. get it at cloud.vinkius.com
    mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)

task = Task(
    description=(
        "Explore all available tools in Lamha "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 8 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* 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 Lamha MCP Server

Connect your Lamha account to any AI agent and manage HR operations through natural conversation.

When paired with CrewAI, Lamha becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Lamha tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.

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

The Lamha MCP Server exposes 8 tools through the Vinkius. Connect it to CrewAI in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

All 8 Lamha tools available for CrewAI

When CrewAI connects to Lamha through Vinkius, your AI agent gets direct access to every tool listed below — spanning attendance-tracking, leave-management, payroll-management, 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.

cancel_order

Cancel an existing order

check_city_coverage

Check delivery coverage for a city

create_order

Create a new logistics order

get_order

Get details for a specific order

list_carriers

List delivery carriers

list_inventory

List product inventory

list_orders

List Lamha orders

list_warehouses

List warehouses

Connect Lamha to CrewAI via MCP

Follow these steps to wire Lamha into CrewAI. The entire setup takes under two minutes — your credentials stay safe behind the Vinkius.

Install CrewAI

Run pip install crewai

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com

Customize the agent

Adjust the role, goal, and backstory to fit your use case

Run the crew

Run python crew.py. CrewAI auto-discovers 8 tools from Lamha

Why Use CrewAI with the Lamha MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with Lamha through the Model Context Protocol.

Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools

CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the `mcps` parameter and agents auto-discover every available tool at runtime

Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls

Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

Lamha + CrewAI Use Cases

Practical scenarios where CrewAI combined with the Lamha MCP Server delivers measurable value.

Automated multi-step research: a reconnaissance agent queries Lamha for raw data, then a second analyst agent cross-references findings and flags anomalies. all without human handoff

Scheduled intelligence reports: set up a crew that periodically queries Lamha, analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain Lamha tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

Compliance and audit automation: a compliance agent queries Lamha against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

Example Prompts for Lamha in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with Lamha immediately.

"Show all departments and today's attendance."

"Show pending leave requests and employee leave balances."

"Show payroll summary and employee details for the Engineering team."

Troubleshooting Lamha MCP Server with CrewAI

Common issues when connecting Lamha to CrewAI through the Vinkius, and how to resolve them.

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.

Rate limiting or 429 errors

Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

Lamha + CrewAI FAQ

Common questions about integrating Lamha MCP Server with CrewAI.

How does CrewAI discover and connect to MCP tools?

CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.

Can different agents in the same crew use different MCP servers?

Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.

What happens when an MCP tool call fails during a crew run?

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.

Can CrewAI agents call multiple MCP tools in parallel?

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.

Can I run CrewAI crews on a schedule (cron)?

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.