Skip to main content
BudgetPixel runs a remote Model Context Protocol server that gives AI agents tools to create with your BudgetPixel account: generate images, video, and music, upload reference files, check pricing and credits, and publish finished work to the BudgetPixel community — all from the chat.
There are no API keys involved: you sign in with Google during the connect flow, and the connector acts as your account. Plan credits, model discounts, and free-generation allowances apply exactly as they do on budgetpixel.com.
Generation, uploads, and posting through MCP require the Premium, Pro, or Ultra plan — the same plans that include the developer API. Any account can connect and browse the model catalog; agents on other plans get a clear upgrade notice when they try to generate.
BudgetPixel exposes two MCP endpoints. This page documents the product server at mcp.budgetpixel.com/mcp — the one that creates images, video, and music with your account. Separately, this documentation site hosts a docs-search server at docs.budgetpixel.com/mcp, giving agents read-only search tools over these docs — useful alongside the API when you want your agent to answer integration questions from the documentation itself.

​
Connect your client

  1. In claude.ai (or the desktop app), open Settings → Connectors and click Add custom connector.
  2. Name it BudgetPixel and paste the server URL:
  3. Click Add → Connect and sign in with Google. Then ask Claude to “generate an image (or video, or song) of … using BudgetPixel”.

​
Available tools

​
Billing

Generations through MCP spend the same credits as the BudgetPixel studio:
  • Your plan’s monthly credits, model discounts, and the Pro/Ultra daily free-models allowance apply automatically.
  • Images are priced per image, video per second by resolution, and music per track — the same published prices as the API. Your agent can check any price up front with list_models.
  • Failed generations are never charged.
  • Publishing a community post costs 10 credits (spam prevention — same policy as the API), and posts are limited to 20 per hour. Posts created this way carry a “via MCP” label for transparency.

​
Try asking

Once connected, prompts like these exercise the full toolchain:
  • “Generate a cinematic portrait of a red fox in falling snow — give me 3 options”
  • “Animate the best one into a 5-second 720p video, gentle camera push-in”
  • “Write and sing a warm folk song about two foxes in the snow”
  • “Post the song to my BudgetPixel feed with the portrait as cover art”
Everything your agent creates is saved privately to your BudgetPixel account — images and videos land in your workshop history, music in your audio studio — so nothing is lost when the chat ends.

​
MCP or the REST API?

MCP server

For AI agents and chat — Claude, ChatGPT, Cursor. OAuth sign-in, no keys, a human in the loop. Best when you are creating, with an agent doing the driving.

Developer API

For applications — API keys, per-model endpoints, full parameter control, webhooks-free polling. Best when your software is creating on a schedule or at volume.
Both surfaces expose the same models at the same credit prices, and both label their creations (via API / via MCP) in your generation history.

​
FAQ

No. You sign in with your BudgetPixel account (Google SSO) during the connect flow — no keys to create or paste. API keys belong to the developer API, which is aimed at building applications.
Premium, Pro, and Ultra. Any account can connect and use list_models; generation, uploads, and posting require an eligible plan. Manage your plan at budgetpixel.com/subscription.
The same catalog as the API — Seedream, FLUX, GPT Image 2, Nano Banana, Qwen and more for images; SeeDance 2.0 / 2.0 Mini for video; Music 2.6, Lyria 3, and Mureka V9 for music. The catalog updates automatically as models launch; list_models always returns the live list with prices.
Everything is saved privately to your account, exactly like studio generations — check your workshop history or audio studio, or ask the agent for get_generation_history. Media links returned in chat are time-limited; your account copies are permanent.
No — the posting tool is instructed to publish only when you explicitly ask, posts cost 10 credits each, and every post is labeled “via MCP” on the feed.