Skip to main content
Glama
efirvida

wakatime-mcp

by efirvida
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to wakatime-mcp

No user-submitted related servers found.

    Related Servers

    • WakaTime MCP Server

      dpshde
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides access to WakaTime coding analytics data through MCP tools. Enables querying coding stats, activity summaries, project lists, and time tracking information from your WakaTime account.
      MIT

    • ATimeLogger MCP Server

      Mrquj
      A
      license
      A
      quality
      B
      maintenance
      A standalone MCP server that exposes the ATimeLogger REST API to Claude Desktop/Code over stdio, enabling activity tracking (start/stop/pause/log), reports/history, and activity type management.
      8
      34 npm
      1
      MIT
    • openrhyme-mcp by OpenRhyme

      openrhyme-mcpofficial

      OpenRhyme
      A
      license
      A
      quality
      B
      maintenance
      Enables any MCP-compatible agent to query a local OpenRhyme activity timeline, search history, and issue control commands over stdio while keeping all data on-machine.
      5
      MIT

    • moltline-mcp

      GarphenGate
      A
      license
      A
      quality
      A
      maintenance
      Zero-dependency stdio bridge to Moltline Studio's fleet of 14 hosted MCP servers covering code review, time operations, data transforms, business ops, education, research, outreach and more. Free tier requires no registration; premium tools unlock with a license. Independently audited, MCPize Verified A.
      2
      10
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.5/5.0

    Scored across 10 tools

    Disambiguation3/5

    Several tools (today, summaries, durations, heartbeats, stats) all return time-tracking data with overlapping periods and granularities, making selection potentially confusing. Descriptions clarify differences, but the boundaries between raw summaries, processed durations, and aggregated stats are not always obvious.

    Naming Consistency4/5

    All tools share the wakatime_ prefix and use snake_case, creating a clear family identity. However, the semantic structure varies (e.g., wakatime_today is adverbial, wakatime_summaries is a plural noun, wakatime_mark_consumed is verb-object), so the pattern is consistent in style but not in syntactic form.

    Tool Count5/5

    10 tools is a well-scoped number for a WakaTime integration, covering user info, projects, multiple time-reporting views, and a session-tracking workflow with mark_consumed. Each tool has a distinct role, and the count fits comfortably in the ideal 3-15 range.

    Completeness4/5

    The tool set covers the major WakaTime API areas: user validation, project listing, summaries, durations, heartbeats, stats, and all-time totals. The session_duration/mark_consumed pair adds a practical workflow. Missing advanced endpoints like goals or leaderboards are non-core, so the surface is nearly complete.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources