Timebook

What is Timebook?

Timebook is a time tracking, invoicing, and lightweight bookkeeping tool built for solo LLCs and freelancers. It ships with an MCP server so AI agents (Claude Code, Cursor, Claude.ai, or any MCP-speaking client) can manage your time directly from your workflow.

How to use Timebook?

Install via stdio by adding a JSON config to your MCP client and running npx @squidcode/timebook login once to authenticate. For remote use (e.g., Claude.ai web), add the endpoint https://usetimebook.com/mcp as a connector; OAuth 2.0 handles authorization with a consent screen.

Key features of Timebook

• Start and stop timers on any project
• Log a discrete time entry with a duration
• List clients, projects, and active timers
• Query recent entries with filters
• Inspect, update, or delete a specific entry

Use cases of Timebook

• Freelancer asks an AI agent to log 45 minutes on a client project
• Solo LLC owner starts a timer from within an IDE without opening a browser tab
• Agent automatically records time based on task context and wraps up when done
• User queries all recent entries to review billable hours for the week

FAQ from Timebook

How does Timebook differ from traditional time trackers?

Existing trackers assume a human flipping a switch in a browser tab. Timebook flips it around: your AI logs the time, so you stay in flow.

What transports does the MCP server support?

Stdio for desktop clients (Claude Desktop, Cursor, Claude Code, Continue) and Streamable-HTTP with full OAuth 2.0 for remote use like Claude.ai web.

Where is the authentication token stored?

After running the login command, a scoped token is written to a local config file with mode 0600. No token paste is required.

What runtime or dependencies are needed?

The server runs via npx (Node.js) for stdio mode. No other external dependencies are mentioned.

Who is Timebook built for?

Solo LLCs and freelancers. One price with no tiers, no per-seat fees, and no upsells.