How to use AI assistants (MCP) to plan and schedule your social media

Many people already use an AI assistant to brainstorm post ideas. The trouble starts afterwards: you copy the text, open your scheduling tool, paste it, fix the formatting, pick a time, then repeat for every network. The assistant helped with the easy part and left you the admin.

MCP changes that. With an AI assistant that supports MCP, you can ask for a week of posts and have them land as drafts in your own calendar, in your own style, ready for you to review. This guide explains what MCP is in plain terms, how to connect it without giving away more control than you want, and how to run your planning in one short conversation each week.

What MCP is, in plain terms

MCP (Model Context Protocol) is an open standard that lets an AI assistant use tools provided by other apps. An app publishes an MCP server: a list of actions the assistant may call, such as "create a draft" or "schedule a post". You add that server to your assistant as a connector, sign in, and approve what it may do.

From then on, when you ask the assistant something like "put three LinkedIn drafts in my calendar for next week", it calls those actions for you instead of only answering in text. Nothing is shared beyond what the connection allows, and you can disconnect it at any time.

Connecting ProPost to your assistant

The setup takes a few minutes and you only do it once. The MCP page has the exact steps for each kind of assistant, but the shape is always the same:

1. In ProPost, open Settings and copy your MCP server address.
2. In your assistant, add it as a new connector.
3. Sign in to ProPost when the assistant asks, and choose what this connection may do.
4. For tools that take a header instead of a sign-in, create an API key in the same settings page and give it its own level.

Connecting an assistant is part of the Pro and Premium plans (see pricing). Your plan's limits apply to everything the assistant does, exactly as if you were clicking the buttons yourself.

Choose the right level of autonomy

This is the most important decision, and you make it per connection. ProPost offers three levels:

• Drafts only. The assistant writes and edits drafts. You review and schedule them in ProPost.
• Schedule. It can also schedule posts and add them to your queue. You can still cancel anything before it goes out.
• Publish. It can also publish immediately. Posts go public with no review, so this is full autopilot.

Start with drafts only. For the first few weeks you want to see how the assistant interprets your requests, whether the tone holds, and how it handles each network. Move to schedule once you trust the output and you have a habit of checking the calendar. Keep publish for narrow cases, like a dedicated key used by a workflow you built and tested yourself.

You decide what gets published. The autonomy level is how you say it once, instead of every time.

What you can ask it to do

Once connected, the assistant can use the same building blocks you use in the app. The useful ones for planning:

• See your channels and each network's character limit, so it writes to fit.
• Write a draft in your voice, using your saved voices and writing samples (this uses one of your monthly AI drafts), or save text you wrote together in the conversation as a draft without using your allowance.
• Rewrite a draft, check it for phrasing that reads as machine-made, and suggest hashtags.
• Attach an image to a post.
• Schedule a post at an exact time, add it to your queue (the channel's next free slot), or publish now if the level allows it.
• Copy a post to another channel, adapted to that network.
• Read and add to your ideas board, manage your voices, read or change your posting schedule, suggest posting times and report on channel stats.

A weekly planning workflow, by conversation

The trick is to treat the assistant like a sharp colleague who knows your tools but not your week. Give it context first, then ask for options, then decide. Here is a sequence that works.

1. Start from what already exists

Asking for suggestions before drafts keeps you in charge of the topics. It also grounds the plan in your own results rather than generic advice. If you want to go deeper on timing, read how to find your own best time to post.

2. Draft with constraints

Constraints beat adjectives. "Make it engaging" gives the assistant nothing to work with; a length, an opening, a structure and an ending do. For how one idea should change from network to network, see how to repurpose one post for LinkedIn, Instagram, TikTok and X.

3. Check before you place

4. Place them in the calendar

On a drafts-only connection this last step simply waits for you in ProPost. On a schedule connection the posts take their slots, and you can still move or cancel them from the calendar.

Prompting tips that make a real difference

• Name the voice and the channel. "Use my Founder voice for the company page" is clearer than hoping it guesses.
• Ask for two or three options for openings or angles, then pick one. Choosing is faster than rewriting.
• Give it facts it can't know. A number from your project, a client's permission, an event date. The assistant can only be specific if you are.
• Say what to avoid. No emojis, no hashtags on LinkedIn, no exclamation marks: whatever matches how you actually write.
• Ask it to show the result before scheduling when you're on a schedule connection. One extra message saves an awkward post.
• Preview the format. Line breaks and length read differently on each network; the post preview tool shows how a draft will look.

The Monday 20-minute session

Here is a routine you can run every week. It works best on a drafts-only or schedule connection.

1. Minutes 0 to 5: review. Ask for last week's channel stats and which post did best and why. Note one thing to repeat.
2. Minutes 5 to 10: choose. Ask for three topic suggestions from your ideas board and the week ahead. Pick two, add a fact or story to each.
3. Minutes 10 to 15: draft. Have it write each one for your main channel in the right voice, then copy them to your other channels.
4. Minutes 15 to 20: check and place. Run the check, read every draft yourself, then queue them or approve them in ProPost.

Twenty minutes is enough because the assistant handles the mechanical parts. Your time goes to the two things only you can do: choosing what is worth saying and making sure it sounds like you.

Limits and safety

• Your plan's limits still apply. AI drafts, scheduled posts and channels count the same whether you or the assistant uses them.
• Read before it goes out. Assistants can misread a request. A quick look at the calendar each week catches most surprises.
• One key per tool. Give each workflow or editor its own API key with its own level, so you can disconnect one without touching the others.
• Disconnect what you don't use. Settings shows when each connection was last used; remove anything idle.

Used this way, an AI assistant doesn't replace your judgment. It removes the copy, paste and click work between having an idea and seeing it in your calendar. The full setup, with steps for each kind of assistant, is on the MCP page.