JMoak Chrono Mcp
Let agents convert, compare, and format dates across timezones with locale-aware rules instead of hand-rolling brittle datetime code.
Overview
ai.smithery/JMoak-chrono-mcp is a MCP server for the Build phase that converts and compares dates and times across timezones with flexible, locale-aware formatting.
What is this MCP server?
- Convert dates and times across arbitrary timezones via MCP tools
- Compare instants and offsets with agent-friendly responses
- Locale-aware formatting for user-facing timestamps
- Smithery remote v0.2.0 with required Bearer authentication
- Open-source lineage from github.com/JMoak/chrono-mcp
- MCP server schema version 2025-09-29
- Package version 0.2.0
- 1 required secret Authorization header on Smithery remote
What problem does it solve?
Agents and solo devs keep shipping subtle timezone bugs because ad hoc datetime prompts do not replace tested conversion and comparison utilities.
Who is it for?
Builders adding multi-timezone features, launch countdowns, or localized datetime display without importing a heavy calendar SDK into every task.
Skip if: Products that need full calendaring, recurring event CRUD, or compliance-grade audit trails without your own validation on top of MCP output.
What do I get? / Deliverables
After connecting Chrono MCP, agents return consistent cross-timezone conversions and formatted timestamps you can paste into backend and launch code.
- Agent-verified timezone conversions embedded in API or job code
- Comparable instant offsets for launch and SLA decisions
- Locale-formatted timestamp strings ready for UI copy or emails
Recommended MCP Servers
Journey fit
How it compares
Focused datetime MCP utility, not a scheduling SaaS integration or a generic cron monitoring server.
Common Questions / FAQ
Who is ai.smithery/JMoak-chrono-mcp for?
It is for solo developers and agent users implementing backend time logic, global launches, or localized formatting through MCP.
When should I use ai.smithery/JMoak-chrono-mcp?
Use it whenever an agent must translate user local times to UTC, compare deadlines across zones, or emit locale-aware date strings during implementation.
How do I add ai.smithery/JMoak-chrono-mcp to my agent?
Add the Smithery streamable-http remote for chrono-mcp and set the Authorization header to Bearer plus your smithery_api_key.