ChronoTab

com.chronotabPublished by chronotab.comOfficial publisherv1.20.1Updated Nov 7, 2026

Log time on GitHub issues in ChronoTab: timers, entries, missing days, client hours.

VerifiedStreamable HTTPWeb executableProductivity & Workflow

Overview

AI-generated overview

ChronoTab lets an assistant log and review time on GitHub issues — timers, entries, missing days and client hours — through a remote endpoint.

What you can do
  • Log time against GitHub issues in ChronoTab
  • Start and manage timers and time entries
  • Review missing days and hours recorded per client
  • No tool list is published, so exact operations are not documented
When to use it
Useful when you track billable or project time in ChronoTab and want an assistant to record or review time entries tied to GitHub issues without switching apps.
Requirements
A remote MCP endpoint at api.chronotab.com over streamable HTTP. OAuth is required, with an Authorization header carrying a bearer ChronoTab API key created on your profile. A ChronoTab account is needed.
Before you install
The server writes time entries, so assistant actions can change your tracked hours and client billing data. It requires a ChronoTab API key sent as a bearer token in the Authorization header; treat that key as a secret. Time data is sent to ChronoTab's service.

Installation

In SourceWeft

  1. Open ChronoTab in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. 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/com.chronotab%2Fchronotab/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": {
    "chronotab": {
      "type": "http",
      "url": "https://api.chronotab.com/v1/mcp"
    }
  }
}

README

ChronoTab for Cursor

Log time on GitHub issues in ChronoTab without leaving Cursor.

This plugin connects Cursor to the ChronoTab MCP server at https://api.chronotab.com/v1/mcp. It contains configuration only; no code runs on your machine.

What it can do

  • Show, start and stop your timer
  • Log time against a GitHub issue
  • List your entries
  • Search issues in your organisation's tracked repositories
  • Find days with missing time
  • List clients and show hours per client

Entries it creates are marked "AI assistant" in ChronoTab. It cannot edit or delete entries, discard timers, or submit, approve or void timesheets. Do those in ChronoTab.

Setup

  1. Sign in to ChronoTab at app.chronotab.com.
  2. Open Profile, then AI assistant, and create an API key. Copy it; it is shown once.
  3. Install this plugin in Cursor and set ChronoTab API key (CHRONOTAB_API_KEY) to the key you copied.
  4. Ask Cursor "what's my timer?" to check the connection.

The key acts as you, in the organisation it was created for. Revoke it on your Profile if you stop using Cursor or think it has leaked.

Try

  • "Start a timer on api#123"
  • "Log 1h30m on web#88 for yesterday, code review"
  • "Which days am I missing time for this week?"
  • "How many hours have we logged for Acme this month?"

Help

License

MIT

Source: README.md at commit 0bfe3c9

Tools

0
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

2
  1. v1.20.1LatestNov 7, 2026
  2. v1.20.0Nov 3, 2026

Score

85% 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