How to Use Claude as Your Social Media Manager (With Revive Social)
Revive.Social Editorial The idea of a Claude social media manager sounds like hype, but if your content lives in WordPress, it is now a practical setup, within clear limits. Through Revive Social, our own sharing plugin, and our free Easy MCP AI plugin, Claude can check what is queued to go out, find out why nothing is sharing, and change which of your posts get shared.
Through Revive’s seven abilities, it can’t post updates that aren’t tied to a published WordPress post; the most those abilities can do is queue a share of one published post, through a share ability that stays off until you switch it on. Revive Social shares the WordPress posts you’ve already published, on a schedule you control, and Claude reads and adjusts that machine; drafting and posting brand-new updates across your networks takes a different kind of tool. If what you want most is help writing the posts themselves, our guide to using AI for social media covers that side.
You need WordPress 6.9 or later, Revive Social 9.4.3 or later, a site reachable on the public internet, and any Claude plan, including the free one.
👉 In this post, we’ll connect Claude to Revive Social step by step, run four real prompts and quote what Claude replied, and mark where Claude’s reach ends. Let’s get started!
What a Claude social media manager can do in Revive Social (and what it can’t)
Since version 9.4.3, Revive Social registers seven abilities with WordPress, and Easy MCP AI turns each enabled ability into a tool Claude can call by name. Six switch on during the connect flow below. The seventh, the share ability, can queue a share of one published post to one account, and it stays off until you tick it.
Here is the full map, with the plan each ability needs:
| Ask Claude to | Plan | Shown in this post? |
|---|---|---|
| List your connected accounts (credentials are never returned) | Free | Yes |
| Report the schedule, sharing status, next share time and content filter | Free | Yes |
| List the upcoming shares and the text each account will post (empty while sharing is stopped) | Free | Yes, empty |
| Change which posts qualify: minimum age, keywords in the post title or content, categories and excluded posts | Free, with up to 3 categories or tags and 30 excluded posts on newer installs (post types and maximum age need Pro) | Yes |
| Change an account’s schedule (hours between shares, or fixed days and times) | Business plan or higher | No |
| Edit the text or image of a queued share, or skip it | Business plan or higher | No |
| Preview (dry run) or queue a share of one published post to one account | Free, off until you switch it on (needs edit rights on the post and an active connected account) | No |
| Connect accounts, start or stop sharing, read the Sharing Logs | Not possible through the abilities | n/a |
None of Revive’s seven abilities connects accounts, starts or stops sharing, or reads the Sharing Logs, so plan to do those jobs in the Revive Social dashboard. And a share that does go out is handed to Revive’s sharing cron first; nothing posts instantly.
What you need before you start
The checklist is short:
- WordPress 6.9 or later. The abilities ride on the WordPress Abilities API, which ships in WordPress 6.9.
- Revive Social 9.4.3 or later. That’s the version that added the abilities, and the free plugin (20,000+ active installs), which shares to Facebook Pages and X, covers every change demonstrated in this post.
- Easy MCP AI. Free, and the connect flow below installs it for you.
- A Claude plan. Per Anthropic: “Custom connectors using remote MCP are available on Claude, Cowork, and Claude Desktop for users on Free, Pro, Max, Ultra, Team, and Enterprise plans. Free users are limited to one custom connector.”
- A public website. In the Claude app, your MCP server “must be reachable over the public internet from Anthropic’s IP ranges”, so a site that lives only on your laptop or behind a VPN will not connect.
- An administrator account. Most of the abilities need an administrator account; the share ability works for any user who can edit that post.
How to connect Claude to Revive Social
Three steps, and the first is a single click.
Step 1: Click “Connect with your AI agent”
Open your Plugins screen and find Revive Social. In its row, click Connect with your AI agent. (No Revive Social yet? Install it from the WordPress.org listing first.)
Step 2: Install Easy MCP AI and send your site to Claude
A modal titled Use Revive Social from your AI agent opens. Click Install and activate Easy MCP: the button installs our free connector plugin and switches it on. When the install finishes, the modal confirms that Easy MCP is active and offers Connect to Claude, Connect to ChatGPT and Add to Cursor buttons.
Connect to Claude opens Claude’s add-custom-connector dialog with your site’s name and MCP URL already filled in. Follow the prompts there: click Continue, review the authentication settings Claude detected, click Continue again, then click Add. On Team or Enterprise plans, an Owner or Primary Owner adds the connector to the organization first, and members then connect to it.
One wrinkle: if Easy MCP AI was already on your site before Revive Social, Revive’s row has no Connect with your AI agent link, and Claude starts with zero Revive tools. Use the connect card on the Easy MCP AI dashboard to add the site to Claude if needed, then open Easy MCP AI → Tools → Abilities and enable the six Revive abilities, leaving the share ability off. The screenshot below, from a site where Easy MCP AI’s first-run seed enabled the abilities, shows the same six on and the share ability off.
Step 3: Approve what Claude may do
The first connection ends on a consent page on your own site. Sign in, choose an access level, and click Approve & Continue. The page states the scope plainly: Claude will act on this site as your user, “and never beyond what that account can do.”
For least privilege, use a Custom Easy MCP key that allows the Revive abilities and read access to posts and categories, without the REST API tools; this grant was not tested in the demonstrations below. The defaults are not on your side: in Easy MCP AI 2.3.2’s code, the Revive abilities start unticked (Claude gets no Revive tools until you tick them), REST routes start with read ticked, and core rows such as posts and taxonomies start with write ticked too, so check every row before you approve.
Back in Claude, switch the connector on for a conversation via the + menu, under Connectors.
Four things to ask Claude, and what happened
To show you what this feels like, here are four prompts run through Claude Code, Anthropic’s command-line app, on a local WordPress site running the free Revive Social with no connected social account and no Pro license. Three of the four are the exact prompts Revive Social suggests in its own modal. That connection had full access rather than the Custom grant from Step 3, and wording in the Claude app can differ.
1. “What is scheduled to go out next on each of my connected accounts?”
Claude checked the account list (including inactive ones), the queue and the schedule, then answered:
Nothing is scheduled to go out.
No social accounts are connected to Revive Social. I checked active and inactive accounts and found none.
Sharing is stopped. The queue is empty and there’s no next share time.
With accounts connected and sharing started, the queue ability returns the upcoming shares and the text each account will post, but that case was not run here. Claude also flagged the plan limit unprompted: “Custom per-account schedules need the Pro business plan.”
2. “Only let Revive Social share posts that are at least 30 days old, and skip anything with “giveaway” in the title.”
The prompt says “in the title”, but Revive’s keyword filter matches words in the post title or content. Claude read the current filter first, then saved the change. The 30-day minimum was already the default (“This was already the setting, so it didn’t change.”), and the rest of the filter stayed put: “Only regular posts are eligible, posts older than 365 days are still left out, and posts can be shared again once all of them have been shared.”
One side effect to know before you try it: changing the content filter clears the current sharing queue. Claude flagged it too: “Saving the filter clears the sharing queue, but nothing was lost: sharing is turned off, so the queue was already empty.”
3. “Share posts from my Reviews category too, and leave out Press releases.”
Claude listed the site’s categories to find the right one, then updated the filter: “Press releases posts are now left out of sharing, and Reviews posts can be shared.” Its explanation shows how the filter thinks: “there was no category filter before, so Reviews posts were already eligible. I set the filter to leave out only Press releases.” And for posts sitting in both: “a post filed under both Reviews and Press releases will be left out.”
The change isn’t hidden inside the chat, either. Revive Social’s General Settings screen shows it:
4. “Revive Social has not shared any of my posts. Can you find out why?”
This one is the diagnostic. Claude worked through the schedule, the account list, the queue and the post list, then reported: “I found two problems, and either one would stop sharing completely.” First, “No social accounts are connected.” Second, sharing was stopped, which keeps the queue empty by design.
Both fixes happen in the Revive Social dashboard, since none of the seven abilities connects accounts or starts sharing, and connecting an account means signing in to the network: “you have to log in to each network yourself.” The dashboard shows the same two blockers:
What the abilities cannot see are the network-side errors: none of the seven reads the Sharing Logs, so delivery failures stay in that tab. And when sharing simply stalls, Revive’s own FAQ names a common cause: “Your website Cron might be faulty.” Its fix walkthrough is in the documentation.
Schedules and the queue: Business plan features
Two abilities, schedule changes and queue edits, need the Business plan or higher.
- Schedule changes. Per account: a recurring interval (hours between shares) or a fixed schedule (days of the week plus times in HH:MM, in your site’s timezone).
- Queue edits. Edit the text or image of a queued share, or skip it.
These two were not demonstrated: with no connected account and no Pro license on the site, they are described from Revive’s code and documentation instead. A free site that tries gets Revive’s own answer: “Custom schedules require an active Revive Social Pro business plan.” The same gate covers queue edits, and other free-plan limits come back as Revive’s own error text: a filter with four taxonomy terms returns “Selecting more than 3 taxonomy terms requires Revive Social Pro.” on sites first installed with version 8.5.3 or later.
Those two need the Business plan or higher; Business is $199 for the first year (introductory price, renewals at full price), and Pro plans start at $99 for the first year, but that entry plan doesn’t include them. Both come with a 30-day money-back guarantee.
Keeping Claude on a short leash
The named risk is prompt injection: “Indirect prompt injections occur when an LLM accepts input from external sources, such as websites or files.” The post titles and queued share texts Claude reads come from your site content, which is exactly that kind of input.
The defenses that matter here:
- Least privilege. OWASP’s rule is “Restrict the model’s access privileges to the minimum necessary for its intended operations.” The Custom consent from Step 3 is how you apply it.
- Know what “off” means. Keeping the share ability off is sensible, but switching a tool off removes that tool, not every route to the action. The permission grant is the real boundary, which is why Step 3 recommends a Custom Easy MCP key without the REST API tools.
- Preview before anything posts. Per Revive’s code, the share ability has a dry run that returns the text, link, image and hashtags it would share to that account, and posts nothing; it wasn’t run with a real account here.
- Know the approval switch’s limit. Easy MCP AI’s optional “Ask before destructive actions” pauses the share ability, which is marked destructive. It does not pause the filter, schedule and queue abilities, which declare themselves non-destructive, and the switch is off by default.
- Keep the receipts. Easy MCP AI’s audit log is on by default. You can pause AI access from its dashboard, or revoke the connection under Easy MCP AI → Connections, at any time.
And the cheapest check of all: after any filter change Claude makes, glance at Revive Social’s General Settings, which shows the result as in the screenshot above.
Final thoughts 🧐
Once everything is connected, Claude can handle the routine checks and tweaks: what is going out next, why nothing has shared, which posts qualify. Revive Social still does the sharing, and the jobs none of the seven abilities covers (connecting accounts, starting sharing, the Sharing Logs) stay with you in the dashboard. The connector is free, and so are the reads and filters you saw above.
If you want to go further, our guide to connecting Claude to WordPress covers the connector side in more detail.
What would you ask Claude to check on your site’s sharing first?
Let us know in the comments section below!
