How do I use MCP-WTIT?

1. Click on "Deploy Server". 2. Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state. 3. In the chat, type @ followed by the MCP server name and your instructions, e.g., "@MCP-WTIT what time is it in Tokyo right now?" That's it! The server will respond to your query, and you can continue using it as needed. Here is a step-by-step guide with screenshots.

MCP-WTIT

by yorifuji

Overview Schema Source Related Servers Discussions Admin

TypeScript

MCP-WTIT (What Time Is It?)

A Model Context Protocol (MCP) server that provides current time in ISO8601 format with timezone support.

🚀 Features

⏰ Get current time with detailed information (ISO8601, timestamp, timezone)
🌍 Support for all IANA timezones
🎯 Optional milliseconds precision
🏗️ Clean Architecture design
📦 ESModules with TypeScript 5.6+
✅ Comprehensive test coverage
🔧 Type-safe with strict TypeScript configuration

Related MCP server: DateTime MCP Server

📋 Requirements

Node.js 18.0.0 or higher
npm or yarn

🛠️ Installation

As a global package

# Install globally
npm install -g mcp-wtit

# Run the server
mcp-wtit

As a dependency

# Install as a dependency
npm install mcp-wtit

From source

# Clone the repository
git clone https://github.com/yorifuji/mcp-wtit.git
cd mcp-wtit

# Install dependencies
npm install

# Build the project
npm run build

# Run the server
npm start

🚦 Quick Start

For MCP Clients (Claude Desktop, etc.)

Add to your MCP client configuration:

If installed globally:

{
  "mcpServers": {
    "mcp-wtit": {
      "command": "mcp-wtit"
    }
  }
}

If installed locally:

{
  "mcpServers": {
    "mcp-wtit": {
      "command": "node",
      "args": ["./node_modules/mcp-wtit/dist/index.js"]
    }
  }
}

From source:

{
  "mcpServers": {
    "mcp-wtit": {
      "command": "node",
      "args": ["/path/to/mcp-wtit/dist/index.js"]
    }
  }
}

Debug with MCP Inspector

MCP Inspector provides a web-based interface to test and debug your MCP server:

# Build the project first
npm run build

# Run with MCP Inspector
npm run inspect

This will:

Start the MCP Inspector on http://localhost:6274
Automatically open your browser
Connect to the MCP server with debug capabilities

In the Inspector, you can:

View available tools and their schemas
Test tool calls with different parameters
Monitor request/response communication
Debug server behavior in real-time

For Development

# Run in development mode
npm run dev

# Run tests
npm test

# Run tests with coverage
npm run test:coverage

# Lint code
npm run lint

# Type check
npm run typecheck

📚 API Documentation

Tools

`get_current_time`

Get the current time with detailed information.

Parameters:

includeMilliseconds (boolean, optional): Include milliseconds in ISO8601 format (default: true)
timezone (string, optional): Timezone for the time (default: "UTC")

Response:

{
  "iso8601": "2024-01-15T10:30:45.123Z",
  "timestamp": 1705315845123,
  "timezone": "UTC"
}

🏛️ Architecture

This project follows Clean Architecture principles:

src/
├── domain/          # Business logic (no dependencies)
├── application/     # Use cases
├── infrastructure/  # External interfaces (MCP)
├── shared/          # Shared types and utilities
└── di/              # Dependency injection

See Architecture Documentation for details.

🧪 Testing

Tests are located in the tests/ directory and use Vitest:

# Run all tests
npm test

# Run tests in watch mode
npm run test:watch

# Generate coverage report
npm run test:coverage

📦 Scripts

Script	Description
`npm run build`	Build the TypeScript project
`npm run dev`	Run in development mode
`npm start`	Run the built server
`npm run inspect`	Debug with MCP Inspector
`npm test`	Run tests
`npm run test:watch`	Run tests in watch mode
`npm run test:coverage`	Run tests with coverage report
`npm run lint`	Run ESLint
`npm run lint:fix`	Run ESLint and fix issues
`npm run typecheck`	Run TypeScript type checking

🤝 Contributing

Fork the repository
Create your feature branch (git checkout -b feature/amazing-feature)
Commit your changes (git commit -m 'Add some amazing feature')
Push to the branch (git push origin feature/amazing-feature)
Open a Pull Request

📄 License

This project is licensed under the MIT License - see the LICENSE file for details.

🙏 Acknowledgments

Built for the Model Context Protocol
Inspired by Clean Architecture principles

📦 NPM Package

npm version License: MIT Node.js Version

Published on npm: mcp-wtit

Available Tools

1 tool

get_current_timeC

Get the current time with detailed information including ISO8601 format, timestamp, and timezone

ParametersJSON Schema

Name	Required	Description	Default
`includeMilliseconds`	No	Include milliseconds in the ISO8601 format (default: true)
`timezone`	No	Timezone for the time (default: UTC). Examples: "UTC", "America/New_York", "Asia/Tokyo"	UTC

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. While it mentions the output format details, it doesn't describe whether this is a read-only operation, whether it has side effects, rate limits, authentication requirements, or error conditions. For a tool with zero annotation coverage, this represents a significant gap in behavioral transparency.

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

Conciseness4/5

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

The description is a single, efficient sentence that communicates the core functionality and output details. It's appropriately sized for this simple tool, though it could be slightly more structured by separating purpose from output format details.

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

Completeness3/5

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

For a simple time retrieval tool with 2 optional parameters and 100% schema coverage, the description is minimally adequate. However, without annotations or an output schema, it should ideally provide more context about the return format, error handling, and behavioral characteristics to be truly complete.

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

Parameters3/5

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

With 100% schema description coverage, the input schema already fully documents both parameters (includeMilliseconds and timezone) with descriptions and defaults. The tool description adds no additional parameter information beyond what's in the schema, so it meets the baseline expectation but doesn't provide extra value.

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

Purpose4/5

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

The description clearly states the tool's purpose ('Get the current time') and specifies what information it provides ('detailed information including ISO8601 format, timestamp, and timezone'). It distinguishes itself from potential generic time tools by listing specific output details. However, without sibling tools, we cannot assess differentiation from alternatives.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives, prerequisites, or typical use cases. It simply states what the tool does without context about when it's appropriate or what problems it solves.

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.

1 tool updateAug 15, 2025
- First observedget_current_time

Deploy Server

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

B3.1/5.0

Scored 2026-04-18 09:25 across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of ambiguity or overlap between tools. The tool's purpose is clearly distinct as it is the only one available.

Naming Consistency5/5

A single tool inherently has perfect naming consistency since there are no other tools to compare against. The name 'get_current_time' follows a clear verb_noun pattern.

Tool Count2/5

One tool is too few for most server purposes, as it severely limits functionality and scope. This feels thin and inadequate for handling time-related operations beyond just getting the current time.

Completeness2/5

The server's domain appears to be time-related, but with only a single tool for getting the current time, there are significant gaps. Missing operations like time conversion, scheduling, or date calculations make the surface severely incomplete.

Maintenance

ActivityInactive

ResponsivenessNo issues

Resources

Need Help?

Related Servers

Related MCP Connectors

tick-mcp A
io.github.Cocabadger
A time server that keeps your AI honest about time. Real clock + drift guard, zero dependencies.
Developer Tools
226
todo.vu AOAuth
io.github.mooball
Model Context Protocol server for todo.vu task management and time tracking.
Payments & Billing Project Management Workplace & Productivity
2
Studex MCP ServerOAuth
io.github.itshivams
Model Context Protocol server for Studex tools, notifications, and profile integrations
Developer Tools
1
timezone A
io.github.pipeworx-io
Timezone MCP — wraps WorldTimeAPI (free, no auth)
Location Services Search
352

Related MCP Servers

Time Tools MCP Server
Code Execution Developer Tools
t-shiratori
A
license
A
quality
D
maintenance
A Model Context Protocol server for time manipulation tasks, enabling AI models to get the current date/time and calculate duration between timestamps.
Updated a year ago (2025-05-08 13:12 UTC)
7
2
MIT
DateTime MCP Server
Developer Tools
TakanariShimbo
A
license
B
quality
D
maintenance
A Model Context Protocol server that provides tools to get the current date and time in various formats, supporting different timezones and custom formatting options.
Updated a year ago (2025-06-28 23:02 UTC)
1
14
1
MIT
Time MCP Server
Developer Tools
ssinha3
A
license
B
quality
D
maintenance
A Model Context Protocol server that provides time and timezone conversion capabilities, enabling LLMs to get current time information and perform timezone conversions using IANA timezone names.
Updated a year ago (2025-06-27 00:14 UTC)
2
MIT
MCP Time Server
Developer Tools
elimS2
A
license
Not graded
quality
D
maintenance
A lightweight Model Context Protocol server that provides current UTC time in various formats, including ISO 8601 and Unix timestamps. It is designed for seamless integration with Cursor IDE to provide consistent time-related capabilities across all development projects.
Updated a year ago (2025-06-21 12:35 UTC)
MIT

MCP-WTIT (What Time Is It?)

🚀 Features

📋 Requirements

🛠️ Installation

As a global package

As a dependency

From source

🚦 Quick Start

For MCP Clients (Claude Desktop, etc.)

If installed globally:

If installed locally:

From source:

Debug with MCP Inspector

For Development

📚 API Documentation

Tools

get_current_time

🏛️ Architecture

🧪 Testing

📦 Scripts

🤝 Contributing

📄 License

🙏 Acknowledgments

📦 NPM Package

Available Tools

TDQS

Tool Schema Changelog

TDQS

Maintenance

Resources

Related MCP Connectors

Related MCP Servers

Time Tools MCP Server

DateTime MCP Server

Time MCP Server

MCP Time Server

`get_current_time`