Fotogenic MCP

Fotogenic MCP

Connect AI assistants to supported Fotogenic AI account tools so they can help with product context, image jobs, BrandDNA, campaign assets, job status, and final asset links.

  • Codex
  • Claude Code
  • Cursor
  • ChatGPT
  • Any MCP client

What it enables

Let an AI assistant help with Fotogenic AI workflows.

Fotogenic MCP is for controlled assistant work: account checks, product context, asset upload, image generation, BrandDNA, job tracking, and result retrieval.

Compatible clients

Connect Fotogenic AI to the AI clients your team already uses.

Use the Fotogenic MCP endpoint from Codex, Claude Code, Cursor, ChatGPT, manual setup, or any client that supports remote MCP server configuration.

Client setup

Choose the setup path for your AI workspace.

Add the remote MCP endpoint, authenticate with your Fotogenic AI account, then verify available permissions before the assistant starts product content work.

Use Fotogenic AI from Codex.

Connect Codex to Fotogenic MCP when you want an AI coding or operating assistant to help prepare product assets, inspect account status, and run supported generation workflows.

1 endpoint Remote MCP server
What this enables
  • Add https://mcp.fotogenic.ai/mcp as the Fotogenic MCP server.
  • Authenticate with Fotogenic AI through OAuth instead of pasting raw secrets.
  • Ask Codex to check scopes, limits, credits, and feature availability before generating.
Open Fotogenic AI
MCP capabilities

Give the assistant only the Fotogenic tools needed for the job.

Fotogenic MCP exposes permissioned product content functions so an assistant can prepare context, generate assets, check account state, and monitor work without guessing what is available.

Generate product content from assistant workflows.

Use MCP when the assistant already understands the product, audience, campaign, or catalog task and needs to request supported Fotogenic AI outputs.

6 tools Generation workflows
What this enables
  • Image generation
  • Image variations
  • ready for ads Visuals generation
  • Campaign Sets generation
  • Content Kits generation
  • Image based video generation
Start with MCP

MCP in practice

What an AI assistant can do with Fotogenic MCP.

Use these workflows when the assistant should help with production while access, review, and publishing decisions stay controlled.

Tool directory

Every Fotogenic MCP function in plain language.

These are the practical jobs an MCP connected assistant can help with when your account permissions and feature availability allow it.

How it works

From AI client connection to finished asset links.

The workflow keeps setup, permissions, asset upload, generation, and job tracking explicit before any result is used.

  1. Step 1

    Connect the client

    Add the Fotogenic MCP endpoint to the AI client and authenticate through your Fotogenic account.

  2. Step 2

    Check permissions and limits

    Have the assistant verify account status, scopes, feature availability, credits, and pricing hints before acting.

  3. Step 3

    Prepare product context

    Upload references, extract product details, choose BrandDNA, and define the supported output.

  4. Step 4

    Generate and retrieve results

    Run the job, monitor status, then return final asset URLs for human review.

Decision guide

Choose Fotogenic MCP when an AI assistant should help with Fotogenic work.

Use MCP when you want Codex, Claude Code, Cursor, ChatGPT, or another MCP capable assistant to work with supported Fotogenic account tools.

FAQ

Fotogenic MCP questions, answered.

Clear answers for teams deciding where MCP belongs in a Fotogenic AI workflow.

Fotogenic MCP is the remote Model Context Protocol connection that lets supported AI clients work with permissioned Fotogenic AI account tools.

Use Codex, Claude Code, Cursor, ChatGPT, manual setup, or any client that supports remote MCP server configuration.

It can check account status, upload reference assets, extract product details, use BrandDNA where supported, generate supported assets, check job status, and return final asset URLs.

No. Authentication should happen through OAuth in the MCP client. Do not paste raw tokens, cookies, service keys, or account secrets into prompts.

Yes, where your account permissions and feature availability allow image generation through the exposed MCP tools.

Supported workflows can read or apply saved BrandDNA profiles when the account and selected tool allow it.

Only source image video is available where enabled. Do not treat MCP as support for UGC video ads, reference video, or scenario video.

A person should still review product accuracy, brand fit, usage rights, channel fit, and final image choice before publishing.

Use MCP when an AI assistant should help prepare context, run supported workflows, monitor jobs, and hand back ready asset links inside the tools where your team already works.

Connect the client, authenticate through Fotogenic AI, run an account status check, then test one low risk product workflow before scaling.

Ready when your next product is

Connect your AI assistant to the next Fotogenic workflow.

Use MCP to let your assistant help with supported Fotogenic account tools, product context, generation setup, and review steps.

  • Product images
  • Campaign outputs
  • Brand controls
  • WooCommerce ready