Skip to main content
Glama
scottyphillips

mcp-timer-server

by scottyphillips
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Local

mcp-timer-server

A Model Context Protocol (MCP) server that provides accurate system time to LLM applications via a simple tool call.

Features

  • Real-time data: Provides the current date and time from the host machine

  • Multi-timezone support: Query time in any supported IANA timezone

  • Zero dependencies at runtime: Uses only Node.js built-in Intl API

  • Stdio transport: Works with any MCP-compatible client

Related MCP server: DateTime MCP Server

Installation

Clone and install locally:

git clone https://github.com/scotty-phillips/mcp-timer-server.git
cd mcp-timer-server
npm install

Usage with LM Studio

  1. Open LM Studio and go to the Developer tab (MCP section)

  2. Add a new MCP server configuration pointing to your local installation:

{
  "mcpServers": {
    "timer": {
      "command": "node",
      "args": ["C:\\Users\\scott\\system-time-mcp\\index.js"]
    }
  }
}

Note: Update the path to match where you clone the repo. Use forward slashes or escape backslashes in Windows paths.

Available Tools

get_system_time

Returns the current accurate system date and time from the local workstation.

Input Parameters: None required.

Example Response:

The current time on this workstation is: Wednesday, June 13, 2026, 7:05 PM (Australian Eastern Summer Time)

Note: For timezone-aware time with more IANA timezone options, use the enhanced version at src/index.js which supports a timezone parameter.

Usage with Other Clients

For other MCP-compatible clients, point the server configuration to your local node executable and the path to index.js.

Claude Desktop

Add to your claude_desktop_config.json:

{
  "mcpServers": {
    "timer": {
      "command": "node",
      "args": ["C:/path/to/system-time-mcp/src/index.js"]
    }
  }
}

Cursor

Add to your Cursor MCP settings:

{
  "mcpServers": {
    "timer": {
      "command": "node",
      "args": ["C:/path/to/system-time-mcp/src/index.js"]
    }
  }
}

Development

Running Locally

npm start

Running Tests

npm test

Help

The server runs via stdio and responds to tool calls from any MCP client.

Project Structure

mcp-timer-server/
├── src/
│   └── index.js      # Enhanced version with timezone support
├── tests/
│   └── index.test.js # Basic test suite
├── .gitignore
├── LICENSE
├── README.md
└── package.json

License

MIT - Copyright (c) 2026 Scott Phillips

Author

Scott Phillips
GitHub: scotty-phillips

Buy Me A Coffee

Available Tools

1 tool
get_system_timeA

Returns the current accurate system date and time. Optionally accept a 'timezone' parameter (IANA timezone like 'America/New_York') to display time in a specific timezone.

ParametersJSON Schema
NameRequiredDescriptionDefault
timezoneNoIANA timezone identifier (e.g., 'America/New_York', 'Europe/London'). Defaults to the server's system timezone.

TDQS

A4.5/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations provided, so description bears full responsibility. It discloses read behavior (returns date/time) and optional timezone. No side effects or permissions needed, so transparency is adequate.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences with no wasted words. Purpose and optional parameter are front-loaded in the first sentence.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple read-only tool without output schema, the description explains what is returned and the single optional parameter. No gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%. Description adds value by specifying IANA timezone format and default behavior, enhancing the schema's own parameter description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states the tool returns current accurate system date and time, with optional timezone parameter. No sibling tools exist, so differentiation is not needed.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Description explains optional timezone parameter usage but does not explicitly state when-not-to-use or alternatives. However, the tool is simple and usage is self-evident.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 1 tool updatev1.0.0
    • First observedget_system_time
Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

A4.1/5.0
Disambiguation5/5

Only one tool exists, so there is no risk of confusion or overlap between tools.

Naming Consistency5/5

With a single tool, there are no naming inconsistencies or conflicts to evaluate.

Tool Count1/5

The server name implies timer functionality, yet only provides a system time lookup. A timer server should have tools for creating, managing, and deleting timers, not just reading time.

Completeness1/5

The tool set is severely incomplete for a server named 'mcp-timer-server', missing all expected timer operations (set, cancel, list).

Maintenance

ActivityStale
ResponsivenessSyncing

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

  • Time MCP Server

    dumyCq
    A
    license
    B
    quality
    D
    maintenance
    Provides time and timezone functionality for LLMs, enabling them to get current time information across different timezones and convert times between zones.
    2
    MIT

  • DateTime MCP Server

    pinkpixel-dev
    A
    license
    A
    quality
    C
    maintenance
    Provides LLMs with current date and time information across any timezone, with configurable defaults and support for IANA timezone identifiers.
    1
    30
    3
    Apache 2.0

  • Time MCP Server

    fisher1006
    A
    license
    B
    quality
    D
    maintenance
    Provides current time information and timezone conversion capabilities using IANA timezone names with automatic system detection. It enables LLMs to fetch local or global times and convert specific timestamps between different regions.
    2
    2
    MIT

  • Time MCP Server

    CarterPape
    A
    license
    Not graded
    quality
    D
    maintenance
    Provides current time information and timezone conversion capabilities using IANA timezone names and automatic system detection. It enables LLMs to fetch current times across different regions and convert specific times between timezones.
    MIT

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/scottyphillips/system-time-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server