mcpField
T
TaskTime Pro

TaskTime Pro

Local
tasktime.proProductivity4Updated 2w ago
RepositoryVisit website

About TaskTime Pro

TaskTime Pro Agent Bridge lets same-device AI agents use TaskTime Pro work-management functions through MCP. It pairs with the browser app and forwards tool calls without directly accessing its stored data.

Key features

  1. 01Local MCP stdio bridge
  2. 02Task and timer management
  3. 03Expenses and invoices
  4. 04Reports and planning
  5. 05Browser-app pairing

Use cases

  1. 01Track tasks and work time
  2. 02Prepare and manage invoices
  3. 03Review reports and work plans

MCP support

It exposes TaskTime Pro operations as MCP tools over stdio for same-device agents. Calls are forwarded to the paired TaskTime Pro browser app.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
  "mcpServers": {
    "pro-tasktime-agent-bridge": {
      "command": "npx",
      "args": [
        "-y",
        "@tasktimepro/agent-bridge"
      ]
    }
  }
}
Run commandnpx -y @tasktimepro/agent-bridge

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npm@tasktimepro/agent-bridge1.2.0

Tools

124

Saved tool list · updated 2w ago

ParameterTypeRequiredDescription
endnumberYes
notestringNo
startnumberYes
taskIdstringYes
idempotencyKeystringNo
billingIncrementMinutesnumber|nullNo

Details

From the project README

TaskTime Pro Agent Bridge

@tasktimepro/agent-bridge provides the tasktime-agent-bridge binary used by same-device AI agents to talk to TaskTime Pro over MCP stdio.

TaskTime Pro is a free, open-source, local-first work manager for freelancers. Core use requires no TaskTime account or cloud sync, works offline after the PWA is loaded or installed, and stores work records in the browser.

The bridge does not read or write TaskTime Pro IndexedDB/Yjs data directly. It starts a loopback app-session endpoint, waits for the running TaskTime Pro browser app to pair through Account > Agent Access, and forwards MCP tool calls to the paired browser app.

Billing-scoped tools include approval-gated invoice finalization and cancellation. Cancellation is limited to finalized unpaid invoices, retains the invoice number and audit record, and releases only source work owned by that invoice.

The paired app also owns subscription policy. Free supports one active client and the closed get_report_summary({"scope":"basic-current-month"}) overview. Advanced Reports and report exports require Pro. Email preparation and PDF export remain Free, while TaskTime-hosted invoice/quote sending requires Pro and explicit confirmation. Use get_email_send_status to reconcile an ambiguous attempt without resending it.

Install and run:

npx @tasktimepro/agent-bridge --app-url https://app.tasktime.pro

Useful commands:

tasktime-agent-bridge --manifest
tasktime-agent-bridge --app-url https://app.tasktime.pro

Use --status-file only for non-secret process/endpoint discovery. Pairing IDs, pairing codes, and launch URLs remain available through interactive stderr and the get_pairing_status/refresh_pairing setup tools; the persisted status file intentionally excludes them and is removed on clean shutdown.

The current browser tab can resume a bounded app session across refresh from sessionStorage. Same-profile close/reopen continuity uses a non-exportable browser signing key and a single-use bridge challenge to obtain a fresh session. No reusable bearer token is stored durably. Explicit disconnect/revoke/disable, expiry, or bridge restart requires pairing again.

Official MCP Registry name: pro.tasktime/agent-bridge.

Public docs:

License: AGPL-3.0-only.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.