# SHIP [Health: Active]

**Category:** 🏢 Workplace & Productivity  
**Repository:** https://github.com/letsship/mcp  
**GitHub Stars:** 0  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/ship

## Description
Assign Linear, Jira or GitHub issues to an AI coding agent team that plans, builds, reviews, tests.

## Tools
Capabilities this server exposes over MCP:

- **start_mission** — Give an issue that is already in your tracker to the agent team. By default, the mission starts at the Planner. With a plan, it starts at the Builder. With an open pull request, it starts at the Reviewer or the Tester
- **create_mission** — Create the issue and start the mission in one call, for work that has no issue yet
- **send_mission_instruction** — Tell an active mission what to change, or record a note for the agent that runs next
- **inspect_mission** — The full record of a mission: its stages, verdicts, provenance and session logs
- **list_missions** — The missions of your projects, with what each mission does now
- **get_mission** — One mission: its stage, its review and test results, its pull request, its agent runs and the run with the proof. With `view: "full"`, also its events and the outcome of each stage
- **pause_mission** — Hold a mission before its next stage. The stage that runs now finishes
- **resume_mission** — Continue a paused mission. When a checkpoint holds the mission, this approves the result of that stage
- **stop_mission** — Stop a mission and every agent run of it. The pull request stays open
- **approve_mission_ceiling** — Let a mission continue after it stops at its credit limit. The mission then uses more credits
- **merge_mission** — Merge the pull request of a mission, with the merge method of the repository. On a merge conflict, SHIP starts the Builder to fix the conflict and merges later
- **decline_mission** — Close the pull request of a mission without a merge
- **set_agents_override** — Change the harness, model, prompt or checkpoint of one role for one mission. The override goes on top of `ship.yml` and does not change the file
- **get_agents_override** — Read the override that applies to a mission now
- **clear_agents_override** — Remove the override, so the mission uses the project's configuration again
- **set_mission_auto_merge** — Turn auto-merge on or off for one mission. For that mission, the setting replaces the auto-merge of the project
- **archive_mission** — Hide a mission from the board and from `list_missions`. Only an owner or an admin can archive a mission
- **unarchive_mission** — Show an archived mission on the board again
- **set_mission_disposition** — Record why a mission ended, for example a test or work that another mission replaced, or clear the value. The delivery statistics use this value
- **list_projects** — The projects that the token can reach
- **get_project** — The configuration and connections of one project
- **update_project** — Change the name, status, auto-merge, issue code, default sandbox or connections of a project
- **list_artifacts** — The proof that a run produced, such as test traces and screenshots
- **get_artifact** — One artifact, with a link to open it
- **list_scheduled_tasks** — The missions that a project runs on a schedule
- **get_scheduled_task** — One scheduled task, with its schedule and prompt
- **create_scheduled_task** — Add a mission that runs on a schedule
- **update_scheduled_task** — Change the schedule or prompt of a scheduled task, or disable it
- **run_scheduled_task** — Run a scheduled task now, outside its schedule
- **list_scheduled_task_runs** — What past runs did, and what they cost
- **list_scheduled_task_templates** — Templates that you can copy to start a scheduled task
- **delete_scheduled_task** — Delete a scheduled task and its run history. Missions that the task started continue
- **list_mcp_servers** — The servers that the MCP file of a project declares, each with its binding and status
- **list_mcp_bindings** — Each binding in the projects of your organization, so you can see where each credential is used
- **bind_mcp_server** — Choose the agents, transport, approved tools and credential for one server
- **unbind_mcp_server** — Remove a binding and delete its credential
- **refresh_mcp_server_tools** — Read the current tool list of the server, so that you can approve tools
- **start_mcp_server_oauth** — Get a sign-in link for a remote server, for a person to open in their browser
- **set_mcp_config_path** — Set a different MCP file for a project, such as `.cursor/mcp.json
- **list_agent_runs** — Agent runs, live and finished, for one mission, one role or one status
- **get_agent_run** — The detail and resource use of one run
- **get_agent_run_logs** — What an agent did inside a run
- **watch_agent_run** — Wait on one run and follow its events, until the run ends or its mission moves to another stage
- **stop_agent_run** — Stop the agent in one run before it finishes
- **list_environments** — Preview environments that SHIP deployed for open pull requests
- **get_environment** — One preview environment, with its URL
- **destroy_environment** — Remove a preview environment early
- **get_billing** — The credit balance, the credit limit for each mission and the recent use. Read it before you send work
- **list_billing_ledger** — Where the credits went, with the newest entry first
- **list_credit_offers** — The credit packs and the monthly plans, with their prices
- **start_credit_checkout** — Open a payment page for a credit pack, a monthly plan or more credits on a plan, and return its URL
- **update_team_subscription** — Change the monthly plan from the next renewal, or cancel it at the end of the month that you paid for
- **request_more_credits** — Ask for more credits. The answer says who has the request
- **get_notices** — What needs attention in the workspace, such as a tracker that you must connect again
- **dismiss_notice** — Close a notice that you can close, such as a low balance
- **list_sandbox_templates** — The sandboxes of your organization, with the active version and the latest build of each
- **list_sandbox_starters** — Sandbox definitions for Python, Java, Go, Rust and Ruby that you can start from
- **save_sandbox_template** — Create a sandbox or change one. A change makes a new version and starts its build
- **list_sandbox_template_versions** — Each saved version of a sandbox, with the active version marked
- **activate_sandbox_template_version** — Make a version the one that missions use from their next run
- **build_sandbox_template** — Build the active version now
- **get_sandbox_build_log** — One page of a build log
- **list_sandbox_registries** — The private package registries that sandboxes install from. A secret is never returned
- **save_sandbox_registry** — Store or replace the credential for a registry. The credential never enters a sandbox
- **get_sandbox_capacity** — How many agents your missions run at once, against the limit of your organization
- **delete_sandbox_template** — Delete a sandbox. The API refuses a sandbox that an agent or the default of a project uses
- **delete_sandbox_registry** — Remove the credential of a private registry
- **list_orgs** — Each organization on the platform. Only a SHIP operator token can call it
- **whoami** — The principal behind the token and the scopes of the token
- **get_setup_progress** — What the workspace has set up so far and the next step, as the console's setup checklist shows it
- **healthz** — The status, environment and version of the API

## Claude Desktop Quick Installation
Remote MCP endpoint (confidence: high). Install path detected from listing signals. Add as a URL/SSE server in your client:

```json
"mcpServers": {
  "ship": {
    "url": "https://mcp.letsship.ai/mcp"
  }
}
```

## Documentation

## What SHIP MCP server does

The SHIP MCP server turns tracked software work into managed missions for an AI coding agent team. A mission can begin from an existing Linear, Jira, or GitHub issue, or the server can create the issue as part of starting the work. The workflow assigns separate stages to a Planner, Builder, Reviewer, and Tester, with CI acting as a gate between stages.

Agents can produce code changes and open a pull request in the connected GitHub repository. From an MCP client, you can follow the mission, provide additional instructions, pause or stop it, approve continuation after a credit limit, and decide whether to merge or decline the pull request.

## How it works

The service is available at `https://mcp.letsship.ai/mcp` over Streamable HTTP. It is stateless, so a client can reconnect without losing mission state. A mission normally starts with planning, but an existing plan can send it directly to the Builder. An open pull request can route the work to review or testing instead.

Mission records include stages, verdicts, provenance, session logs, pull requests, agent runs, and test or review results. Artifacts such as test traces and screenshots can be listed and opened through dedicated tools. The roles can use a selected harness and model, including Claude Code, Codex, OpenCode, Kilo Code, or the pi coding agent, according to the project configuration.

## Setup and configuration

Add the remote endpoint to a compatible MCP client. OAuth 2.1 clients can discover the authorization flow and complete sign-in through the SHIP console. Clients without OAuth can send a personal access token as a Bearer token; tokens are created in SHIP settings and can be restricted to one project.

Claude Code, Cursor, VS Code, and Codex each have documented HTTP configuration formats. A client that supports only stdio can connect through `mcp-remote`. The supplied configuration can also include an `Authorization` header for token-based access.

Project tools expose reachable projects, project configuration, connections, auto-merge settings, issue codes, and default sandboxes. Scheduled-task tools can create, edit, disable, run, and inspect recurring missions and their past runs.

## Tools and capabilities

The SHIP MCP server groups its tools around mission control, project administration, proof, and scheduling:

- Start work from an existing issue or create a new issue and mission.
- Send instructions to active missions and record notes for later stages.
- List, inspect, pause, resume, stop, archive, and unarchive missions.
- Read reviews, tests, events, agent runs, pull requests, and run artifacts.
- Override a role’s harness, model, prompt, or checkpoint for one mission.
- Set mission-specific auto-merge behavior and record an ending disposition.
- Merge or decline a mission’s pull request.
- Create and run scheduled missions, then review their costs and results.

Starting a mission or running a scheduled task consumes one credit. Messages sent to an active mission do not consume credits.

## Limitations and notes

The server operates against connected external systems, so token scopes determine which projects and actions are available. Destructive or externally affecting operations include stopping missions, merging or declining pull requests, changing project settings, and approving additional credit use. Review client confirmation behavior before enabling such actions.

The README documents the remote service and client configuration rather than a local package installation. A personal access token must be supplied explicitly when OAuth is unavailable. The pull request remains open when a mission is stopped, while declining closes it without merging.

_Full upstream README: https://allmcps.com/mcp/ship/readme_