Generate media and speech from Claude or Codex

What you can hand over

MCP (Model Context Protocol) is the standard that lets an AI assistant such as Claude or Codex use another product’s tools. MyChatBot exposes several MCP servers, called surfaces. The one for content is UGC, and its content area generates media.

What the assistant calls over MCP

• Generate media. The docs list no inputs.
• Poll media tasks. Generation runs as a task you can poll; the docs give no task states.
• Text-to-speech, turning a script into spoken audio.

What lives in the app instead

The Content Factory and the Creative studio skills are used by chatting with an agent in the MyChatBot app. The docs do not say they are exposed as MCP tools, so this page keeps them apart.

• Content Factory: a built-in agent. A one-line brief becomes hero images, ad reels or background music, returned as result links.
• Creative studio skills: Photo Looks, Scene Swap, Before/After, Video Ads, Talking Presenter, Reels Factory and Ad Remake.

Example requests

• Image, over MCP. “Generate a square hero image: a matte-black wireless speaker on a light oak desk, soft window light from the left, lots of negative space.”
• Speech, over MCP. “Turn this 30-second script into a voiceover and give me the result.”
• Task check, over MCP. “Check the media task you started and send me the result when it is done.”
• Review first, over MCP. “Plan three variants of this ad image and wait for my go-ahead before you generate anything.”
• Product photo, in the app. In the Content Factory: “Shoot a matte-black wireless speaker in the Golden-Hour Café look, square.”
• Reels, in the app. In the Content Factory: “Give me three reels about the new shoe collection.” The agent shows its plan and total price first.

How it works

1. Connect. Use the MyChatBot plugin for Claude Code and Codex (browser sign-in; it also exposes posting and ads tools), or point your client at https://api.mychatbot.app/api/mcp/ugc?domain=content with an access key from Agents → Tasks → Connect Claude or Codex. The MCP overview has the steps.
2. Ask. Describe the subject, setting, lighting and mood; the docs document no MCP inputs such as aspect ratio.
3. See the plan and the price. In the app, a single image or clip gets a one-line price; higher-quality video or a big batch gets a cost breakdown first. Over MCP, ask the assistant to list what it will generate, and keep your client’s approval prompts on.
4. Approve. Reply “proceed” in the app, or approve the call in your client.
5. Collect the result. In the Content Factory, images take seconds, video about two minutes, and results arrive as links. The docs do not say what a finished MCP media task returns.

Content plans and routines

The docs describe a built-in Weekly content plan routine, run by the Content Director agent: a 7-day posting plan with the format, topic, hook and a paste-ready caption for each day. A routine is a saved multi-step workflow that runs inside MyChatBot. This one produces a plan; the docs do not say it posts.

The docs describe no content-plan tool in the content area. Through the Agents surface, Claude or Codex can help author your own routine whose steps name built-in agents such as the Content Director or the Content Factory. Schedules created over MCP start disabled and you enable them as a separate, approved step; the Agents surface cannot start a live run, so run it once in the app first. A started routine does not pause for approval, so begin with one that only writes the plan.

Stay in control

• Billing. Content generation bills your account balance, and the content area needs a positive balance. In the app, each media job shows as its own line item on the Usage page.
• Cost gates. Starting a generation is the billed step, so keep your client’s approval prompts on. In the app, bigger jobs wait for your “proceed” and Video Ads shows a styled still frame first.
• The content area does not post. Publishing is a separate capability with its own plan requirement and publication approval, and the plugin includes it; see MCP for publishing.
• Keys are credentials. Send the key in the Authorization header only, and keep it out of chats, screenshots and source control. Connect only the content area: without domain the assistant sees every UGC tool, posting and ads included.

The in-app Content Factory documents these typical costs at default quality (mid-2026): a draft-quality photo about $0.05, a video ad about $1.25, a reels pack about $4, a voiceover about $0.07 per 30 seconds. They are not MCP prices: the docs do not tie costs to individual MCP tools, and the agent states the exact price of a job.

What this does not cover

• No models, formats or lengths are promised. For the MCP content tools the docs name no image, video or audio models and give no output formats, resolutions, clip lengths or link lifetimes.
• Video and audio. The docs describe video and music generation in the app’s Content Factory. Which of these the content area returns over MCP is not published, so test with a small request first.
• No published tool list. The docs describe the content area in one line, with no tool names or inputs. Your client’s live tool list is the source of truth.
• Skills over MCP. Whether the Creative studio skills can be invoked from Claude or Codex is not documented.
• Posting. Generating media does not post it. Publishing is a separate capability with its own plan requirement and approval; see MCP for publishing. The list of supported networks is not published, so check in the app.

This page is about connecting Claude or Codex to MyChatBot. The opposite direction, a MyChatBot agent using an external MCP server, is in the MCP integration guide. In-app details: Content Factory and Creative studio.