Your time tracker, in the conversation.

Connect a supported client

TickRiver detects user configuration folders for Codex, Claude Code, Claude Desktop, Kiro, and Grok Build. On first setup it adds a missing TickRiver server to detected configurations and backs up changed configuration files.

1. Install your AI client and run it once so its configuration folder exists.
2. Launch TickRiver from its Windows shortcut.
3. Choose AI connections in TickRiver to check or retry setup.
4. Reconnect or restart the AI client. Claude Desktop requires a full quit and restart.

Disabled servers and customized commands or settings are preserved. Organization policies and project-specific client settings still apply.

The MCP server uses the same local database as the desktop app and can run while the TickRiver window is closed. TickRiver does not provide an AI model itself; your AI client's account, permissions, and any provider charges still apply.

Things you can ask

These examples assume you have created the named clients and projects.

• “What were my hours last week?”
• “Show my unbilled hours for Acme between July 1 and September 30.”
• “Start the timer for Website maintenance, working on the checkout page.”
• “Stop my timer.”
• “Add 09:00 to 10:30 on September 15 to Website maintenance.”
• “Change entry 2's description to Client correspondence.”

The client can list clients, projects, and entries; report completed hours; control timers; and add or edit completed entries. Ambiguous project names require a choice. Overlapping entries are rejected, and stale edits fail instead of overwriting newer changes.

The desktop app refreshes after changes made through MCP. An active timer is reported separately from completed-hour totals.

Data and privacy

Time records are stored locally in %LOCALAPPDATA%\TickRiver\tickriver.sqlite. TickRiver does not require an online account or a cloud time-tracking service.

When you request information through an AI client, the requested records, including relevant client names, project names, descriptions, hours, and billing data, are returned to that client and may be processed by its AI provider. Choose a client and provider appropriate for the data you track.

The bundled MCP server communicates locally over standard input and output. It does not expose a network endpoint. Reporting tools read the database; timer and entry tools can change it when invoked. Your client's tool-permission policies govern access.

See the company's privacy policy for website and support information.

If the connection is missing or outdated

• Run AI connections again after installing a new client.
• Fully quit and reopen Claude Desktop; reconnect or restart other clients as needed.
• After a TickRiver update, reconnect the AI client so it starts the new server executable.
• Check the status shown by TickRiver. A customized or disabled server is left under your control.
• If you deliberately removed the server, AI connections can retry adding it.

For other MCP clients, use the installed TickRiver.Mcp.exe as a local stdio server and pass --database followed by the absolute path to your TickRiver database. Keep the installed executable with its complete runtime and dependencies.

Need help? Contact support with the connection status and your AI client's name.