Bring Time Tracking
to CrewAI
Learn how to connect DeskTime to CrewAI 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 DeskTime MCP Server?
Connect your DeskTime account to any AI agent and take full control of your workforce management and productivity tracking workflows through natural conversation.
What you can do
- Project & Task Orchestration — List and manage time-tracking projects and individual tasks programmatically to maintain a high-fidelity record of work distribution
- Team Visibility — Monitor real-time staff activity, including who is currently online and tracking time, to coordinate team availability and throughput
- Productivity Intelligence — Access comprehensive productivity reports and performance metrics for individual employees or the entire company directly through your agent
- Workflow Automation — Programmatically create new projects, assign tasks, and mark work as completed to streamline your project management cycle
- Administrative Oversight — Retrieve detailed company metadata and employee directories to maintain a perfectly coordinated workforce ecosystem
How it works
1. Subscribe to this server
2. Retrieve your API Key from your DeskTime settings (Settings > Integrations)
3. Start managing your team's productivity from Claude, Cursor, or any MCP client
No more manual logging or digging through productivity charts in the dashboard. Your AI acts as your dedicated workforce operations and time-tracking coordinator.
Who is this for?
- Project Managers — instantly retrieve task completion reports and update project statuses using natural language commands
- Team Leads — monitor real-time availability and productivity scores without leaving your communication tools
- HR & Ops Leads — automate employee data retrieval and monitor company-wide time utilization through simple AI queries
Built-in capabilities (12)
Add task to project
Add new project
Get company details
Check employee stats
Check company performance
Get project info
List company employees
Check who is working
List tasks in project
List DeskTime projects
Complete a task
Delete a project
Why CrewAI?
When paired with CrewAI, DeskTime becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call DeskTime tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.
- —
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
mcpsparameter 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
DeskTime in CrewAI
DeskTime and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect DeskTime to CrewAI 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 DeskTime in CrewAI
The DeskTime 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 CrewAI 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
DeskTime for CrewAI
Every tool call from CrewAI to the DeskTime MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
How do I find my DeskTime API Key?
Log in to your account, navigate to Settings > Integrations, and you will find your API Key at the bottom of the page.
Can I see who is currently online?
Yes! Use the list_online_staff tool to retrieve a real-time list of employees who are actively tracking their time.
Does it support detailed performance metrics?
The get_employee_performance tool provides granular productivity scores and time breakdown for specific dates.
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.
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.