# Shipem

> MCP-first deployment for AI-built web apps. Use @shipem/mcp from Claude Desktop, Cursor, or another MCP client, or use the CLI directly.

Shipem deploys web apps with two paths:

- **Shipem-managed:** Log in with GitHub once and deploy without Cloudflare credentials.
- **Direct Cloudflare:** Set `CLOUDFLARE_API_TOKEN` and `CLOUDFLARE_ACCOUNT_ID` to deploy straight to Cloudflare Pages.

MCP tools currently exposed by @shipem/mcp:
- `shipem_login`
- `shipem_deploy`
- `shipem_fix`
- `shipem_status`
- `shipem_logs`
- `shipem_down`
- `shipem_env`
- `shipem_scan`
- `shipem_init`
- `shipem_logout`

MCP resources:
- `shipem://project`
- `shipem://deployments`

Login once with GitHub for the default Shipem flow. If the MCP client cannot finish login in-app, open the returned login URL in your browser and retry.

Framework detection currently covers: Next.js, Astro, SvelteKit, Nuxt, Remix, Gatsby, Vite (React/Vue/Svelte), Create React App, Hono, Express, FastAPI, Flask, Django, generic Node builds, and static HTML.

Deploy URLs are returned by the deployment provider. Shipem-managed deploys and direct Cloudflare deploys do not necessarily use the same hostname.

## Docs

- [Getting Started](https://shipem.dev/docs/index.html.md): MCP-first quick start and CLI entry points
- [MCP Setup](https://shipem.dev/docs/mcp.html.md): Current @shipem/mcp setup, auth flow, tools, resources, and limits
- [CLI Reference](https://shipem.dev/docs/commands.html.md): Current shipem / npx ship-em command reference
- [Supported Frameworks](https://shipem.dev/docs/frameworks.html.md): Auto-detected frameworks and build configuration

## Optional

- [ship-em on npm](https://npmjs.com/package/ship-em): CLI package — npx ship-em
- [MCP server on npm](https://npmjs.com/package/@shipem/mcp): @shipem/mcp for Claude Desktop and Cursor
- [Dashboard](https://app.shipem.dev): Manage deployments, view usage, upgrade plan