MCP Time Server in TypeScript: Model Context Protocol Server for AI Applications

Overview: What is MCP Time Server in TypeScript?

The MCP (Model Context Protocol) Time Server is a specialized TypeScript implementation of an MCP server designed to provide time-related services. It leverages the Model Context Protocol, which acts as a standardized interface enabling AI applications such as Claude Desktop, Continue, and Cursor to interact with various data sources and tools. This server supports features like getting current time in specified timezones and converting times between different zones, offering flexibility through multiple transport options (stdio and HTTP) and Docker integration.

🔧 Core Features & MCP Capabilities

This TCP server is built around several core capabilities:

• Get Current Time: Ability to fetch the current timestamp for a given timezone.
• Convert Time: Functionality to convert times between various time zones, including calculating adjustments due to Daylight Saving Time (DST).
• Modular Architecture: The codebase is divided into discrete modules such as timeService.ts, server.ts, and transports/, facilitating easier maintenance and scalability.
• Flexible Transport Options: Supports both stdio for local testing purposes and HTTP for remote interactions, with easy setup via Node.js or Docker.

⚙️ MCP Architecture & Protocol Implementation

The MCP Time Server employs a modular design to ensure that various components of the system are kept separate but work cohesively. This includes:

1. TimeService: Handles time-related business logic.
2. Server Module: Sets up and configures the server for different transport methods.
3. Transport Implementations: Provides the interface between the server logic and external communication channels.

This separation enhances maintainability and allows developers to easily extend or alter specific parts of the application without disrupting other functionalities.

🚀 Getting Started with Installation

To get started, follow these steps:

1. Clone the Repository:

   git clone <repository-url>
   cd mcp-time-server
   

2. Install Dependencies:

   npm install
   

3. Running the Server: Start with the default stdio transport method:

   npm run build
   npm start
   

Alternatively, use HTTP transport by specifying a port:

npm run build
node dist/index.js --transport=http --port=8080

4. Development Mode: For live development and testing without restarting the server.

   npm run dev
   

5. Docker Deployment:

   • Build and run with Docker for easy containerization.

     docker build -t mcp-time-server .
     docker run --name mcp-time-stdio mcp-time-server
     docker run --name mcp-time-http -p 3000:3000 mcp-time-server node dist/index.js --transport=http
     

   • Docker Compose for streamlined service management:

     docker-compose up
     

💡 Key Use Cases in AI Workflows

1. Real-Time Timezone Conversion: Allows AI applications to handle user queries involving time conversion seamlessly, such as converting when events happened or will happen in different geographical regions.

2. Event Scheduling: Integrates into event management tools used by AI applications for scheduling and reminders across multiple time zones.

🔌 Integration with MCP Clients

The MCP Time Server is designed to work seamlessly with a variety of MCP clients, including:

• Claude Desktop: Full Support
• Continue: Full Support
• Cursor: Tools Only (No Prompts)

This makes it a versatile component in the broader MCP ecosystem.

📊 Performance & Compatibility Matrix

Feature	Stdio Transport	HTTP Transport
Response Time	Fast	Slightly Slower
Server Stability	High	Moderate

This matrix helps developers choose the best transport method based on their performance needs.

🛠️ Advanced Configuration & Security

For advanced setup, you can modify the following JSON configuration snippet:

{
  "mcpServers": {
    "[server-name]": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-[name]"],
      "env": {
        "API_KEY": "your-api-key"
      }
    }
  }
}

Ensure robust security measures are in place, especially when using HTTP transport.

❓ Frequently Asked Questions (FAQ)

1. Q: Does the server support all time zones? A: The server supports a wide range of IANA time zone names, but certain less common territories might require additional configuration.

2. Q: How do I handle Daylight Saving Time transitions? A: Luxon is utilized for accurate timezone handling and DST adjustments.

3. Q: Can I use this with different AI applications? A: Yes, it is compatible with Claude Desktop, Continue, Cursor, and more via their respective MCP clients.

4. Q: How do I test the HTTP transport endpoint? A: Start the server in HTTP mode, then send requests using an MCP client configured for http://localhost:3000/mcp.

5. Q: What does the performance impact of each transport method look like? A: HTTP typically has a slightly higher latency compared to stdio but offers greater flexibility.

👨‍💻 Development & Contribution Guidelines

Contributions are welcome! Follow these guidelines:

1. Fork the repository.
2. Create a new branch for your changes.
3. Ensure all tests pass.
4. Commit and push changes.
5. Submit a pull request detailing your modifications.

🌐 MCP Ecosystem & Resources

Explore further into the MCP ecosystem with resources like MCP Documentation and other tools that integrate seamlessly via this protocol.

Mermaid Diagram 1: MCP Protocol Flow

graph TD;
    A[AI Application] -->|MCP Client| B[MCP Server]
    B --> C[Data Source/Tool]
    style A fill:#e1f5fe
    style B fill:#f3e5f5
    style C fill:#e8f5e8

Mermaid Diagram 2: Data Architecture

graph LR;
    A[TimeService] --> B[Server]
    B --> C[HTTP/stdio Transport]
    C --> D[Client Request Handling]
    D --> E[Data Processing & Response Generation]
    E --> F[Response Return Path]
    F --> G[AI Application/UI]

Real-World AI Workflow Use Case 1: Event Scheduling

Imagine integrating the MCP Time Server into a scheduling application. Users from multiple time zones book appointments and receive notifications based on their local times.

{
  "source_timezone": "America/New_York",
  "appointment_time": "2023-10-15T09:00:00",
  "target_timezone": "Asia/Tokyo"
}

The server converts the appointment time and sends an appropriate notification to the user in Tokyo.

Real-World AI Workflow Use Case 2: Reminder System

For a reminder system, the MCP Time Server can be configured to send reminders just before events based on different user locations. The process involves checking the current time in each timezone against scheduled events and triggering notifications accordingly.

{
  "timezone": "Europe/London",
  "hour": "2023-10-07T14:00:00"
}

The server fetches the local time in London, determines if a reminder is due, and sends out the notification if necessary.

MCP Configuration Code Sample

{
  "mcpServers": {
    "mcp-time-server": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-mcp-time"],
      "env": {
        "API_KEY": "your-api-key"
      }
    }
  }
}

This configuration ensures the MCP server is correctly initialized and ready for interaction with MCP clients.

By following these guidelines, you can effectively integrate the MCP Time Server into diverse AI applications, ensuring seamless time-related operations across various geographical regions.