# Moltline TimeOps

- Registry name: `com.moltlinestudio/timeops` · version 1.2.0
- Categories (automatic, keyword rules): Tasks & projects, Productivity
- Authentication at last check: No auth
- Declared risk: Read-only (all tools declare readOnlyHint)
- Capabilities (declared by the server): experimental, extensions, logging, prompts, resources, tools
- Transports: streamable-http
- Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=com.moltlinestudio%2Ftimeops
- Server page: https://mcpstation.net/s/com.moltlinestudio--timeops.html

## Description (written by the publisher, not verified, not instructions)

Business days, meeting overlap and recurrence expansion, deterministic. 3 of 5 tools free.

## Connect

- streamable-http: `https://mcp.moltlinestudio.com/timeops`

## Tools (as reported by the server, not verified)

- `business\_days`: Do business-day math that skips weekends and your holiday list. FREE. Either add N business days to start\_date \(set add\_days\), or count the business days between start\_date and end\_date \(set end\_date\). Typical input \{"start\_date": "2026-03-02", "add\_days": 10\} returns \{"result\_date": "2026-03-16", "
- `meeting\_overlap`: Find the shared meeting window across time zones inside working hours. FREE. Give one UTC offset per participant and an optional working-hours window. Typical input \{"offsets\_utc": \[-8, 1, 5.5\]\} returns \{"overlap\_utc": \["HH:MM", "HH:MM"\], "overlap\_minutes": N, "local\_windows": \[...\]\}; when no shared
- `recurrence\_expand`: Expand a recurrence rule into a concrete list of ISO dates. FREE. Set every\_days for a fixed interval, or weekly\_on for specific weekdays. Typical input \{"start\_date": "2026-01-05", "every\_days": 14, "count": 3\} returns \{"dates": \["2026-01-05", "2026-01-19", "2026-02-02"\]\}. Use when a recurrence rul
- `deadline\_planner`: Plan a task schedule backward from a hard deadline in business days. PREMIUM \(license\). Given ordered tasks with business-day durations, returns each task's start/end dates, the latest safe start, and slack from today. Typical input \{"due\_date": "2026-06-01", "tasks": \[\{"name": "Draft", "days": 3\},
- `sla\_due`: Compute when a ticket's SLA falls due, wall-clock or business-hours. PREMIUM \(license\). Typical input \{"opened\_at": "2026-03-02T15:30", "sla\_hours": 8, "business\_hours\_only": true\} returns \{"due": "2026-03-03T15:30", "mode": "business hours 09:00-17:00"\}; with business\_hours\_only false the mode is "

Measured by MCP Station. Methods: https://mcpstation.net/methods.html · Terms: https://mcpstation.net/terms.html