SHIP

What you can ask

• Which SHIP projects can you reach, and what stage is each open mission in?Copy

  Example path list_missions→get_mission · Ship scheduled tasks skill

• Assign SHIP-412 to SHIP. Tell me when its pull request passes CI, review and tests.
• Turn the plan we just wrote into a SHIP mission that starts at the Builder.

MCP connector

Server URL

https://mcp.letsship.ai/chatgpt/mcpCopy

Login

OAuth

Protocol

MCP 2026-07-28

Instructions

SHIP runs a team of AI coding agents (planner, builder, reviewer, QA) on the user's own GitHub repository. Each mission takes one issue to a pull request that passed CI, a code review and a test of its acceptance criteria. Start with whoami (who you act as, the workspace and the token's scopes) or list_projects (the project ids that mission calls need). Mission lifecycle:

start_mission runs an issue that already exists in the tracker; create_mission files the issue and starts it in one call.

A mission runs for tens of minutes. To wait on one of its agent runs, call watch_agent_run, not a poll: it returns when the run ends or its stage changes. Read get_mission between runs. inspect_mission has the full record when one fails.

To change what a mission does, or to answer its review, call send_mission_instruction. Never call start_mission again to send feedback: call it again only to restart a mission that ended or needs attention. Credits: start_mission, create_mission and run_scheduled_task each start a mission, and every started mission spends workspace credits. Read get_billing before you start work for someone. Instructions to a mission that is already open are free. Handles are stable: an issue id (SHIP-123, WEB-42) and a project id name the same mission and project across calls and conversations. Keep them instead of searching again. A refusal that names a missing scope means this token cannot do that action. Ask the person to grant the scope; do not retry.

Tools

Skills

6 in the ChatGPT listing

• Ship agent runsUse when the user wants to read an agent's log, find why a run failed, follow a run live or stop an agent.
• Ship delegateUse when the user wants to hand a plan, a spec or an open pull request to SHIP.
• Ship mcp serversUse when the user wants the SHIP agents to use an MCP server, or asks which MCP servers the agents can use.
• Ship missionsUse when the user wants to follow a SHIP mission, check its status, or pass it feedback, review comments or a decision while it runs.
• Ship sandboxesUse when the SHIP agents need a runtime or a tool that is not in their sandbox, or a mission waits for an agent slot.
• Ship scheduled tasksUse when the user wants to schedule a task that SHIP runs every day, week or month, such as a dependency update.