Skip to main content
Glama
at-mcp

at-mcp

by prepaser

at-mcp

A local MCP server that helps agents stay aware of elapsed time and check whether a user-requested minimum task duration has been met. For a request such as “work for at least 30 minutes,” the agent starts a 1,800-second timer and checks it before its final response.

The server measures elapsed time, including tool waits. It does not measure active effort, judge task completion, or block an agent from ending early. Compliance depends on the agent following the instructions.

Setup

Requires Node.js 24.12.0 or newer and npm.

npx --yes at-mcp@latest

The server listens on stdin and writes MCP messages to stdout. It exits when the client closes stdin. It is normally launched by your MCP host rather than used interactively.

Related MCP server: timex-mcp

Connect

Add the following entry to your MCP host's configuration, adapting the surrounding structure to that host:

{
  "mcpServers": {
    "at-mcp": {
      "command": "npx",
      "args": ["--yes", "at-mcp@latest"]
    }
  }
}

Codex

codex mcp add at-mcp -- npx --yes at-mcp@latest

Or add this to ~/.codex/config.toml (Codex MCP docs):

[mcp_servers.at-mcp]
command = "npx"
args = ["--yes", "at-mcp@latest"]

Tools

Tool

Input

Behavior

start_timer

min_seconds: positive safe integer

Creates an independent timer and returns its UUID and status.

check_timer

timer_id: UUID

Returns the current status without modifying the timer.

get_current_time

Optional time_zone, e.g. Asia/Seoul or UTC

Returns the current system time with its UTC offset and resolved time zone. Defaults to the server's local time zone.

For a request such as “work until 9 PM,” call get_current_time with the user's time zone and interpret the deadline using the returned date and local time. Preserve that deadline in task context and check the time before reporting completion. If the date or time zone is unclear, ask the user rather than assuming the server's default matches their location.

With {"time_zone":"Asia/Seoul"}, get_current_time returns the following as structured content and JSON text:

{
  "current_time": "2026-10-01T21:00:00.123+09:00",
  "time_zone": "Asia/Seoul"
}

Time-zone offsets reflect daylight saving time. If the server's local zone has no usable name, time_zone contains its current UTC offset instead. This tool uses the system clock; minimum-duration checks use the monotonic timers.

The timer tools return the same status as structured content and JSON text:

{
  "timer_id": "e39dadf5-6cd0-40ab-88df-cbb2fb1b27dc",
  "min_seconds": 1800,
  "elapsed_seconds": 1240,
  "remaining_seconds": 560,
  "minimum_met": false
}

Elapsed seconds are rounded down, and remaining seconds are rounded up to a minimum of zero. minimum_met compares the unrounded elapsed duration with the requested minimum, so it cannot become true early because of rounding. Timing uses Node.js's monotonic process.hrtime.bigint() and is unaffected by system time adjustments. Timer ID lookups are case-insensitive and return the canonical lowercase ID.

Each start call creates a new timer; it does not reset an existing one. Timers stay in process memory until the server exits, including after their minimum duration has elapsed. There is no automatic expiration, persistence, reset, or waiting tool. A server restart loses all timers. Invalid inputs and unknown IDs return isError: true; missing timers are never treated as having met their minimum.

Frequent checks

check_timer and get_current_time share a recommended interval of 180 seconds. The first successful check returns normally. Another successful check within the interval adds a warning string to both structured content and JSON text, while still returning fresh time data. Every successful check starts the interval again; changing the tool, timer ID, or time zone does not avoid the warning. Failed calls and start_timer do not count as checks. The history is cleared when the server exits.

The warning asks the agent to continue useful work rather than poll or wait out the interval. It is advisory: completion verification and explicit user requests may justify earlier checks.

Set AT_MCP_CHECK_INTERVAL_SECONDS in the server's environment to change the interval. It must be a positive safe integer representing seconds.

Development

Install pnpm and work from the repository checkout:

pnpm install --frozen-lockfile
pnpm check
pnpm test
pnpm start

Development runs TypeScript directly in Node.js. pnpm build replaces dist/ with the compiled JavaScript CLI so old build artifacts cannot enter a release. To connect a host to your checkout, use node as the command and the absolute path to src/index.ts as its argument.

Publishing

Log in once with npm login, then publish:

npm publish --access public

Publishing runs type checks, tests, and the build automatically, then installs a temporary package and verifies its CLI and all MCP tools. Run pnpm check:package to perform the package check separately. npm reads the version from package.json. For subsequent releases, bump it with npm version patch --no-git-tag-version, using minor or major as appropriate.

Available Tools

2 tools
check_timerA
Read-onlyIdempotent

Check the saved timer after long tool calls, at phase changes, and immediately before a completion response. Require both the current minimum duration and task completion. minimum_met refers to the original min_seconds; if the user revises the minimum, compare elapsed_seconds with the revised duration rounded up to whole seconds, using the same timer. Continue useful work within task scope until both conditions are met; avoid idle waiting, rapid polling, redundant tests, and unrelated changes. Progress updates are allowed. Honor explicit stop requests immediately. Errors do not establish elapsed time; recover if possible or report the limitation without claiming completion.

Inputs: timer_id (required). Returns: timer_id, min_seconds, minimum_met, elapsed_seconds, +1 more

start_timerA

Start a timer at the beginning of a task with a user-requested minimum duration. Convert the duration to whole seconds, rounding up (30 minutes = 1800). Preserve timer_id and min_seconds in task context and summaries. Each call creates a new timer; reuse the existing timer for the same task, including after status questions and context compaction.

Inputs: min_seconds (required). Returns: timer_id, min_seconds, minimum_met, elapsed_seconds, +1 more

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4/5.0

    Scored across 2 tools

    Disambiguation5/5

    start_timer and check_timer have clearly distinct actions: one creates a timer, the other inspects an existing timer. The descriptions reinforce this separation, leaving no ambiguity about which tool to use.

    Naming Consistency5/5

    Both tool names follow a consistent snake_case verb_noun pattern: start_timer and check_timer. This predictable convention makes the set easy to scan and use.

    Tool Count3/5

    Two tools is borderline thin for a timer-related server, as there is no explicit stop, reset, pause, or list operation. The pair is coherent, but the surface feels minimal for the apparent domain.

    Completeness3/5

    The set covers starting and checking a timer but lacks an explicit stop/delete/reset tool, which is a notable lifecycle gap. The description mentions honoring stop requests, but there is no dedicated tool to perform that operation.

    Maintenance

    ActivitySlowing
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Provides LLM agents with a sense of time between turns via two MCP tools that track elapsed time and day rollover per conversation thread.
      3
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables coding agents to create, start, pause, and delete labeled timers within projects, with persistence via SQLite, through a stdio MCP interface.
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI models to answer time-related questions by providing tools for current time and elapsed time.
      -
    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI models to consult a clock, answering current time and elapsed conversation duration through MCP.
      -