A Model Context Protocol (MCP) server for interacting with Microsoft 365 and Office services through the Graph API
Nothing to run from here
Moltline TimeOps is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
5
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Business days, meeting overlap and recurrence expansion, deterministic. 3 of 5 tools free.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http moltline-timeops-mcp https://mcp.moltlinestudio.com/timeops
# 2 — ask your agent for something these tools do
# business_days, meeting_overlap, recurrence_expand and 2 more
Moltline TimeOps costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
MOAll 22 servers
moltlinestudio22 servers
15 categories
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http moltline-timeops-mcp https://mcp.moltlinestudio.com/timeopsReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
5 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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", "result_weekday": "Monday", ...}; with end_date set it returns {"business_days_between": N, "from":
| Parameter | Type | Required | Notes |
|---|---|---|---|
| start_date | string | yes | Anchor date in ISO format YYYY-MM-DD, e.g. "2026-03-02". |
| add_days | integer | no | Business days to add; negative subtracts. Range -5000 to 5000. Ignored when end_date is provided. |
| end_date | string | no | Optional end date, ISO YYYY-MM-DD. When set, the tool counts business days between start_date and end_date instead of adding. |
| holidays | array | no | Optional list of ISO YYYY-MM-DD dates to treat as non-working days, e.g. ["2026-12-25"]. |
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 window exists it returns {"overlap": null, "verdict": "..."}. Use when people in different zones
| Parameter | Type | Required | Notes |
|---|---|---|---|
| offsets_utc | array | yes | One UTC offset per participant, each between -14 and +14; fractional offsets allowed, e.g. [-8, 1, 5.5]. |
| work_start | string | no | Working day start, 24h HH:MM local in every zone. Default "09:00". |
| work_end | string | no | Working day end, 24h HH:MM; must be later than work_start. Default "17:00". |
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 rule has to become concrete dates. Not for counting working days in a span (business_days) and not fo
| Parameter | Type | Required | Notes |
|---|---|---|---|
| start_date | string | yes | First date of the series, ISO YYYY-MM-DD. |
| count | integer | no | How many dates to generate; values outside 1-60 are clamped into that range. Default 10. |
| every_days | integer | no | Interval in days between occurrences; use this OR weekly_on, not both. |
| weekly_on | array | no | Weekday names to recur on, e.g. ["mon", "thu"]; full names like "monday" also work. |
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}, {"name": "Review", "days": 2}]} returns {"schedule": [...], "latest_safe_start": "YYYY-MM-DD", "sla
| Parameter | Type | Required | Notes |
|---|---|---|---|
| due_date | string | yes | The deadline, ISO YYYY-MM-DD. |
| tasks | array | yes | Ordered list of task objects, each {"name": str, "days": int} where days is the business-day duration (1-365); the first 30 tasks are scheduled. |
| holidays | array | no | Optional list of ISO YYYY-MM-DD dates treated as non-working days. |
| buffer_days | integer | no | Business days of safety margin kept free before due_date, clamped to 0-365. Default 1. |
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 "wall-clock". Use when a response or resolution clock has started and one due moment is needed. Not
| Parameter | Type | Required | Notes |
|---|---|---|---|
| opened_at | string | yes | When the SLA clock started, ISO datetime YYYY-MM-DDTHH:MM. |
| sla_hours | number | yes | SLA length in hours; greater than 0, at most 24000; fractions allowed, e.g. 7.5. |
| business_hours_only | boolean | no | If true, only time inside day_start-day_end on business days counts toward the SLA. |
| day_start | string | no | Business day start, 24h HH:MM. Default "09:00". |
| day_end | string | no | Business day end, 24h HH:MM; must be later than day_start. Default "17:00". |
| holidays | array | no | Optional list of ISO YYYY-MM-DD dates that never count as working days. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Moltline TimeOps or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.2.0.
1.2.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Moltline TimeOps can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.