SHIP

SHIP MCP server

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.

Endpoint

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

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:

{

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

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

{

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

Codex. Add this to ~/.codex/config.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:

{

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

{

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

{

"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

Projects and proof

Scheduled tasks

MCP servers for your agents

Agent runs

Preview environments

Credits and notices