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

> Keep vibe coding in Claude Code, Codex or any MCP client. Send the work to SHIP and get back a pull request that passed your CI, a code 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 you get a reviewed, tested pull request.

- **For:** Developers and technical founders who build with an AI assistant all day.
- **Instead of:** Assistant output that you copy into a branch, then fix for 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 work to SHIP from your chat

1. **Connect your assistant once.** Give your coding agent letsship.ai/SKILL.md, or add https://mcp.letsship.ai/mcp to any client that supports remote MCP servers. Use an API token limited to one project.
2. **Ask it to send the work.** Say what you want built, and your assistant files it as a mission with your notes. It can also send 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 results and the proof, and reply with feedback.

## Work from the assistant you already use

- **Use any MCP client.** Any client that takes a remote server URL and an authorization header can file missions, check their status and send feedback. The server keeps no session, so the client can reconnect at any time.
- **Limit each token to one project.** Create an API token with only the permissions the assistant needs. Limit it to one project, so it cannot reach your other projects.
- **Reply with feedback on the open pull request.** Send feedback as an instruction, and the Builder goes back to the open pull request with it. SHIP replies with what the instruction will start.
- **Check the proof from each test.** Each mission has the Tester's proof attached: a trace of the test session, or a screenshot that shows the change works.
- **Close the chat while it runs.** A mission runs for tens of minutes. It continues after you close the chat that started it.

## Frequently asked questions

### Which assistants work with SHIP?

Claude Code and Codex work through the SHIP skill and CLI. 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 only files missions for your project. SHIP works on the repository in an isolated sandbox.

### What does a mission cost?

A mission uses one SHIP credit for up to 3 agent-hours, and one more for each further 3 agent-hours or part of them. If a mission fails or needs attention without a pull request, you get the credits back. Your own provider bills model usage.

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

Vibe-coded work is ready for production once it passes your CI, a code review and a test of the app with the change. SHIP waits for your CI, reviews the change and tests it, then leaves the pull request for you to merge.

### Does SHIP merge anything without me?

No, not by default. Every change comes to you as a pull request to merge. 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)

## Start with one change from your assistant

Connect your assistant once. After that, every change you ask for comes back as a reviewed, tested pull request.

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