Schedule social media posts with Claude
Add Postozo to Claude as a custom connector. Then ask Claude in plain English to plan, write and schedule posts on your connected channels.
How to connect Postozo to Claude
You need a Postozo account with at least 1 connected channel. Claude connects to Postozo's MCP server at https://app.postozo.com/mcp using OAuth sign-in.
- In Claude, open Customize, then Connectors.
- Click + and choose Add custom connector.
- Name it Postozo and paste
https://app.postozo.com/mcpas the remote MCP server URL. Leave the OAuth fields empty: Claude registers itself with Postozo. - Click Add, then Connect. A Postozo window opens. Sign in and click Allow.
- Start a new chat and ask: "List my Postozo channels". If Claude does not use it, turn the Postozo connector on in the chat's tools menu.
Team and Enterprise plans: an Owner adds the connector once in Organization settings, Connectors, Add, Custom, Web, with the same URL. Members then find it under Customize, Connectors and click Connect to sign in with their own Postozo account.
Plans: custom connectors work on Claude Free, Pro, Max, Team and Enterprise. Free accounts can add 1 custom connector.
No sign-in possible? Claude has no general option to add your own headers, so the fallback is your personal URL https://app.postozo.com/mcp/YOUR_API_KEY with no sign-in. Anthropic recommends OAuth over keys in URLs, so use this only if the sign-in does not work for you, and never share the URL.
Check it works
Ask Claude: "List my Postozo channels." It should answer with your channel names and networks.
What Claude can do with Postozo
Postozo gives Claude up to 30 tools. A normal flow is: list your channels, read the rules of each network, check the post, find a free slot, then schedule it once you say yes.
| Tool | What it does | Changes data |
|---|---|---|
list_channels | List the connected social channels (accounts, pages) with their id, network, name and status. Call this first to get channel ids. | No |
list_networks | List every network this server supports and whether it can be connected. Useful to explain what is possible. | No |
list_customers | List customers. A customer groups channels (agencies use 1 per client). | No |
get_channel_rules | Get the posting rules for 1 channel: max length, media needs, whether comments are supported, and the settings schema (some settings are required, for example a title on YouTube or a board on Pinterest). Read before scheduling to that channel. | No |
find_free_slot | Find free posting times for these channels. Give count to get several times, each on a different day (use it to plan a week). Give after to start from a date, for example next Monday. Uses each channel's posting times (times of day in the user's local time). Returns an ISO date in UTC, or dates when count is given. | No |
check_post | Check a post against every channel's rules without saving it. Returns a list of problems (empty means it is fine). | No |
schedule_post | Create or edit a post for 1 or more channels. Supports drafts, scheduling, posting now, client review, threads with delays, per-channel text, network settings, tags and repeats. Returns the post id, its status and a preview link. | Yes |
list_posts | List posts on the calendar between 2 dates (default: last 7 days to next 30 days). | No |
get_post | Get 1 post with its text per channel, state per channel (queued, published, error...), links to the live posts, errors with a fix, comments and history. | No |
change_post_date | Move a post to a new date and time. | Yes |
schedule_draft | Schedule a saved draft at the time it already has (or right away if that time has passed). Keeps its text, channels and settings. Use the post id from schedule_post or list_posts. Only after the user says yes. | Yes |
list_businesses | List the businesses in this workspace (each client of an agency is 1 business; channels without a client belong to the workspace itself), with their channels, how complete each business profile is, and whether the client approves posts. Call this before planning or writing for businesses. | No |
get_business_profile | Read 1 business profile: what it does, audience, area, website, what to promote now, topics, tone, words to use and avoid, hashtags, language, posts per week. | No |
update_business_profile | Save facts about a business so every future post uses them, for example a new offer, an event, opening hours, a new product, the tone, or how many posts per week. Only the fields you send change. | Yes |
fill_profile_from_website | Read a business website and fill the empty fields of its profile (what it does, audience, area, tone, offers, topics, hashtags, language). Fields that already have text are kept. | Yes |
plan_posts | Plan and write posts for 1 or many businesses at once and save them as DRAFTS (nothing goes live). Uses each business profile, its channels, its posting times and its recent posts; the user does not need to give ideas. Runs in the background; the app shows the progress and a summary with Schedule buttons. Use it for a week, a month, several posts, or more than 1 business. | Yes |
get_plan | Progress and summary of a plan: per business, how many posts, how many still drafts, scheduled or waiting for the client, and problems such as posts that need a photo. | No |
schedule_plan | Schedule the drafts of a plan at their planned times (all businesses, or 1). Clients that approve posts get them for approval. Only after the user says yes. | Yes |
add_plan_photos | Make an AI photo for every draft of a plan that needs one (Instagram and other photo networks) and attach it, using the photo idea written for each post. Uses 1 image credit per photo. Runs in the background. | Yes |
discard_plan | Delete the drafts of a plan that were not scheduled (all businesses, or 1). Only after the user says yes. | Yes |
retry_post | Retry the channels of a post that failed or could not be confirmed. Only use after the user confirms the post is not already live. | Yes |
delete_post | Delete a post from the calendar. Posts already live on a network stay live there. | Yes |
upload_media_from_url | Import an image or video from a public URL into the media library. Returns a media id to use in schedule_post. | Yes |
list_media | List files in the media library. | No |
list_tags | List tags used to label posts. | No |
get_analytics | Get account statistics for 1 channel from its network (7, 30 or 90 days). Some networks do not share statistics. | No |
get_post_analytics | Get statistics for 1 published post on 1 channel. Use the per-channel post id from get_post (channels[].root.id). | No |
get_workspace_stats | Counts from this workspace: posts by state, published posts per channel, and short link clicks. | No |
run_channel_tool | Run a network helper for 1 channel, for example list Pinterest boards, Reddit flairs or YouTube playlists, to fill a setting. get_channel_rules lists the tools for each channel. | No |
generate_image | Create an image with AI from a description and save it to the media library. Uses 1 image credit. Returns a media id. Only when AI images are turned on for your workspace. | Yes |
The server also offers 2 ready prompts: plan_week (plan 5 posts for the next 7 days about a topic) and repurpose (turn a link or text into 1 post per channel).
Example prompts
- "Plan 5 LinkedIn posts for next week about our new pricing. Show me a table first, then save them as drafts."
- "Here is our blog post link. Turn it into 1 post per channel, following each network's rules, and schedule them at free times this week."
- "Which of my posts failed this month, and why? Suggest a fix for each."
- "Compare how my Instagram and Facebook channels did in the last 30 days."
- "Move everything scheduled for Friday to Monday at the same times."
- "Write an X thread from these notes and send it to my client for approval."
Safety and control
- 17 of the tools only read. The 13 that change data (schedule_post, change_post_date, schedule_draft, update_business_profile, fill_profile_from_website, plan_posts, schedule_plan, add_plan_photos, discard_plan, retry_post, delete_post, upload_media_from_url and generate_image) are marked as write tools, so Claude can ask you before it runs them.
- The server tells the AI to confirm the text, channels and time with you before it schedules or publishes.
- Ask for drafts ("save as drafts") or for client review ("send for approval") when you want a human to check first.
- A post is never sent twice. If Postozo cannot confirm a post went live, it marks it "could not confirm" instead of retrying on its own.
- Remove access any time in Postozo under Settings, Approved Apps, or by creating a new API key.
Technical details: MCP server reference, with every tool and its inputs, and the developer docs.
Sources
Can Claude schedule posts with Postozo?
Yes. After you add Postozo's MCP server, Claude can list your channels, check each network's rules, find free times and create drafts, scheduled posts or posts for client approval.
Do I need a paid Claude plan?
No. Claude Free can add 1 custom connector. Pro, Max, Team and Enterprise can add more.
Does it work in Claude Desktop and on my phone?
Yes. The connector is added to your Claude account and runs from Anthropic's cloud, so it is available where you use Claude.
Why does Claude ask before scheduling?
Write tools are marked as such, and Postozo asks the AI to confirm text, channels and time with you first.
Does it cost extra?
No. The API and MCP server are included in every Postozo plan. Claude has its own plans and limits.
Post to each network from Claude
Claude for Facebook
posts on your Facebook Pages
Claude for Instagram
Instagram posts, carousels, Reels and Stories
Claude for LinkedIn
LinkedIn profile and Company Page posts
Claude for X
posts and threads on X
Claude for TikTok
TikTok videos and photo posts
Claude for Google Business Profile
Google Business Profile updates, offers and events
Connect Claude to Postozo
Start a 7-day free trial, connect your channels, then add the server.
7 day free trial. No card needed.