TrackingTime

io.github.TrackingTimePublished by GitHub account TrackingTimev1.0.4Updated Oct 24, 2026

TrackingTime MCP server for time, projects, tasks, users, customers, services, and reports.

VerifiedStreamable HTTPWeb executableProductivity & Workflow Data & Analytics Business & Commerce

Server details

Identifier: io.github.TrackingTime/mcp-server
Transport: Streamable HTTP
Runtime: Web executable
Trust: Verified
Published: Sep 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified the GitHub account TrackingTime for this listing. That does not show the account is the product's maker.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.github.TrackingTime%2Fmcp-server.svg)](https://sourceweft.com/mcp/io.github.TrackingTime%2Fmcp-server?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

Official TrackingTime remote MCP server that lets an assistant track time, manage projects, tasks and customers, and report on hours.

What you can do: Start and stop timers, log manual time entries, and edit or delete entries
Query logged hours by user, project, task, customer or date range, including billable vs. non-billable time
Create, update, archive and assign projects and tasks, and add task comments
Look up and manage customers and services
List users, groups and schedules, and see who is tracking what
Access timecards, time off, expenses, invoices and saved reports where plan and permissions allow
When to use it: Useful for agencies, consultancies and professional services teams already on TrackingTime that want to ask about hours, start timers, log time or manage projects and customers in natural language from an MCP client.
Requirements: A remote endpoint at mcp.trackingtime.co over Streamable HTTP; no installation needed. Authentication is OAuth 2.1 with a TrackingTime account, or an App Password sent in the X-API-Key header for clients without OAuth. Clients lacking remote MCP support can bridge via npx mcp-remote.

Before you install

Actions run with the permissions of the signed-in TrackingTime user and can create, update, archive or delete time entries, projects and tasks. An App Password in the X-API-Key header is a credential and should be stored as an environment variable rather than shared. Some back-office features depend on plan and permissions.

Installation

In SourceWeft

Open TrackingTime in the dashboard and add it to a workspace.
Connect the required credentials. They are stored privately and never shown on public pages.
Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.TrackingTime%2Fmcp-server/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "trackingtime": {
      "type": "http",
      "url": "https://mcp.trackingtime.co/mcp"
    }
  }
}

README

TrackingTime MCP Server

The official Model Context Protocol (MCP) server for TrackingTime, the time tracking software built for agencies, consultancies, and professional services teams.

Connect Claude, ChatGPT, Cursor, VS Code, Windsurf or any MCP-compatible client to your TrackingTime workspace. Ask about your hours, start and stop timers, log time, and manage projects, tasks and customers in natural language.

Remote server, nothing to install: https://mcp.trackingtime.co/mcp
Transport: Streamable HTTP
Auth: OAuth 2.1 (sign in with your TrackingTime account). An App Password via the X-API-Key header is also supported for clients without OAuth.

Features

Track time: start and stop timers, log manual time entries, and edit or delete entries.
Report on hours: query time by user, project, task, customer or date range, including billable vs. non-billable time.
Manage projects and tasks: create, update, archive and assign projects and tasks; add task comments.
Customers and services: look up and manage the customers and services linked to your work.
Team data: list users, groups and schedules, and see who is tracking what.
Back office: timecards, time off, expenses, invoices and saved reports, depending on your plan and permissions.

Every action runs with the permissions of the signed-in TrackingTime user.

Example prompts

"How many hours did the team log last week, by project?"
"Start a timer on the Homepage redesign task."
"Log 2 hours yesterday on Acme Corp > Monthly retainer."
"Which tasks in Website Redesign are over their estimate?"
"What's the billable time for Acme Corp this month?"

Connect

Claude, ChatGPT and other clients with remote MCP support

Add a custom connector with this URL and sign in with TrackingTime when prompted:

Clients that need a local bridge (mcp-remote)

json

{  "mcpServers": {    "trackingtime": {      "command": "npx",      "args": ["-y", "mcp-remote", "https://mcp.trackingtime.co/mcp"]    }  }}

{  "mcpServers": {    "trackingtime": {      "command": "npx",      "args": ["-y", "mcp-remote", "https://mcp.trackingtime.co/mcp"]    }  }}

Using an App Password instead of OAuth

json

{  "mcpServers": {    "trackingtime": {      "command": "npx",      "args": [        "-y", "mcp-remote", "https://mcp.trackingtime.co/mcp",        "--header", "X-API-Key:${TRACKINGTIME_APP_PASSWORD}"      ],      "env": { "TRACKINGTIME_APP_PASSWORD": "<your app password>" }    }  }}

{  "mcpServers": {    "trackingtime": {      "command": "npx",      "args": [        "-y", "mcp-remote", "https://mcp.trackingtime.co/mcp",        "--header", "X-API-Key:${TRACKINGTIME_APP_PASSWORD}"      ],      "env": { "TRACKINGTIME_APP_PASSWORD": "<your app password>" }    }  }}

Endpoints

POST /mcp: MCP over Streamable HTTP
GET /health: health check
/.well-known/oauth-authorization-server and /.well-known/oauth-protected-resource/mcp: OAuth discovery

The legacy SSE endpoint (/sse) has been retired.

Tools

This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

v1.0.4LatestOct 6, 2026
v1.0.3Oct 2, 2026
v1.0.2Sep 16, 2026

Score

75% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

Reached in the last 30 daysRequired25 pts
Auth declaredRequired10 pts
Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
License10 pts
Declare a license in the repository or the registry entry.