Saypix for AI clients

Edit photos from your AI client

Connect the Saypix AI image editor through the Model Context Protocol (MCP). Hand your client a photo and an instruction such as “change the background to a sunny beach”, approve the credit cost, and get the edited image back. Ask for another change and it builds on the last result.

Same models as the website · Your existing credits · Failed edits refunded automatically

Connect

Use a client that supports remote MCP over Streamable HTTP with a custom Authorization header, such as Cursor or Claude Code. Server URL:

https://saypix.io/api/mcp

Your MCP key

A key lets your AI client upload photos, spend your Saypix credits on edits, and read your balance and results. It expires after 30 days, and you can have up to five at once. Only give it to clients you trust.

Loading account…

Client configuration

Replace YOUR_SAYPIX_KEY with your key in your client's private MCP settings. This example uses the mcpServers format from Cursor; other clients may use a different format.

{
  "mcpServers": {
    "saypix": {
      "url": "https://saypix.io/api/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_SAYPIX_KEY"
      }
    }
  }
}

Claude Code:

claude mcp add --transport http saypix https://saypix.io/api/mcp \
  --header "Authorization: Bearer YOUR_SAYPIX_KEY"

Keys are personal Bearer keys, not OAuth, so clients that only support OAuth connectors can't sign in. Listing models and estimating cost work without a key.

Six tools

list_edit_models
See the edit models, what each is good at and what an edit costs. No key needed.
estimate_edit_cost
Get the exact credit cost before editing. No key needed.
get_credit_balance
Check the credits left in your Saypix account.
upload_image
Upload a PNG, JPEG or WebP photo. It is screened before editing.
edit_image
Edit the photo with a plain-words instruction, or keep editing an earlier result.
get_edit_status
Follow the edit and get the finished image link and its step page.

From photo to edited image

  1. Ask your client to list the models and check your balance.
  2. Upload the photo and describe the change. Review the cost and approve it.
  3. Your client starts the edit with a unique requestId and checks it every few seconds until the image is ready.
  4. For the next change, your client passes the finished edit's taskId as parentTaskId, so the edit continues from that result.

Example: “Upload ~/Pictures/portrait.jpg to Saypix and change the background to a city street at night. Tell me the cost and wait for my OK.”

Working with photos

Your client needs access to the image file to upload it. The upload tool takes raw base64 PNG, JPEG or WebP up to 3 MiB. A chat attachment alone may not give your client the original file. Clients with shell access can upload a local file with the same key and pass the returned url to edit_image:

curl https://saypix.io/api/upload \
  -H "Authorization: Bearer YOUR_SAYPIX_KEY" \
  -F "file=@photo.jpg"

Credits and results

There is no separate MCP plan. Edits use the same credits, content rules and failure refunds as the website, and every finished edit appears under My edits with its own page. Identical retries with the same requestId are recognised for 24 hours. If a submission times out, check My edits before trying again; a new requestId can create another paid edit.