# Vibe code anywhere, then ship it through review and test

> Keep vibe coding in Claude Code, Codex or any MCP client, then hand the work to SHIP and get back a pull request that passed your CI, a review and a test.

Available now, for founders.

Connect Claude Code, Codex or any MCP client to SHIP once. Then ask it to send the work, and get back a reviewed, tested pull request.

- **For:** Developers and technical founders who build with an assistant all day.
- **Instead of:** Pasting assistant output into a branch and chasing CI and review yourself.

Say this to your coding agent once. It installs the CLI and the SHIP skill, then asks for your SHIP API token.

```
set up https://letsship.ai/SKILL.md
```

## Hand off from the conversation you are in

1. **Connect your assistant once.** Point your coding agent at letsship.ai/SKILL.md, or add https://mcp.letsship.ai/mcp to any client that supports remote MCP servers. Use a token bound to one project.
2. **Ask it to send the work.** Say what you want built. Your assistant files it as a mission with your notes, or hands over a plan it wrote or a pull request it opened.
3. **Get a pull request back.** SHIP builds the change, waits for your CI, then reviews and tests it. Your assistant can read the verdict and the proof and answer with feedback.

## Bring the tools you already like

- **Use any MCP client.** Any client that accepts a remote server URL and an authorization header can file missions, follow them and send feedback. The server keeps no session, so a client can reconnect at any point.
- **Scope every token to one project.** Mint a token for the assistant with only the scopes it needs and bind it to one project, so everything it can reach stays inside that project.
- **Follow up without restarting.** Send feedback as an instruction and the Builder goes back to the open pull request with it. The reply says what the instruction will start.
- **Check the proof each run produced.** Read the trace of a test session or a screenshot of the change working, attached to the mission as an artifact.
- **Leave the conversation whenever you like.** A mission runs for tens of minutes and carries on whether or not the assistant that filed it is still in the conversation.

## Frequently asked questions

### Which assistants work with SHIP?

Claude Code and Codex work through the SHIP skill and CLI, and any assistant that supports remote MCP servers works through https://mcp.letsship.ai/mcp. [MCP server](https://letsship.ai/docs/mcp)

### Does my assistant need my repository?

No. Over MCP your assistant files missions against your project, and SHIP works on the repository in an isolated sandbox.

### What does a mission cost?

One SHIP credit covers one mission of up to 3 agent-hours, and each further 3 agent-hours, or part of them, uses one more credit. Credits come back when a mission ends in failure or needs attention with no pull request. Model usage is billed separately by your own provider.

### How do I get vibe-coded work into production safely?

Vibe-coded work is ready for production once it has passed your CI, a code review and a test of the running change. SHIP waits for your CI, reviews the change and tests it on whatever your assistant hands over, then leaves the pull request for you to merge.

### Does SHIP merge anything without me?

Not by default. Every change arrives as a pull request for you to merge, and auto-merge stays off unless you turn it on for a project or a single mission. [Human in the loop](https://letsship.ai/docs/configuration/human-in-the-loop)

## Send your next idea to production

Connect your assistant once and let every idea come back as a verified pull request.

Source: https://letsship.ai/platform/vibe-coding-for-production