mcp

<p align="center"><a href="https://letsship.ai" target="_blank" rel="noopener"><img src="assets/ship.png" alt="SHIP" width="96" height="96"></a></p>

# SHIP MCP server

[![MCP Registry](https://img.shields.io/badge/MCP%20Registry-ai.letsship%2Fship-e84826)](https://registry.modelcontextprotocol.io/v0.1/servers/ai.letsship%2Fship/versions/latest)
[![Transport](https://img.shields.io/badge/transport-Streamable%20HTTP-0f0a07)](https://letsship.ai/docs/mcp)
[![Auth](https://img.shields.io/badge/auth-OAuth%202.1%20%7C%20token-0f0a07)](https://letsship.ai/docs/mcp#connect-a-client)
[![Docs](https://img.shields.io/badge/docs-letsship.ai-0f0a07)](https://letsship.ai/docs/mcp)
[![Smithery](https://smithery.ai/badge/ship/ship)](https://smithery.ai/servers/ship/ship)

Assign Linear, Jira or GitHub issues to an AI coding agent team. Its coding agents plan and build each change, run code review and tests, and open a pull request in your GitHub repository. With this MCP server, your assistant can file missions, follow them, send instructions and read the proof of each run.

SHIP runs an agentic SDLC as a headless AI software factory. You operate the whole mission from your coding agent or AI assistant. Start it, send instructions, read its code review and test reports, and approve the pull request. A Planner, a Builder, a Reviewer and a Tester each do one stage, and your CI is a gate between them. Each role runs the coding agent and the model that you choose: Claude Code, Codex, OpenCode, Kilo Code or the pi coding agent.

[![Install in VS Code](https://img.shields.io/badge/VS%20Code-Install%20SHIP-0098FF)](https://vscode.dev/redirect/mcp/install?name=ship&config=%7B%22type%22%3A%22http%22%2C%22url%22%3A%22https%3A%2F%2Fmcp.letsship.ai%2Fmcp%22%7D)
[![Install in VS Code Insiders](https://img.shields.io/badge/VS%20Code%20Insiders-Install%20SHIP-24bfa5)](https://insiders.vscode.dev/redirect/mcp/install?name=ship&config=%7B%22type%22%3A%22http%22%2C%22url%22%3A%22https%3A%2F%2Fmcp.letsship.ai%2Fmcp%22%7D)
[![Add to Cursor](https://cursor.com/deeplink/mcp-install-dark.svg)](cursor://anysphere.cursor-deeplink/mcp/install?name=ship&config=eyJ1cmwiOiJodHRwczovL21jcC5sZXRzc2hpcC5haS9tY3AifQ==)

## Endpoint

```text
https://mcp.letsship.ai/mcp
```

The transport is Streamable HTTP. The server is stateless, so a client can reconnect at any time and lose nothing.

## Sign in

**OAuth 2.1.** A client that supports MCP authorization finds the sign-in automatically. If a request needs a token and has no valid token, the server answers `401` with a `WWW-Authenticate` header.
The header points to `https://mcp.letsship.ai/.well-known/oauth-protected-resource/mcp`. SHIP supports dynamic client registration and client ID metadata documents, so you do not have to register a client first. You approve the sign-in in the SHIP console.

**Personal access token.** A client without OAuth sends `Authorization: Bearer pat_...`. Create a token at https://letsship.ai/settings/tokens. Bind it to one project, so that it can reach only that project.

## Install

**Claude Code**

```bash
claude mcp add --transport http ship https://mcp.letsship.ai/mcp
```

**Claude and ChatGPT.** Add a custom connector with the URL `https://mcp.letsship.ai/mcp`. Sign in when the app asks.

**Cursor.** Use the button above, or add this to `.cursor/mcp.json`:

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

**VS Code.** Use the buttons above, or add this to `.vscode/mcp.json`:

```json
{
  "servers": {
    "ship": {
      "type": "http",
      "url": "https://mcp.letsship.ai/mcp"
    }
  }
}
```

**Codex.** Add this to `~/.codex/config.toml`:

```toml
[mcp_servers.ship]
url = "https://mcp.letsship.ai/mcp"
```

**Grok.** Open grok.com/connectors. Select **New Connector**, then **Custom**. Paste the URL `https://mcp.letsship.ai/mcp`. Then sign in.

**xAI API.** Pass the URL as a remote MCP tool, with a token in `headers`:

```json
{
  "type": "mcp",
  "server_url": "https://mcp.letsship.ai/mcp",
  "server_label": "ship",
  "headers": {
    "Authorization": "Bearer pat_your_token_here"
  }
}
```

**A client that supports only stdio** connects through `mcp-remote`:

```json
{
  "mcpServers": {
    "ship": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.letsship.ai/mcp"
      ]
    }
  }
}
```

**With a token.** Add the header to any of the HTTP entries above:

```json
{
  "mcpServers": {
    "ship": {
      "url": "https://mcp.letsship.ai/mcp",
      "headers": {
        "Authorization": "Bearer pat_your_token_here"
      }
    }
  }
}
```

## Tools

Each tool declares `readOnlyHint`, `destructiveHint` and `openWorldHint`. With these hints, your client can run a read-only tool immediately. It can also ask you before it runs a tool that removes or replaces something, or opens a payment page. The scopes of the token decide what each tool can do, and a refusal names the scope that the token does not have.

> [!IMPORTANT]
> `start_mission`, `create_mission` and `run_scheduled_task` start a mission, and each mission start costs one credit. Messages to an active mission are free.

### Missions

| Tool | Kind | What it does |
| --- | --- | --- |
| `start_mission` | reaches outside SHIP | 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` | reaches outside SHIP | Create the issue and start the mission in one call, for work that has no issue yet |
| `send_mission_instruction` | reaches outside SHIP | Tell an active mission what to change, or record a note for the agent that runs next |
| `inspect_mission` | reads | The full record of a mission: its stages, verdicts, provenance and session logs |
| `list_missions` | reads | The missions of your projects, with what each mission does now |
| `get_mission` | reads | 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` | writes | Hold a mission before its next stage. The stage that runs now finishes |
| `resume_mission` | reaches outside SHIP | Continue a paused mission. When a checkpoint holds the mission, this approves the result of that stage |
| `stop_mission` | removes | Stop a mission and every agent run of it. The pull request stays open |
| `approve_mission_ceiling` | reaches outside SHIP | Let a mission continue after it stops at its credit limit. The mission then uses more credits |
| `merge_mission` | removes | 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` | removes | Close the pull request of a mission without a merge |
| `set_agents_override` | replaces | 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` | reads | Read the override that applies to a mission now |
| `clear_agents_override` | removes | Remove the override, so the mission uses the project's configuration again |
| `set_mission_auto_merge` | reaches outside SHIP | Turn auto-merge on or off for one mission. For that mission, the setting replaces the auto-merge of the project |
| `archive_mission` | writes | Hide a mission from the board and from `list_missions`. Only an owner or an admin can archive a mission |
| `unarchive_mission` | writes | Show an archived mission on the board again |
| `set_mission_disposition` | writes | 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 |

### Projects and proof

| Tool | Kind | What it does |
| --- | --- | --- |
| `list_projects` | reads | The projects that the token can reach |
| `get_project` | reads | The configuration and connections of one project |
| `update_project` | reaches outside SHIP | Change the name, status, auto-merge, issue code, default sandbox or connections of a project |
| `list_artifacts` | reads | The proof that a run produced, such as test traces and screenshots |
| `get_artifact` | reads | One artifact, with a link to open it |

### Scheduled tasks

| Tool | Kind | What it does |
| --- | --- | --- |
| `list_scheduled_tasks` | reads | The missions that a project runs on a schedule |
| `get_scheduled_task` | reads | One scheduled task, with its schedule and prompt |
| `create_scheduled_task` | writes | Add a mission that runs on a schedule |
| `update_scheduled_task` | replaces | Change the schedule or prompt of a scheduled task, or disable it |
| `run_scheduled_task` | reaches outside SHIP | Run a scheduled task now, outside its schedule |
| `list_scheduled_task_runs` | reads | What past runs did, and what they cost |
| `list_scheduled_task_templates` | reads | Templates that you can copy to start a scheduled task |
| `delete_scheduled_task` | removes | Delete a scheduled task and its run history. Missions that the task started continue |

### MCP servers for your agents

| Tool | Kind | What it does |
| --- | --- | --- |
| `list_mcp_servers` | reads | The servers that the MCP file of a project declares, each with its binding and status |
| `list_mcp_bindings` | reads | Each binding in the projects of your organization, so you can see where each credential is used |
| `bind_mcp_server` | replaces | Choose the agents, transport, approved tools and credential for one server |
| `unbind_mcp_server` | removes | Remove a binding and delete its credential |
| `refresh_mcp_server_tools` | removes | Read the current tool list of the server, so that you can approve tools |
| `start_mcp_server_oauth` | reaches outside SHIP | Get a sign-i