Chronova MCP Server
Retrieves developer context including GitHub status and organization memberships via Chronova.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Chronova MCP Serverget my productivity summary for last 7 days"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Chronova MCP Server
MCP server that exposes Chronova developer productivity data to AI agents. Built on the Model Context Protocol, it lets tools like Claude Desktop, Cursor, and OpenCode query your coding stats, activity, and AI-assisted coding metrics.
Installation
# Run directly (stdio transport for MCP clients)
npx -y @chronova/mcp-server
# Or install globally
npm install -g @chronova/mcp-server
chronova-mcp-serverConfiguration
The server resolves your API key from multiple sources in priority order:
Environment variable
CHRONOVA_API_KEYConfig file
~/.chronova.cfg—api_keyunder[settings]Config file
~/.wakatime.cfg—api_keyunder[settings](WakaTime-compatible)Default: empty (requests will fail with 401)
Similarly, api_url is resolved from CHRONOVA_API_URL env var, then the config file's api_url key, then the default https://chronova.dev.
Config files use INI format:
[settings]
api_key = waka_your-api-key-here
api_url = https://chronova.dev/api/v1Variable | Required | Default | Description |
| Yes* | — | Your Chronova API key (*or set in config file) |
| No |
| Chronova API base URL |
| No |
| Server listen port |
CLI flags override env vars: --port 3001, --api-url https://chronova.dev, --help.
Usage with AI Clients
Claude Desktop
Add to claude_desktop_config.json:
{
"mcpServers": {
"chronova": {
"command": "npx",
"args": ["-y", "@chronova/mcp-server"],
"env": {
"CHRONOVA_API_KEY": "your-api-key"
}
}
}
}Cursor
Add to .cursor/mcp.json:
{
"mcpServers": {
"chronova": {
"command": "npx",
"args": ["-y", "@chronova/mcp-server"],
"env": {
"CHRONOVA_API_KEY": "your-api-key"
}
}
}
}OpenCode
Add to opencode.json under mcp:
{
"mcp": {
"chronova": {
"type": "local",
"command": ["npx", "-y", "@chronova/mcp-server"],
"enabled": true,
"env": {
"CHRONOVA_API_KEY": "your-api-key"
}
}
}
}Tools
Tool | Description | Parameters |
| Get user profile, subscription, GitHub status, org memberships | None |
| Aggregated coding stats by time range |
|
| AI vs manual coding analytics |
|
| Recent coding heartbeats with filters and pagination |
|
Named ranges: today, last_7_days, last_30_days, last_3_months, last_6_months, last_year, all_time. Custom: YYYY-MM-DD_to_YYYY-MM-DD.
Development
npm run dev # Watch mode
npm test # Run tests
npm run build # Compile TypeScript
npm run type-check # Type check onlyDocker
docker build -t chronova-mcp .
docker run -e CHRONOVA_API_KEY=your-key -p 3001:3001 chronova-mcpLicense
Proprietary
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/nx-solutions-ug/chronova-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server