Connect your AI assistant to Fotogenic workflows
Use Fotogenic MCP to send product assets, start generation jobs, check account state, and return finished output links inside an assistant workflow.
- Codex
- Claude Code
- Cursor
- ChatGPT
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.
How it works
From assistant request to Fotogenic output.
-
Step 1
Connect the client
Add the remote MCP server in a supported client.
-
Step 2
Check permissions
Confirm account access, available tools, and generation permissions.
-
Step 3
Send product context
Provide product assets, generation intent, and review context.
-
Step 4
Generate and retrieve results
Start supported jobs and return final asset links.
Compare
Use the app, plugin, or MCP for the right job.
MCP is for assistant-driven workflows, not a replacement for every Fotogenic interface.
| Interface | Best use | Good fit |
|---|---|---|
| Web app | Create manually | Visual work |
| WordPress plugin | Work in WooCommerce | Store teams |
| MCP | Use an assistant | Automation |
| BrandDNA | Reuse brand context | Consistency |
Where MCP helps the Fotogenic workflow.
Keep MCP practical: connect tools, prepare context, start supported jobs, and bring results back for review.
Developer workflows
Use MCP where an assistant can prepare context, call tools, and return links.
- Tool calls
- Job status
- Result links
Marketing workflows
Let an assistant organize product context before supported generation jobs.
- Product context
- Campaign notes
- Review links
Agency workflows
Use one assistant workflow to support repeated client product tasks.
- Repeatable setup
- Client context
- Human review
FAQ
Fotogenic MCP questions
Common workflow questions.
Fotogenic MCP is the remote Model Context Protocol connection that lets supported AI clients use permissioned Fotogenic tools.
Use Codex, Claude Code, Cursor, ChatGPT, manual setup, or another remote MCP client.
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 MCP tools.
Saved BrandDNA supports MCP workflows.
Only source image video is available where enabled. Do not treat MCP as support for UGC video ads, reference video, or scenario video.
Human review still checks accuracy, rights, brand fit, and final channel choice.
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, check account status, then test one low-risk workflow.
Ready when your next product is
Connect Fotogenic MCP to your assistant workflow.
Use MCP for setup and review.
- Product images
- Campaign outputs
- Brand controls
- WooCommerce ready