Log inSubmit server
Atimelogger MCP logo

Atimelogger MCP

Connects AI assistants to ATimeLogger for timer control, activity logging, reports, history, and app documentation.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Atimelogger MCP

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "atimelogger-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "atimelogger-mcp"
      ],
      "env": {
        "ATL_TOKEN": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Automated check passed— started and listed 10 tools correctly (13d ago).

Overview

atimelogger-mcp MCP server exposes the ATimeLogger REST API to AI assistants through MCP. It can control active timers, record or annotate intervals, list activity types, and retrieve reports or raw history. The server runs locally over stdio and uses an ATimeLogger personal access token, while docs-only mode provides app guidance without API access. Reach for it when conversational time tracking or activity analysis is more useful than operating ATimeLogger manually.

Use cases

  • Start and stop timers with natural-language requests
  • Backdate missed timer actions
  • Log and tag completed activities
  • Review time by activity and period
  • Inspect official ATimeLogger feature documentation

Key features

  • Timer control with pause and resume
  • Retroactive interval logging
  • Activity comments and tags
  • Period-based reports and daily history
  • Fuzzy activity-type matching
  • Official app documentation lookup

Tools10

What Atimelogger MCP lets your agent do. Expand a tool for its parameters.

Verified live~2.0k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 3d ago

Recent health check succeeded.

8/8 checks healthy over the last 50d

What it can do

From the 10 tools this server returned when we ran it.

Can delete or modify data · 1Makes network requests · 1Read-only tools · 9
Network at startup3 connections
Files written at startupNone
Install scriptsNone
npm provenanceNot published
Package age86 days
Maintainers1

Observed 2026-10-15 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 12d ago via OSV.dev · atimelogger-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars19Stargazers on the source repository.
npm downloads196Package downloads in the last 30 days.
Last commit2mo agoMost recent push to the default branch.
Availability100%Our rolling endpoint + install checks that succeeded.
Install checkPassedOur sandbox started it and listed its tools.
Tools exposed10Callable tools this server registers over MCP.
Directory activity5 viewsConfig copies, upvotes, and views on AllMCPs.

How Atimelogger MCP works

What atimelogger-mcp does

The atimelogger-mcp MCP server connects an MCP-compatible assistant to an ATimeLogger account through the service's REST API. It covers active timers, activity types, completed intervals, annotations, reports, and history. The server supports both read operations and changes to tracked time, so it can handle requests such as starting work, stopping a timer, adding a past meeting, or tagging an existing entry.

Activity types are addressed by human-readable names and matched approximately against the account's type list. If a name is ambiguous, the assistant can ask for clarification. Internal identifiers may pass through tool inputs and outputs for precise targeting, but they are not shown as the primary user-facing names.

How it works

The atimelogger-mcp MCP server communicates locally over stdio. An MCP client launches the package with Node.js, and the server uses the configured ATimeLogger token for authenticated API calls. The package can be started with npx, so a separate build is not needed when using the published package. Node.js 20 or newer is required.

Time controls include starting, stopping, pausing, and resuming activities. Start and stop operations can use either a wall-clock timestamp or a number of minutes in the past, which supports correcting missed timer actions. Completed intervals can be logged retroactively with start and end times, comments, and tags. Existing entries can have their comments or tags changed without changing their recorded times.

Reports accept named periods such as today, this_week, and last_month, or explicit dates. History is returned by day and supports paging, with a maximum requested range of 100 days. Durations are presented as readable strings, and times use the ATimeLogger account timezone unless a tool request supplies another timezone.

Setup and configuration

Create a personal access token in the ATimeLogger web app under Settings, API Tokens, and Generate token. The token is displayed once and can later be revoked. Set it as ATL_TOKEN in the MCP client's configuration.

Claude Code, Claude Desktop, and OpenAI Codex can register the server with an npx -y atimelogger-mcp command. Claude Desktop requires adding an MCP server entry to its configuration file and restarting the application. The repository also documents running from source by cloning the project, installing dependencies, building it, and using the setup command.

The server can start without ATL_TOKEN in docs-only mode. In that state, app_help remains available and the time-tracking tools return setup guidance instead of accessing account data. Authentication failures generally indicate an invalid, expired, or revoked token.

Tools and capabilities

The atimelogger-mcp MCP server provides these tools:

  • get_current_status reports running or paused activities and elapsed time.
  • list_activity_types returns the account's activity type tree.
  • start_activity, stop_activity, and pause_resume_activity control timers.
  • log_interval records a completed interval with optional comments or tags.
  • update_activity edits comments or tags on current or historical entries.
  • time_report returns aggregated statistics by activity type.
  • list_intervals returns raw, day-grouped history with pagination.
  • app_help retrieves official ATimeLogger documentation about features such as goals, widgets, synchronization, and export.

The same package also installs atimelogger-cli, a read-only JSON command-line tool for status, types, reports, intervals, and diagnostics. It is separate from MCP use and does not start, stop, or edit activities. An experimental library entry point is also available for in-process use by applications such as daemons or editor plugins.

Limitations and notes

The server depends on an ATimeLogger personal access token for account operations and the ATimeLogger service being reachable. The history tool limits a requested range to 100 days. The command-line interface is intentionally read-only; write operations remain available through the MCP server. The app_help tool uses the official ATimeLogger documentation so assistants can look up application behavior instead of inferring it.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Atimelogger MCP

atimelogger-mcp is an MCP server that connects AI assistants to the ATimeLogger REST API. Its main tools control timers, list activity types, log or update intervals, generate time reports, retrieve history, and look up official ATimeLogger documentation. It runs locally over stdio and authenticates with an ATimeLogger personal access token.

Install it by registering `npx -y atimelogger-mcp` with your MCP client and setting the `ATL_TOKEN` environment variable. Node.js 20 or newer is required. The README provides registration commands for Claude Code and OpenAI Codex, plus a configuration block for Claude Desktop.

It requires an ATimeLogger personal access token stored in `ATL_TOKEN` for account operations. Generate the token in the ATimeLogger web app under Settings, API Tokens, and Generate token. The value is shown once; if it is revoked or invalid, generate a replacement and update the MCP configuration.

It can start without a token in docs-only mode, but account time-tracking operations are unavailable. The `app_help` tool remains usable and provides official ATimeLogger documentation, while the other tools return setup instructions until `ATL_TOKEN` is configured.

The documented clients are Claude Desktop, Claude Code, and OpenAI Codex.

Related MCP servers

All in Workplace & Productivity All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewAtimelogger MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/atimelogger-mcp?style=directory)](https://allmcps.com/mcp/atimelogger-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/atimelogger-mcp"><img src="https://allmcps.com/api/badge/atimelogger-mcp?style=directory" alt="Atimelogger MCP on AllMCPs" /></a>