mcpbeat Sign in

Cronometer MCP Server

local only

Cronometer runs on your own machine — the client starts it, so there is no endpoint to ping. 684 installs a week from npm. Last commit 18 Oct 2026.

Your Cronometer diary, nutrition with honest coverage (missing is never zero), and safe writes.

Installs per day peak 680 · avg 22
a month agotoday
684
Installs / week
npm · @ekelly95/cronometer-mcp
0
Stars
0 open issues
18 Oct 2026
Last commit
4 releases in 90 days
MIT
License
TypeScript

What the code does

We read the source, 4 d ago · rules 995398eba69f

Capabilities

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

  const result = spawnSync(command, args, {

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

This code can reach further than it looks

We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.

Three servers free · no card

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

run in your terminal
claude mcp add cronometer-mcp -- npx -y @ekelly95/cronometer-mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "cronometer-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@ekelly95/cronometer-mcp"
      ]
    }
  }
}
~/.codex/config.toml
[mcp_servers.cronometer-mcp]
command = "npx"
args = ["-y", "@ekelly95/cronometer-mcp"]
.cursor/mcp.json
{
  "mcpServers": {
    "cronometer-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@ekelly95/cronometer-mcp"
      ]
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "cronometer-mcp": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@ekelly95/cronometer-mcp"
      ]
    }
  }
}

Optional settings from the registry entry, left out of the block above: CRONOMETER_USERNAME (Cronometer account email. Optional if `npx @ekelly95/cronometer-mcp setup` saved it), CRONOMETER_PASSWORD (Cronometer password. Optional if setup saved it to the OS keyring), CRONOMETER_LIVE_ENABLED (Set to 1 to accept the risks of unofficial access when using environment credentials), CRONOMETER_TOTP_SECRET (Base32 authenticator key, for accounts with two-factor sign-in), CRONOMETER_TIMEZONE (Diary timezone, e.g. America/New_York. Defaults to the saved setup, else this computer's), CRONOMETER_READ_ONLY (Set to 1 to offer no tool that can change the account).

Alternatives to Cronometer

same job, measured the same way
Vinv
by vinvai

Vinv runs, tests, and finds issues in your services — with zero code changes.

18 installs/wk local only
DVERA CT verification tools
by suresofttechnologies

DVERA drives CT verification of mission-critical C/C++: setup, analysis, tests, coverage.

local only
Conning
by eranyonai

Run commands on your remote test machines over SSH without the agent ever seeing a secret.

1 325 installs/wk local only
RewindMap
by rewindmap

Historical borders and dated map events with source attribution and coverage limits.

4 tools answering
Mida
by mida

Create, run and analyze A/B tests and personalizations on your site with Mida.

answering
RxRooster
by rxrooster

Six privacy-safe tools for anesthesia discovery, drafts, coverage, and recruiting packets.

6 tools answering
Test Intel
by barissozudogru

Coverage analysis, untested function detection and complexity scoring for TS and JS.

10 installs/wk local only
Directory Submission Retention Proof
by textforagents

Pre-submission escrow receipts and coverage-aware retention diffs.

5 tools answering

Cronometer — questions

Answers built from our own checks of this server.

Why is there no uptime for Cronometer?
Cronometer runs on your own machine over stdio — there is no network address to reach, so uptime cannot be measured for it by anyone. What can be measured is adoption: the npm package @ekelly95/cronometer-mcp was installed 684 times last week.
How do I connect Cronometer?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It runs locally, so the command pulls @ekelly95/cronometer-mcp straight from npm; nothing to host, nothing to sign up for.
How many people use Cronometer?
The npm package @ekelly95/cronometer-mcp was installed 684 times in the last week. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.
Is Cronometer open source?
Yes — it is published under the MIT licence, written in TypeScript and 0 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.