Shipreel, for your
agents too.

A summary written for language models

A plain-text brief of what Shipreel is, the pricing tiers, the page map, and how repo data is handled. No HTML to parse, no marketing to wade through. It is live now and kept in sync with the site.

# the canonical machine summary
curl https://getshipreel.com/llms.txt

View /llms.txt

Generate a reel as a tool call

Shipreel is becoming an MCP server, so an agent can turn a GitHub repo into a launch reel without a browser and without clicking through the dashboard. The planned tool surface:

• list_projects the repos connected to the account
• generate_reel start a render from a repo, returns a job id
• get_reel poll status, fetch the MP4 / GIF / 9:16 / 1:1 cuts
• edit_scene change a scene in plain English, then re-render
• list_reels the reels already rendered

Connecting it will look like this:

# Claude Code / CLI
claude mcp add shipreel --transport http https://mcp.getshipreel.com

# or in an MCP client config
{
  "mcpServers": {
    "shipreel": {
      "url": "https://mcp.getshipreel.com",
      "auth": "oauth"
    }
  }
}

The same actions over REST

A REST API covering the same actions (list, generate, poll, edit) is on the roadmap under the Studio tier. The MCP server is a thin wrapper over it, so anything an agent can do, a script can do too.

Crawlers and agents are welcome

The public pages are open to agents and crawlers. robots.txt allows the marketing site and disallows internal drafts and /api/. The page map lives in sitemap.xml. There is no rate-limit theater here. Be reasonable and identify your user agent.