Compatible with every major AI agent and IDE
What is the Wakapi (WakaTime Alternative) MCP Server?
Connect your Wakapi instance to any AI agent to monitor your development workflow through natural conversation. Wakapi is a self-hosted, open-source alternative to WakaTime that tracks your coding activity across different editors and languages.
What you can do
- Coding Statistics — Retrieve detailed stats including languages, editors, and operating systems used over various time ranges using
get_stats. - Activity Summaries — Fetch granular summaries of your work for specific date ranges or individual projects with
get_summaries. - Project Listing — View all projects you have tracked time for using
list_projectsto keep your portfolio or billable hours organized. - Heartbeat Tracking — Manually send coding activity heartbeats via
send_heartbeatsto ensure your timeline is always accurate.
How it works
- Subscribe to this server
- Enter your Wakapi API URL and API Key
- Start analyzing your coding habits from Claude, Cursor, or any MCP-compatible client
Who is this for?
- Individual Developers — track your own productivity and see which languages you spend the most time on.
- Engineering Managers — get high-level summaries of team activity and project distribution.
- Freelancers — accurately report time spent on specific client projects without manual timers.
Built-in capabilities (4)
Retrieve coding statistics for a user
Retrieve a detailed summary of activity
List all projects tracked by the user
Provide a heartbeat object or an array of heartbeat objects. Send coding activity heartbeats to Wakapi
Why CrewAI?
When paired with CrewAI, Wakapi (WakaTime Alternative) becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Wakapi (WakaTime Alternative) 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
Wakapi (WakaTime Alternative) in CrewAI
Wakapi (WakaTime Alternative) and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Wakapi (WakaTime Alternative) 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 | 4,000+ 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 Wakapi (WakaTime Alternative) in CrewAI
The Wakapi (WakaTime Alternative) 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 4 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
Wakapi (WakaTime Alternative) for CrewAI
Every tool call from CrewAI to the Wakapi (WakaTime Alternative) MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
How can I see my coding statistics for the last 7 days?
You can use the get_stats tool and specify 'last_7_days' as the range. The agent will return a breakdown of your languages, editors, and projects for that period.
Can I get a list of all projects I have ever tracked in Wakapi?
Yes! Use the list_projects tool. It will retrieve all project names associated with your account, allowing you to see the scope of your tracked work.
Is it possible to track activity for a specific date range?
Absolutely. Use the get_summaries tool by providing a 'start' and 'end' date in YYYY-MM-DD format. You can even filter this by a specific project name.
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.
Explore More MCP Servers
View all →
Mio
12 toolsBridge conversations between Slack, Microsoft Teams, and Webex so teams on different platforms can collaborate without switching apps.

Cartesia (Voice AI)
20 toolsGenerate lifelike AI voices, clone speech, and transcribe audio with Cartesia's state-of-the-art Sonic models directly from your AI agent.

n8n (AI Workflow Automation)
7 toolsManage workflow automation via n8n — audit active workflows, track execution logs, and monitor credentials.

Cypress Cloud
10 toolsAudit E2E testing via Cypress — monitor test runs, inspect spec instances, track flaky tests, and generate enterprise reports directly from any AI agent.
