Moltline TimeOps

com.moltlinestudioPublished by moltlinestudio.comOfficial publisherv1.2.0Updated Nov 2, 2026

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

The publisher's own server: Moltline Business Suite

VerifiedStreamable HTTPWeb executableProductivity & Workflow Developer Tools

Server details

Identifier: com.moltlinestudio/timeops
Transport: Streamable HTTP
Runtime: Web executable
Trust: Verified
Published: Sep 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified that this server's namespace belongs to moltlinestudio.com, which also runs its endpoint. That identifies the publisher; it does not make the server's tools safe.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/com.moltlinestudio%2Ftimeops.svg)](https://sourceweft.com/mcp/com.moltlinestudio%2Ftimeops?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

Hosted Moltline server for deterministic date math: business days, meeting overlap across time zones, recurrence expansion, deadline and SLA planning.

What you can do: Compute business-day dates, skipping weekends and a supplied holiday list, or count business days between two dates
Find shared meeting windows across participant UTC offsets within working hours
Expand recurrence rules into concrete ISO date lists, by fixed interval or chosen weekdays
Plan task schedules backward from a hard deadline in business days, with latest safe start and slack
Compute when a ticket's SLA falls due, either wall-clock or business-hours only
When to use it: Useful when an assistant has to answer scheduling questions exactly rather than estimate: delivery or due dates that skip weekends and holidays, finding a call slot across time zones, turning a recurrence rule into dates, or working out SLA and deadline timelines.
Requirements: Remote Streamable HTTP endpoint; no install, account or credentials needed for the free tools. Premium tools need a Moltline license, supplied as the MOLTLINE_LICENSE environment variable (sent as the X-Moltline-License header) or purchased at the vendor site. Stdio-only clients can use the vendor's Python 3.9+ bridge script or its Docker image, which needs network access to the hosted endpoint.

Before you install

Three of the five tools are premium and require a paid license; the free tools work anonymously. A license key is a secret: keep it in the environment variable rather than command-line arguments, which are visible to other local processes. The bridge forwards requests to the vendor's hosted endpoint, so dates and scheduling inputs leave your machine.

Installation

In SourceWeft

Open Moltline TimeOps in the dashboard and add it to a workspace.
Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.moltlinestudio%2Ftimeops/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

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

README

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"    }  }}

{  "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.gitpython3 moltline-mcp/moltline_mcp.py timeops   # any of the 22 slugs; default: catalog

git clone https://github.com/GarphenGate/moltline-mcp.gitpython3 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"]    }  }}

{  "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"]    }  }}

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

CLI

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

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:

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

Source: README.md at commit bbf91e4

Tools

business_days

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.

Parametersadd_daysend_dateholidaysstart_daterequired

meeting_overlap

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.

Parameterswork_endwork_startoffsets_utcrequired

recurrence_expand

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.

Parameterscountweekly_onevery_daysstart_daterequired

deadline_planner

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.

Parameterstasksrequireddue_daterequiredholidaysbuffer_days

sla_due

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.

Parametersday_endholidaysday_startopened_atrequiredsla_hoursrequiredbusiness_hours_only

Version history

v1.2.0LatestSep 16, 2026

Score

100% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

Reached in the last 30 daysRequired25 pts
Auth declaredRequired10 pts
Tools listedRequired15 pts
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
License10 pts

Other Moltlinestudio integrations

Moltline Business Suite

com.moltlinestudioOfficial publisher

Moltline Business Suite is a hosted MCP server offering 30 finance, bookkeeping, legal-ops and SMB operations skill products, plus free business math tools.

Streamable HTTPWeb executable

Finance8 toolsOct 24, 2026