# Whenship Muse connector

From musedirectory.ai, the independent directory of Meta Muse connectors. Not affiliated with Meta.

## Whenship

See when work will actually ship and which deadlines are at risk.

- Record: https://musedirectory.ai/connector/whenship
- Category: Productivity
- Developer: Hamed Shams (https://whenship.app)
- Muse status: Extra setup. Not in Muse's Connectors list yet. Muse can still use it: its page gives you a request to paste into Muse.
- Health: Working, 316ms, checked 2026-11-21T17:00:59Z
- Endpoint: https://whenship.app/mcp
- Auth: No account needed; Pricing: unknown
- Screening: Screened, no issues found (2026-11-21T09:31:17Z)
- Source: Found in the official MCP Registry (io.github.HamedShams/whenship) https://registry.modelcontextprotocol.io/v0/servers?search=io.github.HamedShams%2Fwhenship

Connects to Whenship's what-if Gantt planner. Muse can build a plan from your people and tasks, compare changes, flag deadlines that are tight or late, suggest options to meet more of them, and export the result as a calendar, spreadsheet-ready CSV, markdown report or share link.

Example request: "Can my three-person team hit these four client deadlines if we add one more designer in June?"

How to connect: Not in Muse's Connectors list yet, but Muse can still use it. Paste this into Muse: "Use Whenship to help me. It is a free service with an MCP server at https://whenship.app/mcp. It does not need an API key. Ask me before you share anything with it." Muse asks before it shares anything with the app's site. Meta does not review apps used this way, so only use ones you trust. We tested this in the Muse app on September 24, 2026: Muse used an app's link directly this way and returned a live answer.

Tools:
- show_plan: Schedules work for a small team and shows an interactive Gantt chart: finish dates per item, deadline risk (on time / tight / late, with a rough chance), what sets the end date, and the best options to meet more deadlines. Use for "when will this ship", "can we make these deadlin
- what_if: Compares a plan before and after a change and reports which finish dates move and which deadlines are newly met or missed. The change is a list of simple `changes` (move an item to a position, change effort, set or clear a deadline or a can't-start-before date, change a lane's pe
- find_options: Searches realistic changes that would meet more deadlines or make the plan sturdier: reordering, deferring undated work, more availability, one more person, or negotiating a deadline. Every option is re-planned exactly, and returned with its effect and the changes that would appl
- export_plan: Returns the plan as a file: json (the whenship save file, re-openable on the website and in Claude), csv (one row per item with dates), ics (calendar with finish dates and deadlines), markdown (the report), or link (a share link with the whole plan inside it). Spreadsheet (XLSX) 

Screening checks:
- MCP handshake: pass (Answered in 213ms)
- Domain against threat feeds (Cloudflare security DNS): pass (whenship.app not flagged)
- Published packages against the OSV malicious-package database: pass (No malicious-package advisories)
- Hidden instructions or invisible characters in tool text: pass (4 tools read, nothing found)
- Inputs asking for passwords, card numbers or seed phrases: pass (None found)
- Domain and redirects: pass (Domain registered 19 days ago)
- AI review of purpose and tool behavior: pass (No concerns)
