MCP image and video generation for marketing teams

Give the team a bounded MCP tool sequence

Treat MCP as an execution layer for an approved campaign brief, not as the brief owner. A marketing lead should lock the audience, placement, aspect ratio, visual constraints, source rights, and approver before a generation request reaches the tool layer. The agent can then discover models, inspect the balance, start one generation, wait for its status, and retrieve the completed output without hiding those stages inside one opaque instruction.

The current @offlinecreator/mcp 0.1.2 package documents nine separate tools for model discovery, balance, generation, image upload, status, polling, output retrieval, cancellation, and recent-job listing. That published tool list does not include top-up purchase or Checkout creation tools, so account funding remains outside the MCP action set a connected agent can call.

Plan against published account limits, not an assumed team tier

The public pricing page currently shows Starter with 800 monthly credits and one concurrent generation, Creator with 2,200 credits and two concurrent generations, and Pro with 6,000 credits and four concurrent generations. It does not display a Team or Enterprise tier. A marketing department should therefore budget from the published plan it can actually buy and ask OfflineCreator directly about any procurement, shared-account, seat, permission, or consolidated-billing need that the page does not document.

Concurrency is an operational ceiling, not a reason to launch every campaign variant at once. Estimate the proof set from the live model costs, reserve room for failed creative directions, and schedule parallel jobs within the chosen plan's published limit. The same account credit balance and per-model costs apply across the web Studio, MCP, CLI, and API, so switching interfaces does not create a separate marketing allocation.

Starter

800 credits per monthOne concurrent generation on the currently published monthly plan.

Creator

2,200 credits per monthTwo concurrent generations on the currently published monthly plan.

Pro

6,000 credits per monthFour concurrent generations on the currently published monthly plan.

Review a proof set before requesting campaign variants

Start with one representative deliverable for the hardest placement: for example, a square launch concept with the product position, negative space, palette, and prohibited elements written into the brief. Review composition, source fidelity, legibility risk, brand fit, and the editing work still required. Generated text, logos, claims, prices, and legal copy should remain downstream review items rather than acceptance criteria inferred by an agent.

The current catalog separates text-to-image, text-to-video, and image-to-video and publishes model-specific costs from 1 credit for FLUX Schnell to 96 credits for Veo 3.1 Fast. Those catalog labels and costs help a team choose a proof route; they are not comparative quality measurements. Keep each accepted output with its prompt, model, workflow, intended placement, reviewer, and decision so later variants have a traceable creative basis.

Use this workflow when one owner can control spend and approvals

This pattern fits concept production where a named operator can connect the account and a human creative owner can accept or reject every proof. It is not evidence that Studio replaces a digital asset manager, project-management tool, brand portal, legal review queue, or enterprise procurement control.

Choose it

A small team needs a repeatable proof workflowUse one accountable operator, one visible credit balance, and named reviewers for each campaign stage.

Avoid assuming

A documented multi-seat workspaceThe public pricing page does not advertise a team tier, seat administration, role-based campaign permissions, or consolidated team billing.

Combine it

Generation plus an existing approval systemKeep briefs, rights records, comments, version decisions, and final publishing approval in the system the marketing team already governs.

Run the campaign as seven reviewable stages

MCP documentation describes tools as model-controlled, schema-defined actions, while the host can expose tool-availability settings, execution approvals, pre-approval rules, and activity logs. Marketing teams should configure those host controls around generation and upload actions; connecting an MCP server is not blanket approval for every future campaign request.

1. Freeze the brief

Name the audience and placementRecord dimensions, approved source media, required exclusions, copy handoff, budget ceiling, and final approver.

2. Inspect models and credits

Choose a workflow before generationRead the live catalog and account balance instead of copying a stale model or cost into a reusable prompt.

3. Generate one proof

Test the riskiest deliverable firstDo not multiply a visual direction across placements until the representative output survives review.

4. Wait and retrieve

Keep status explicitPoll the job, retrieve only a completed output, and preserve its model and workflow disclosure with the review record.

5. Review

Apply human brand and rights checksReject or revise problems with composition, source fidelity, claims, text, accessibility, or downstream edit burden.

6. Expand carefully

Request only approved variantsRespect the plan's concurrency limit and keep placement-specific prompts separate from the approved core direction.

7. Package the decision

Deliver files with provenanceAttach the prompt, model, reviewer, intended placement, and an explicit publish-or-revise decision.

Choose the next page by the team's immediate decision

Open the parent use-case directory when the role or output is still undecided. Use the startup-founder playbook for founder-led launch production, or the design-exploration page when the team needs to compare visual directions before building a campaign proof. These routes narrow the next action without implying that one workflow covers every marketing function.

Evidence boundary for marketing-team claims

The latest last30days retrieval returned community and web items, but none substantiated OfflineCreator adoption, reliability, speed, collaboration quality, or campaign outcomes among marketing teams. Adjacent anecdotes included an r/ClaudeAI question about MCP servers for image and video generation and a seven-point Show HN post about another product's MCP video editor; both remain qualified adjacent observations only.

In this page's summary, “private media” has a limited meaning: Studio stores generation media privately and does not make it publicly listable by default, unless the account holder chooses to publish a generation to the Community gallery. It does not mean on-device processing or that media never reaches another service. The current privacy policy says Studio sends the prompt, settings, and any source media to fal.ai for the selected cloud model and uses Cloudflare for private media storage.

Accordingly, this page relies on current first-party pages for plans, concurrency, models, costs, and package behavior. It does not infer team seats, shared workspaces, approval roles, service levels, output performance, or return on ad spend. Any marketing organization that needs those capabilities should verify them directly before procurement rather than treating a role-oriented workflow as a product commitment.