MCP Server

Before you start

• A personal access token: open Settings → API Tokens, create a token and copy it (it starts with tta_ and is shown once). The assistant acts as you, with your role, in that token's workspace.
• A Solo, Team or Business plan (the MCP server uses the API).

Option 1: remote server (recommended)

Nothing to install. The app serves MCP over Streamable HTTP at https://demo.trackingtabs.com/api/mcp; send your token as a bearer header.

Claude Code

claude mcp add --transport http tracking-tabs https://demo.trackingtabs.com/api/mcp \
  --header "Authorization: Bearer tta_YOUR_TOKEN"

Cursor

In ~/.cursor/mcp.json (or .cursor/mcp.json in a project):

{
  "mcpServers": {
    "tracking-tabs": {
      "url": "https://demo.trackingtabs.com/api/mcp",
      "headers": { "Authorization": "Bearer tta_YOUR_TOKEN" }
    }
  }
}

Claude Desktop

Claude Desktop's config file only launches local servers, so bridge to the remote one with mcp-remote (needs Node.js 18+). Edit claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\) and restart Claude:

{
  "mcpServers": {
    "tracking-tabs": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://demo.trackingtabs.com/api/mcp",
               "--header", "Authorization:${TRACKING_TABS_AUTH}"],
      "env": { "TRACKING_TABS_AUTH": "Bearer tta_YOUR_TOKEN" }
    }
  }
}

Any other client that supports remote MCP servers with custom headers works the same way.

Option 2: local server (stdio)

The same tools as a local process, in the mcp/ folder of the app repository. It is not published to npm yet, so it has to be built from the source repository (Node.js 18+). Most people should use the remote server above.

git clone https://github.com/rebrandstack/tt-app.git
cd tt-app/mcp
pnpm install   # or npm install
pnpm build     # writes dist/index.js

Environment: TRACKING_TABS_TOKEN (required) and TRACKING_TABS_URL (defaults to https://app.trackingtabs.com).

Claude Code

claude mcp add tracking-tabs \
  -e TRACKING_TABS_TOKEN=tta_YOUR_TOKEN \
  -- node /absolute/path/to/tt-app/mcp/dist/index.js

Claude Desktop / Cursor

{
  "mcpServers": {
    "tracking-tabs": {
      "command": "node",
      "args": ["/absolute/path/to/tt-app/mcp/dist/index.js"],
      "env": { "TRACKING_TABS_TOKEN": "tta_YOUR_TOKEN" }
    }
  }
}

Tools

27 tools. Projects, clients and tasks can be passed by id or by name. Members see only their own time; admins and owners see the whole workspace. Destructive tools are marked so clients ask before running them.

Resources

• workspace://info — The signed-in user and workspace (plan, role, timezone).
• timer://current — The running timer with elapsed seconds, or null.

Example prompts

• "Start a timer on the Website project: homepage copy review."
• "Log 90 minutes yesterday from 2pm on Acme / Design, billable, tagged meeting."
• "How many hours did each person log last week? Group by user."
• "Show this week as a timesheet by project."
• "Draft an invoice for Acme for everything billable in September."
• "Archive the Q2 Retainer project."

Troubleshooting

401 unauthorized

The token is wrong, revoked or expired, or you were removed from the workspace. Create a new token.

403 feature_gated

The workspace is on the Free plan; API and MCP access need Solo or higher.

403 forbidden on create/update project or client

Those actions need the admin or owner role in the workspace.

409 conflict when starting a timer

Your timer is running in another workspace. Stop it there first (one running timer per person).

Rate limited

Each token gets 600 API requests per hour; the remote server counts one request per MCP message.

Local server exits immediately

Set TRACKING_TABS_TOKEN; the error is printed to stderr (your client's MCP log).