Skip to main content
Glama
Chronova MCP Server

Chronova MCP Server

Related Servers

Alternatives to Chronova MCP Server

  • 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
  • A
    license
    A
    quality
    D
    maintenance
    Exposes WakaTime Summaries API tools over stdio, enabling daily and today's coding activity summaries via MCP.
    10
    MIT

Related Servers

  • A
    license
    Not graded
    quality
    A
    maintenance
    AI-native developer observability MCP (Model Context Protocol) server that gives AI agents full-stack visibility into your development environment — browser, terminal, and processes — all in one unified interface.
    1
    MIT
  • A
    license
    Not graded
    quality
    D
    maintenance
    A Model Context Protocol server that connects your AI IDE to Jira. Query your tickets, active sprint, and issue details directly from GitHub Copilot, Cursor, Claude Desktop, or any MCP-compatible client.
    ISC
  • A
    license
    Not graded
    quality
    D
    maintenance
    A comprehensive Model Context Protocol (MCP) server that integrates with the Cronlytic API to provide seamless cron job management through LLM applications like Claude Desktop.
    1
    MIT
  • A
    license
    A
    quality
    A
    maintenance
    A Model Context Protocol (MCP) server that fetches sleep, HRV, and training data from the unofficial Coros API and exposes them to AI assistants like Claude, enabling natural language queries about fitness metrics and workout management.
    26
    126
    MIT

TDQS

A4.2/5.0

Scored across 4 tools

Disambiguation5/5

Each tool targets a distinct area: AI insights, developer profile, productivity aggregates, and raw activity events. The descriptions clearly differentiate the data returned, leaving no ambiguity about which tool to select.

Naming Consistency5/5

All tool names follow a consistent get_<object> pattern with clear snake_case naming. The verbs and nouns are uniform, making the API predictable and easy to navigate.

Tool Count5/5

With only 4 tools, the server is tightly scoped to read-only coding analytics. Each tool covers a distinct and necessary data view without unnecessary bloat or redundancy.

Completeness4/5

The set covers the major analytics surfaces: AI insights, user context, productivity summaries, and raw activity logs. Minor gaps like team-level analytics or detailed project history could exist, but core personal coding analytics needs are well served.

Maintenance

ActivityActive
ResponsivenessLimited data