mite

mite-mcp-server

[CI] [npm] [License: MIT]

English · Deutsch

Ask Claude about your mite time tracking — "How many hours did we spend on each project per month this year, and what did that earn?" — and get the answer from a report mite computes itself, not from hundreds of entries the model has to add up.

[Demo: monthly report per project in a chat (invented data)]

Unofficial. Not affiliated with or endorsed by mite GmbH.

Why this server

• Ready-made reports. mite groups on the server (group_by), so a whole year is one request and one small answer.
• Safe by default. Starts read-only. Write tools only exist when you switch the mode on, and an allowlist narrows it further. Tools outside mode and allowlist are not even shown to the agent.
• Your key stays yours. API key from the environment only, sent as header, removed from every error message, never logged.

Tools

Deleting with a confirmation token

mite_delete_time_entry and the three master data delete tools never delete on the first call:

1. Call it with the id (or with dry_run: true). It returns a preview of the entry and a confirm_token; nothing is deleted.
2. Call it again with the same id and the confirm_token. Only then is it deleted.

The token is bound to the tool and its arguments, valid for 5 minutes, usable once, and only known to the running server process (a restart invalidates it).

If the MCP client supports elicitation, the second call (and any call with force: true and a token) additionally asks the human with a short summary of what will be deleted or forced. Only if the human accepts is anything executed. If they decline or cancel, nothing is sent to mite and the token stays unused until it expires. Clients without elicitation are not asked; the token alone applies.

Client support (checked 28.10.2026): Claude Desktop does not offer elicitation yet, so it shows no dialog; deleting there uses the token flow only. Once a client announces elicitation, the extra question applies without a new release of this server.

Locked entries

Locked time entries cannot be changed or deleted by default; mite answers with 423 and the tool returns a "locked" error. force is never set automatically, not even after a 423.

In mode admin only, mite_update_time_entry and mite_delete_time_entry additionally accept force: true. A call with force: true always needs a confirm_token, also on update: the first call (or dry_run: true) returns a preview stating that the entry is locked, plus a token; only a second call with the same arguments, force: true and the token executes. In modes read-only and write the parameter is not part of the input schema.

More tools (more reports) are planned — see the architecture decision.

Install without technical knowledge (Claude Desktop)

1. Download mite-mcp-server.mcpb from the latest release.
2. Double-click the file. Claude Desktop opens and offers to install the extension.
3. Fill in the settings and enable the extension:

[mite extension settings in Claude Desktop]

No JSON, no environment variables, no Node.js installation: Claude Desktop runs the bundle with its built-in Node.js. You need a mite account with API access enabled (in your mite user settings) and your API key from there. The settings are in German because mite's users mostly are.

Changing a setting later: Claude Desktop → Settings → Extensions → mite. A changed setting only takes effect after you switch the extension off and on again or restart Claude Desktop — until then the running server keeps the old switches. Ask Claude to call mite_whoami to see the mode the server is actually running in. In the same place you can also switch single tools on and off — on top of the switches above, which decide which tools exist at all.

Manual setup (Claude Desktop, for developers)

Requirements: Node.js 22 or newer, a mite account with API access enabled (enable it in your mite user settings), and your API key from there.

Add the server to claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/), then restart Claude Desktop:

{  "mcpServers": {    "mite": {      "command": "npx",      "args": ["-y", "mite-mcp-server"],      "env": {        "MITE_ACCOUNT": "your-account",        "MITE_API_KEY": "your-api-key"      }    }  }}

Then ask, for example: "Show me hours and revenue per project and month for this year."

Configuration

Use either MITE_MODE or the two switches; the server refuses MITE_MODE together with a switch set to true. Values true/false (also 1/0, yes/no, on/off).

mite still checks every call against the role of your key. The server can only restrict that, never extend it.

Development

npm cinpm run check   # lint, format, typecheck, tests with coverage, build

See CONTRIBUTING.md and the architecture decision.

License

MIT © Stefan Jacomeit — www.jacomeit.de