4,000+ servers built on vurb.ts
Vinkius
CrewAIFramework
WakaTime (Coding Stats) MCP Server

Bring Coding Stats
to CrewAI

Learn how to connect WakaTime (Coding Stats) to CrewAI and start using 14 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.

MCP Inspector GDPR Free for Subscribers
Create External DurationCreate HeartbeatGet All Time Since TodayGet GoalGet StatsList CommitsList Custom RulesList DurationsList External DurationsList GoalsList HeartbeatsList ProjectsList SummariesUpdate Custom Rules

Compatible with every major AI agent and IDE

ClaudeClaude
ChatGPTChatGPT
CursorCursor
GeminiGemini
WindsurfWindsurf
VS CodeVS Code
JetBrainsJetBrains
VercelVercel
+ other MCP clients
WakaTime (Coding Stats)

What is the WakaTime (Coding Stats) MCP Server?

Connect your WakaTime account to any AI agent to analyze your coding habits, track project progress, and monitor productivity goals through natural conversation.

What you can do

  • Coding Statistics — Get summarized stats for specific ranges (7 days, 30 days, etc.) or your all-time total coding time.
  • Project Tracking — List all projects detected by your IDE plugins and see daily summaries of activity per project.
  • Goal Monitoring — Check your progress on custom coding goals and retrieve specific details for individual targets.
  • Activity Analysis — Inspect raw heartbeats and duration blocks to understand exactly when and how you are working.

How it works

  1. Subscribe to this server
  2. Enter your WakaTime API Key
  3. Start querying your coding data from Claude, Cursor, or any MCP-compatible client

Who is this for?

  • Developers — track your own productivity and see which projects consume most of your time.
  • Team Leads — monitor high-level project activity and goal progress without manual reporting.
  • Data Enthusiasts — analyze coding patterns and heartbeats to optimize your workflow.

Built-in capabilities (14)

create_external_duration

Create activity from an external app

create_heartbeat

Create a raw coding activity ping

get_all_time_since_today

Get total time logged since account creation

get_goal

Get a specific user-defined coding goal

get_stats

Get summarized coding statistics for a given range

list_commits

List of commits for a project with time spent on each

list_custom_rules

Get rules to modify or delete coding activity based on patterns

list_durations

Get coding activity joined into blocks based on keystroke timeout

list_external_durations

g., Google Calendar). Get activity created from external apps

list_goals

List user-defined coding goals and their progress

list_heartbeats

Get raw coding activity pings from IDE plugins

list_projects

List of projects detected for the user

list_summaries

Get daily totals of coding activity

update_custom_rules

Update rules to modify or delete coding activity

Why CrewAI?

When paired with CrewAI, WakaTime (Coding Stats) becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call WakaTime (Coding Stats) 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 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

See it in action

WakaTime (Coding Stats) in CrewAI

AI AgentVinkius
High Security·Kill Switch·Plug and Play
Why Vinkius

WakaTime (Coding Stats) and 4,000+ other MCP servers. One platform. One governance layer.

Teams that connect WakaTime (Coding Stats) 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.

4,000+MCP Servers ready
<40msCold start
60%Token savings
Raw MCP
Vinkius
Server catalogFind and host yourself4,000+ managed
InfrastructureSelf-hostedSandboxed V8 isolates
Credential handlingPlaintext in configVault + runtime injection
Data loss preventionNoneConfigurable DLP policies
Kill switchNoneGlobal instant shutdown
Financial circuit breakersNonePer-server limits + alerts
Audit trailNoneEd25519 signed logs
SIEM log streamingNoneSplunk, Datadog, Webhook
HoneytokensNoneCanary alerts on leak
Custom domainsNot applicableDNS challenge verified
GDPR complianceManual effortAutomated purge + export
Enterprise Security

Why teams choose Vinkius for WakaTime (Coding Stats) in CrewAI

The WakaTime (Coding Stats) 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 14 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.

WakaTime (Coding Stats)
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

The Vinkius Advantage

How Vinkius secures WakaTime (Coding Stats) for CrewAI

Every tool call from CrewAI to the WakaTime (Coding Stats) MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.

< 40msCold start
Ed25519Signed audit chain
60%Token savings
FAQ

Frequently asked questions

01

Can I get a summary of my coding activity for the last week?

Yes! Use the get_stats tool with the range 'last_7_days'. Your agent will return aggregated data including total time, languages used, and project breakdown.

02

How do I check my progress on my coding goals?

Run the list_goals tool to see all your active goals and their current completion percentage. You can also use get_goal with a specific ID for deeper details.

03

Can I see which projects I've been working on?

Yes, the list_projects tool will return a list of all projects detected by your WakaTime plugins. You can then use list_summaries to see time spent on them.

04

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.

05

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.

06

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.

07

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.

08

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.

09

MCP tools not discovered

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

10

Agent not using tools

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

11

Timeout errors

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

12

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 →