Qb Time MCP Server

Qb Time MCP server exists for a simple reason — assistants are far more useful when they can act on Qb Time directly instead of describing what you should do. This is a combined MCP server that provides access to all QuickBooks Time API functionality through a single interface. It combines the functionality of four separate servers:.

What the assistant can call

Once Qb Time is connected, these are the calls the assistant has available:

• get_jobcodes — Get jobcodes with advanced filtering options
• ids — (array of numbers, optional) Comma separated list of jobcode IDs
• name — (string, optional) Filter by jobcode name, supports wildcard (*) matching from string start
• active — (string, optional) Filter by status: "yes", "no", "both" (default: "yes")
• type — (string, optional) Filter by type: "regular", "pto", "paid_break", "unpaid_break", "all" (default: "regular")
• parent_ids — (array of numbers, optional) Filter by parent jobcode IDs. Special values: 0 (top-level only), -1 (all levels)
• customfields — (boolean, optional) Include custom fields in response
• modified_before — (string, optional) Filter by modification date (ISO 8601 format)
• modified_since — (string, optional) Filter by modification date (ISO 8601 format)
• page — (number) Page number for pagination
• limit — (number) Results per page (max 200)
• get_jobcode — Get a specific jobcode by ID

Configuration and credentials

You will need one environment variable: QB_TIME_ACCESS_TOKEN. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Setting it up

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Choosing this one

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Qb Time's toolset — get_jobcodes, ids, name and 11 more — is a fair guide to whether it matches your workflow. It is maintained by aallsbury; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Before you rely on it

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Qb Time.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the qb time mcp server does with a few real requests.