Time

This is the MCP equivalent of a good watch: unglamorous, essential, and you forget it's there until you need it. Time gives your agent three tools: current time in any timezone, date arithmetic ("three weeks from next Tuesday"), and parsing human date strings into ISO timestamps. I reach for this whenever I'm building agents that schedule things, log events, or need to reason about deadlines. The timezone support is proper IANA format, so "America/New_York" works as expected. The scheduling math is surprisingly capable: you can ask "what's the date 45 days after 2024-03-15" and get a clean ISO string back. The parser handles messy input like "next Friday at 3pm" or "two weeks from now" without drama. The workflow that sold me: I built a meeting scheduler that needed to propose times across London, New York, and Tokyo. Time let the agent compute "9am EST is what in JST?" without me writing timezone conversion logic or worrying about daylight saving. It just worked. Another use: logging agent runs with proper timestamps instead of the host machine's local time, which matters when you're debugging async workflows. Quirks are minimal. It's a pure utility, so there's no state, no config, no API keys. The tools are simple enough that Claude rarely misuses them. The only gotcha I've hit: if you ask for "tomorrow" without specifying a timezone, it assumes UTC, which can surprise you if you're working in a different zone. Not a bug, just something to remember. Who shouldn't bother: if your agent never touches dates, times, or scheduling, you don't need this. It's not solving a problem you don't have. But if you're building anything calendar-aware, or if you've ever written timezone conversion code by hand, install it. It's one of those tools that earns its place by being boring and reliable.