Integrate Cherry Shot with Claude and Cursor via MCP

Connect Cherry Shot’s remote MCP server to Claude Desktop, Claude Code, Cursor, or any MCP client and generate product shoots and video ads by chatting.

Cherry Shot ships a remote Model Context Protocol server, so you can generate product photography and video ads directly from any MCP-compatible client — including Claude Desktop, claude.ai, Claude Code, and Cursor. The server is a thin, fully-supported layer over the Cherry Shot REST API: it uses the same API key, the same credit balance, and the same rate limits you already have.

Server details

Property	Value
URL	https://kyliwpyuseadbwawnsyd.supabase.co/functions/v1/mcp
Transport	Streamable HTTP
Auth	Authorization: Bearer cs_your_key

Add to Claude

Claude Desktop / claude.ai

1. Open Settings in Claude Desktop or claude.ai.
2. Navigate to Connectors → Add custom connector.
3. Paste the MCP URL above into the server field.
4. Add your Cherry Shot API key as a bearer token in the authentication field.
5. Save — Claude will discover the available tools automatically.

Claude Code

Run the following command in your terminal, replacing cs_your_key with your real API key:

claude mcp add --transport http cherry-shot \
  https://kyliwpyuseadbwawnsyd.supabase.co/functions/v1/mcp \
  --header "Authorization: Bearer cs_your_key"

Claude Code will confirm the server was added and list the discovered tools.

Available tools

Once connected, your MCP client can invoke the following tools on your behalf:

Tool	What it does
get_credits	Return your current credit balance.
list_models	List both preset and your own custom models available for with-model shoots.
create_shoot	Start a new product-photography shoot and return a shoot ID.
get_shoot	Poll the status of a shoot; returns image URLs when generation is complete.
create_video	Start a video ad using one or more image URLs from a completed shoot.
get_video	Poll the status of a video; returns the MP4 URL when rendering is complete.

Example conversation

Here is what a typical back-and-forth looks like once Cherry Shot is wired up as an MCP server:

You: Generate an editorial 4-shot set for this product: https://example.com/bottle.jpg

Claude: (calls create_shoot with your image URL and style preferences, then polls get_shoot until the images are ready, and returns the four image URLs inline)

You: Great — make a 10-second 720p video ad from the first two images.

Claude: (calls create_video with those two URLs, polls get_video until rendering completes, and returns the MP4 link)

You can iterate, change styles, or request additional shots all in the same conversation thread without leaving your AI client.

The MCP server enforces the same authentication, rate limits, and credit charges as the Cherry Shot REST API — it is a friendlier front door to the same engine. Any credits spent through MCP appear in your dashboard exactly as REST API usage would.