Plan, schedule and measure social posts with your AI assistant

What you can ask your assistant to do

MCP, the Model Context Protocol, is a standard that lets an AI assistant such as Claude or Codex use the tools of another product. MyChatBot exposes it as separate servers called surfaces. Posting and post analytics sit on the UGC surface, which is split into areas:

• Posting area: create posts, timelines, best-times and posting frequency.
• Analytics area: post analytics, engagement decay, daily metrics and campaign tree.

Those are the docs’ own one-line descriptions. Read plainly, you can ask your assistant to create and schedule posts, look at timing and posting frequency, and report how published posts performed. Making the media for a post is a separate step, covered in MCP for content.

Scheduled publishing also appears in the in-app Reels Factory skill: three vertical reels with different hooks, a caption for each, optional music, and scheduled publishing to your connected social accounts. Instagram is the one posting network the docs name.

Example requests

These are examples of what to type, not a list of commands. The first three follow docs examples typed to an in-app agent; the last two match what the areas are named for.

• Plan the week. Draft a 5-post content plan for this week and write a caption for each post. This produces text only. Nothing is published.
• Queue three reels in the app. Three reels about the new shoe collection, and queue them on Instagram for Mon/Wed/Fri. In Reels Factory the agent plans first, shows the total price, and you approve each reel after delivery.
• Run a recurring content team. Every weekday at 8am: draft this week’s content plan and delegate the captions to my content agent. In the docs you tell a lead agent in the app, which creates its own schedule and hands the captions to a content agent. A schedule created over MCP starts disabled.
• Read the results. Show how last week’s posts performed, with the daily metrics. This is reading only.
• Ask about timing. When are the best times to post, and how often should we?

How it works

1. Connect your social accounts in MyChatBot first. The docs do not name the screen or the steps, so look for it in the app. Never paste a password or token into the chat.
2. Connect the posting area. Create an access key under Agents → Tasks → Connect Claude or Codex. Then add the address https://api.mychatbot.app/api/mcp/ugc?domain=posting to Claude Code or Cursor, with the key in an Authorization header. Add a second entry with domain=analytics to read results. With the MyChatBot plugin for Claude Code or Codex you sign in through the browser instead of copying a key.
3. Plan, media, approve, schedule. Ask for the plan first. Generate the media as its own billed step. Approve the result. Only then ask for it to be scheduled, and approve that separately.
4. Recurring work becomes a routine. A routine is a saved workflow that runs inside MyChatBot on a schedule. A schedule created over MCP with create_routine_schedule always starts disabled. Enabling it with set_routine_schedule_enabled is a separate step you approve.

Once a routine is enabled it runs inside MyChatBot, and Claude or Codex is no longer in the loop. The Agents surface has no immediate live run, so the first live check happens in the app. Reference: MCP and connectors.

How you stay in control

• Reading is separate from writing. Looking at analytics changes nothing. Creating or scheduling a post is a write, and your client should ask you to review it first.
• Publishing needs its own approval. In the MyChatBot plugin, publishing or scheduling a social post needs a separate publication approval. Approving a media generation does not approve the post.
• Billed generation needs your review. Generation bills your account balance. Reels Factory shows the plan and total price first, while a single image runs with a one-line cost note. The default pack of three reels is about $4, as documented.
• Schedules created over MCP start disabled. Enabling one is a separate step.
• A running routine does not pause. Once enabled, a routine runs every step to the end. There is no approval pause, and writing a publishing step is the authorization. Start read-only or draft-only: a routine that writes a plan and captions and publishes nothing. A dry run is tool-free, so it cannot test real posting.
• Keys are credentials. Keep the access key out of chats, screenshots and source control, and prefer one area per connection so the assistant sees a short, focused tool list.

What the docs do not cover

Posting and analytics are described by area only. Here is what the documentation does not say.

• Networks. No list of supported networks is published. Instagram is named in one example and nothing else is listed. Check in the app which accounts you can connect.
• Formats. No list of post types is published for the posting area. The one documented format is the three vertical reels of Reels Factory.
• Tool names and schemas. None are published for posting or analytics. Your client reads the live tool list when it connects, so ask it what it sees.
• Post state. The docs do not say whether a created post is a draft, is scheduled or goes live, or how to edit or cancel a scheduled post. Ask the assistant to state what a call will do, and approve that.
• Metrics. Engagement decay, best-times, timelines and campaign tree are named but not defined.
• Plans and accounts. Posting and analytics need a paid social plan. Generating media needs a positive balance and no particular plan. The auto-posting step of a scheduled content team is not included in a free trial. Social accounts beyond those included in your plan are billed per account, as documented.
• The Claude app connector. It is documented for sales-assistant setup, not for posting.