Moltline TimeOps

Official5 tools

by GarphenGate · Python

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

com.moltlinestudio/timeops (MCP Server)

The com.moltlinestudio/timeops MCP server provides deterministic tooling for business days, meeting overlap, and recurrence expansion. It exposes 5 tools and is intended to integrate with Moltline Studio’s hosted MCP servers via a stdio bridge.

🛠️ Key Features

Deterministic handling for business days
Meeting overlap processing
Recurrence expansion
5 tools available

🚀 Use Cases

Calculate or verify business-day schedules
Determine overlaps between meetings
Expand recurring events into concrete instances

⚡ Developer Benefits

Thin, dependency-free stdio bridge
Proxies newline-delimited JSON-RPC over stdio verbatim
No telemetry and uses only Python 3.9+ standard library

⚠️ Limitations

Designed as a stdio-transport bridge; direct Streamable HTTP connection is preferred for compatible MCP clients
Server tooling and scope described cover “business days, meeting overlap and recurrence expansion” with 5 tools

Topics

agent-skillsai-agentsclaudemcpmcp-servermodel-context-protocol

Captured live from the server via tools/list.

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", "result_weekday": "Monday", ...}; with end_date set it returns {"business_days_between": N, "from": ..., "to": ...}. Use when the span must exclude weekends and named holidays. Not for plain calendar-day differences, which are a direct subtraction, and not for scheduling backward from a fixed deadline (deadline_planner). Errors: on invalid, missing, or malformed input this tool never raises a protocol error — it returns {"error": "<what is wrong and how to fix it>"} (for example {"error": "dates must be YYYY-MM-DD"}). Every call is read-only and idempotent, so after correcting the input it is always safe to retry.

Parameters4

start_date	string	required	Anchor date in ISO format YYYY-MM-DD, e.g. "2026-03-02".
add_days	integer	optional	Business days to add; negative subtracts. Range -5000 to 5000. Ignored when end_date is provided.
end_date	string	optional	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	optional	Optional list of ISO YYYY-MM-DD dates to treat as non-working days, e.g. ["2026-12-25"].

Raw schema

{
  "type": "object",
  "properties": {
    "start_date": {
      "type": "string",
      "description": "Anchor date in ISO format YYYY-MM-DD, e.g. \"2026-03-02\"."
    },
    "add_days": {
      "default": 0,
      "maximum": 5000,
      "minimum": -5000,
      "type": "integer",
      "description": "Business days to add; negative subtracts. Range -5000 to\n5000. Ignored when end_date is provided."
    },
    "end_date": {
      "default": "",
      "type": "string",
      "description": "Optional end date, ISO YYYY-MM-DD. When set, the tool counts\nbusiness days between start_date and end_date instead of adding."
    },
    "holidays": {
      "default": [],
      "items": {
        "type": "string"
      },
      "type": "array",
      "description": "Optional list of ISO YYYY-MM-DD dates to treat as\nnon-working days, e.g. [\"2026-12-25\"]."
    }
  },
  "required": [
    "start_date"
  ],
  "additionalProperties": false
}

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 window exists it returns {"overlap": null, "verdict": "..."}. Use when people in different zones need one shared slot. Not for converting a single known time between zones, and not for expanding a recurring series (recurrence_expand). Errors: on invalid, missing, or malformed input this tool never raises a protocol error — it returns {"error": "<what is wrong and how to fix it>"} (for example {"error": "times must be HH:MM"}). Every call is read-only and idempotent, so after correcting the input it is always safe to retry.

Parameters3

offsets_utc	array	required	One UTC offset per participant, each between -14 and +14; fractional offsets allowed, e.g. [-8, 1, 5.5].
work_start	string	optional	Working day start, 24h HH:MM local in every zone. Default "09:00".
work_end	string	optional	Working day end, 24h HH:MM; must be later than work_start. Default "17:00".

Raw schema

{
  "type": "object",
  "properties": {
    "offsets_utc": {
      "items": {
        "maximum": 14,
        "minimum": -14,
        "type": "number"
      },
      "type": "array",
      "description": "One UTC offset per participant, each between -14 and\n+14; fractional offsets allowed, e.g. [-8, 1, 5.5]."
    },
    "work_start": {
      "default": "09:00",
      "type": "string",
      "description": "Working day start, 24h HH:MM local in every zone.\nDefault \"09:00\"."
    },
    "work_end": {
      "default": "17:00",
      "type": "string",
      "description": "Working day end, 24h HH:MM; must be later than work_start.\nDefault \"17:00\"."
    }
  },
  "required": [
    "offsets_utc"
  ],
  "additionalProperties": false
}

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 rule has to become concrete dates. Not for counting working days in a span (business_days) and not for finding a slot across zones (meeting_overlap). Errors: on invalid, missing, or malformed input this tool never raises a protocol error — it returns {"error": "<what is wrong and how to fix it>"} (for example {"error": "start_date must be YYYY-MM-DD"}). Every call is read-only and idempotent, so after correcting the input it is always safe to retry.

Parameters4

start_date	string	required	First date of the series, ISO YYYY-MM-DD.
count	integer	optional	How many dates to generate; values outside 1-60 are clamped into that range. Default 10.
every_days	integer	optional	Interval in days between occurrences; use this OR weekly_on, not both.
weekly_on	array	optional	Weekday names to recur on, e.g. ["mon", "thu"]; full names like "monday" also work.

Raw schema

{
  "type": "object",
  "properties": {
    "start_date": {
      "type": "string",
      "description": "First date of the series, ISO YYYY-MM-DD."
    },
    "count": {
      "default": 10,
      "type": "integer",
      "description": "How many dates to generate; values outside 1-60 are clamped\ninto that range. Default 10."
    },
    "every_days": {
      "default": 0,
      "type": "integer",
      "description": "Interval in days between occurrences; use this OR\nweekly_on, not both."
    },
    "weekly_on": {
      "default": [],
      "items": {
        "type": "string"
      },
      "type": "array",
      "description": "Weekday names to recur on, e.g. [\"mon\", \"thu\"]; full names\nlike \"monday\" also work."
    }
  },
  "required": [
    "start_date"
  ],
  "additionalProperties": false
}

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}, {"name": "Review", "days": 2}]} returns {"schedule": [...], "latest_safe_start": "YYYY-MM-DD", "slack_business_days_from_today": N, "verdict": "..."}. Use when the end date is fixed and steps must be placed backward from it. Not for forward counting from a start date (business_days) and not for response-time targets (sla_due). Errors: on invalid, missing, or malformed input this tool never raises a protocol error — it returns {"error": "<what is wrong and how to fix it>"} (for example {"error": "due_date must be YYYY-MM-DD"}). Every call is read-only and idempotent, so after correcting the input it is always safe to retry.

Parameters4

due_date	string	required	The deadline, ISO YYYY-MM-DD.
tasks	array	required	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	optional	Optional list of ISO YYYY-MM-DD dates treated as non-working days.
buffer_days	integer	optional	Business days of safety margin kept free before due_date, clamped to 0-365. Default 1.

Raw schema

{
  "type": "object",
  "properties": {
    "due_date": {
      "type": "string",
      "description": "The deadline, ISO YYYY-MM-DD."
    },
    "tasks": {
      "items": {
        "additionalProperties": true,
        "type": "object"
      },
      "type": "array",
      "description": "Ordered list of task objects, each {\"name\": str, \"days\": int}\nwhere days is the business-day duration (1-365); the first 30\ntasks are scheduled."
    },
    "holidays": {
      "default": [],
      "items": {
        "type": "string"
      },
      "type": "array",
      "description": "Optional list of ISO YYYY-MM-DD dates treated as\nnon-working days."
    },
    "buffer_days": {
      "default": 1,
      "type": "integer",
      "description": "Business days of safety margin kept free before\ndue_date, clamped to 0-365. Default 1."
    }
  },
  "required": [
    "due_date",
    "tasks"
  ],
  "additionalProperties": false
}

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 "wall-clock". Use when a response or resolution clock has started and one due moment is needed. Not for multi-step project schedules (deadline_planner). Errors: on invalid, missing, or malformed input this tool never raises a protocol error — it returns {"error": "<what is wrong and how to fix it>"} (for example {"error": "opened_at must be ISO YYYY-MM-DDTHH:MM"}). Every call is read-only and idempotent, so after correcting the input it is always safe to retry.

Parameters6

opened_at	string	required	When the SLA clock started, ISO datetime YYYY-MM-DDTHH:MM.
sla_hours	number	required	SLA length in hours; greater than 0, at most 24000; fractions allowed, e.g. 7.5.
business_hours_only	boolean	optional	If true, only time inside day_start-day_end on business days counts toward the SLA.
day_start	string	optional	Business day start, 24h HH:MM. Default "09:00".
day_end	string	optional	Business day end, 24h HH:MM; must be later than day_start. Default "17:00".
holidays	array	optional	Optional list of ISO YYYY-MM-DD dates that never count as working days.

Raw schema

{
  "type": "object",
  "properties": {
    "opened_at": {
      "type": "string",
      "description": "When the SLA clock started, ISO datetime YYYY-MM-DDTHH:MM."
    },
    "sla_hours": {
      "exclusiveMinimum": 0,
      "maximum": 24000,
      "type": "number",
      "description": "SLA length in hours; greater than 0, at most 24000;\nfractions allowed, e.g. 7.5."
    },
    "business_hours_only": {
      "default": false,
      "type": "boolean",
      "description": "If true, only time inside day_start-day_end on\nbusiness days counts toward the SLA."
    },
    "day_start": {
      "default": "09:00",
      "type": "string",
      "description": "Business day start, 24h HH:MM. Default \"09:00\"."
    },
    "day_end": {
      "default": "17:00",
      "type": "string",
      "description": "Business day end, 24h HH:MM; must be later than day_start.\nDefault \"17:00\"."
    },
    "holidays": {
      "default": [],
      "items": {
        "type": "string"
      },
      "type": "array",
      "description": "Optional list of ISO YYYY-MM-DD dates that never count as\nworking days."
    }
  },
  "required": [
    "opened_at",
    "sla_hours"
  ],
  "additionalProperties": false
}

README.md9 KBView on GitHub

moltline-mcp

A thin, dependency-free stdio bridge to Moltline Studio's fleet of 22 hosted MCP servers.

Most modern MCP clients can connect to the fleet directly over Streamable HTTP — no install needed (see Direct connection below). This bridge exists for clients that only speak the stdio transport: it proxies newline-delimited JSON-RPC between your client and the hosted server, verbatim, with no telemetry and no dependencies beyond the Python 3.9+ standard library.

160 tools across 22 servers; 110 are free.
Free tier: no registration, no account, no credentials — connect and call tools immediately.
Premium tools are unlocked with a Moltline license. Set MOLTLINE_LICENSE in your MCP client's environment; the bridge sends it as the X-Moltline-License header and never writes it to argv, URLs or logs. See auth.md.
Independently checked by MCPize on the direct endpoints (scans of 5–6 September 2026: 6 A+, 15 A, 1 B+; scores 89–98). All 22 servers score 100 on clarity, 100 on reliability and 100 on trust, 95 on protocol and 87 on safety; the one finding raised on every server is that the free tier accepts anonymous access — which is the point of it — and the spread between servers sits in MCPize's "Market" dimension (a crowded category). Each server's MCPize listing links its own public result.

Find it on: Smithery · MCPize · Glama · Clawmart · MCP Registry

The fleet

Server	Tools	What it does
`catalog`	10	Search 138 agent skills and personas by plain-language job; preview any product.
`codereview`	7	Risk-scan a diff, flag AI-generated-code tells, find secrets, report complexity.
`govern`	8	Audit an MCP config or SKILL.md for over-broad scope and prompt-injection risk.
`timeops`	5	Business days, meeting overlap, recurrence expansion, deadline and SLA math.
`data`	7	Paste-your-data analytics: CSV profiling, A/B tests, correlation, growth, cohorts.
`humanizer`	5	Find AI-isms with evidence, fingerprint a writing voice, measure burstiness.
`business`	8	30 finance, bookkeeping, legal-ops and SMB operations persona-skill products.
`creator`	8	20 blogging, brand-voice, copywriting, video and social persona-skill products.
`educator`	7	8 curriculum, classroom, accommodations and exam-prep persona-skill products.
`outbound`	8	7 outreach, sequencing, deliverability, call-coaching and CRM-hygiene products.
`personal`	9	20 inbox, calendar, travel, meals and family-logistics persona-skill products.
`research`	8	7 research navigation, thesis, note-taking and citation persona-skill products.
`skillmd-lint`	6	Lint a SKILL.md for frontmatter, structure, secrets and size. All tools free.
`merchant`	6	Commerce arithmetic: processor fees, charge-to-net, invoice totals, proration.
`shipping`	6	Dimensional weight, parcel fit, landed cost, freight class, rate cards.
`shopify`	6	Check a product CSV, URL handles, variant matrices and metafield keys.
`dropship`	6	Dropshipping unit economics: margin, lead time, SKU mapping, price ladders.
`recall`	6	A portable knowledge-graph memory you pass in and get back. No database.
`vision`	6	Image header probing, bbox conversion, resize plans, color and detection math.
`regclock`	9	Incident-reporting deadlines from the legal text (EU CRA, NIS2, DORA, GDPR, UK GDPR, HIPAA, SEC 8-K), cited.
`taxlots`	8	Crypto cost basis: parse exchange CSVs, lint, match transfers, FIFO/LIFO/HIFO lots, Form 8949 rows, 1099-DA diff.
`optimize`	11	OR-Tools routing, 3-D packing, 1-D/2-D cutting, knapsack and shift rostering with stated limits.

Machine-readable discovery: api-catalog · per-server card at https://mcp.moltlinestudio.com/<server>/.well-known/mcp/server-card.json · fleet health.

Direct connection (preferred)

If your MCP client supports Streamable HTTP (Claude Desktop, Claude Code, Cursor, and most current clients do), point it straight at the hosted endpoint — nothing to install:

json

{
  "mcpServers": {
    "moltline-timeops": {
      "type": "http",
      "url": "https://mcp.moltlinestudio.com/timeops"
    }
  }
}

Swap timeops for any slug in the table above.

The stdio bridge (for stdio-only clients)

Install

Run directly (recommended) — the bridge is a single stdlib-only file, so a clone is all you need:

bash

git clone https://github.com/GarphenGate/moltline-mcp.git
python3 moltline-mcp/moltline_mcp.py timeops   # any of the 22 slugs; default: catalog

Docker — see Docker below if you prefer a container.

A PyPI package is planned; until then, use the methods above.

Client configuration

Point your MCP client at the script with an absolute path:

json

{
  "mcpServers": {
    "moltline-timeops": {
      "command": "python3",
      "args": ["/absolute/path/to/moltline-mcp/moltline_mcp.py", "timeops"]
    }
  }
}

Or run it through Docker (after docker build -t moltline-mcp .):

json

{
  "mcpServers": {
    "moltline-timeops": {
      "command": "docker",
      "args": ["run", "-i", "--rm", "moltline-mcp", "timeops"]
    }
  }
}

CLI

text

python3 moltline_mcp.py [server] [--timeout SECONDS] [--list] [--version]

server — one of the 22 slugs (default catalog); anything else fails fast with the valid list.
--timeout — per-request timeout in seconds (default 300, or env MOLTLINE_TIMEOUT).
--list — print the server slugs and exit.
Env MOLTLINE_BASE_URL — override the fleet base URL (for testing).
Env MOLTLINE_LICENSE — your Moltline license, sent as the X-Moltline-License header to unlock premium tools. Omit it and the bridge runs free-tier only.
Env MOLTLINE_DEBUG=1 — diagnostic logging on stderr (stdout stays protocol-clean). The license is never logged; debug output reports only whether one is configured.

Docker

The bridge also runs containerized (stdio in, network egress to the fleet required):

bash

docker build -t moltline-mcp .
docker run -i --rm moltline-mcp timeops   # any of the 22 slugs; default: catalog

See Client configuration for the matching mcpServers entry.

How it works

One process per server connection. Each JSON-RPC message read from stdin is POSTed to https://mcp.moltlinestudio.com/<server>; JSON and SSE-framed responses are relayed back to stdout as newline-delimited JSON. The bridge tracks the server-assigned Mcp-Session-Id and echoes the negotiated MCP-Protocol-Version, per the Streamable HTTP transport spec. It never inspects, stores, or reports your traffic.

Tests

The bridge ships with an offline test suite - no network, no dependencies:

bash

python -m unittest -v

Twenty-two tests cover the parts that actually break in a transport bridge: newline-delimited framing, SSE event splitting (multiple events, multi-line data: payloads, a trailing event with no blank line, comments and named events), session-id capture and reuse, protocol-version negotiation on initialize only, and error relay - a JSON-RPC error document is passed through verbatim, anything else becomes a well-formed -32603. CI runs them on Python 3.9, 3.12 and 3.13, plus a Docker build and container smoke test.

Access and licensing

Free tier — anonymous. No registration or credentials; all free tools work immediately.
Premium — unlocked with a Moltline license purchased (human-in-the-loop) at moltlinestudio.com. Set MOLTLINE_LICENSE in the environment and the bridge forwards it as the X-Moltline-License request header. It is deliberately not a command-line flag: argv is world-readable through ps. It is never placed in a URL and never logged. Details: auth.md.

License

Install

Tools (5)

business_daysmeeting_overlaprecurrence_expanddeadline_plannersla_due

Remote endpoint

Streamable HTTP

Hosted server - connect over the network, no local install.

url

https://mcp.moltlinestudio.com/timeops

Add to VS Code Add to Cursor

claude_desktop_config.json

json

{
  "mcpServers": {
    "timeops": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.moltlinestudio.com/timeops"
      ]
    }
  }
}

Desktop config is stdio-only; this bridges via mcp-remote. Native remote: Settings > Connectors.

Moltline TimeOps

com.moltlinestudio/timeops (MCP Server)

🛠️ Key Features

🚀 Use Cases

⚡ Developer Benefits

⚠️ Limitations

Topics

business_days

meeting_overlap

recurrence_expand

deadline_planner

sla_due

moltline-mcp

The fleet

Direct connection (preferred)

The stdio bridge (for stdio-only clients)

Install

Client configuration

CLI

Docker

How it works

Tests

Access and licensing

Links

License

Install

Remote endpoint

Related servers