Connect Claude Desktop, Claude Code, or any MCP client to your RecurPost account. Schedule posts, fill libraries, and pull posting history from one conversation.
No credit card required
The RecurPost MCP server is an official npm package (recurpost-mcp) that runs on your own machine. Your assistant calls 9 RecurPost tools from plain-language requests.
With RecurPost MCP Server
Schedule posts to the minute from a Claude chat
9 tools: accounts, posting, libraries, history, AI
Per-platform captions and controls stay intact
Draft with AI and schedule in the same conversation
API key stays on your machine, never in the chat
850+ post-failure error types surfaced
Without RecurPost MCP Server
Copy-paste every draft from Claude into a scheduler tab
Re-type platform variants for each network by hand
Paste client credentials into third-party GPT plugins
No posting history where the drafting happens
RecurPost’s MCP server sets up in 2 steps: generate an API Password Key in Account Settings, then add one config block to Claude Desktop or one command in Claude Code.
Log in to RecurPost, open Account Settings, and generate an API Password Key. It is separate from your login password.
Output: a key you can revoke without touching your password.
Paste the recurpost-mcp block into Claude Desktop's config file, or run one 'claude mcp add' command in Claude Code.
Output: the server starts locally via npx, nothing to install.
Restart Claude Desktop or Claude Code. The 9 RecurPost tools appear in the assistant automatically.
Output: RecurPost tools ready in the conversation.
Say "schedule these for Tuesday 9am on the client's LinkedIn". The assistant picks the right tool for each request.
Output: posts land in the client’s queue.
The RecurPost MCP server exposes 9 tools. social_account_list and library_list return your accounts and libraries with IDs. post_content publishes now or at a set time. add_content_in_library files posts with live and expiry dates. history_data pulls up to 100 posts per request with engagement metrics.
Also included:
AI text generation with multi-turn refinement across the chat
AI image generation from a text prompt
Connection URLs to add new client accounts
Credential check tool to verify the key works
Images hosted on RecurPost by default, so generated media survives
Both posting tools accept a separate message for each of the 10 networks RecurPost publishes to. The deeper platform fields come through too, so AI-scheduled posts stay platform-native.
GBP CTA buttons plus full Offer fields: dates, coupon code, terms, redemption link
YouTube title, category, tags, privacy, custom thumbnail, made-for-kids flag
TikTok privacy level plus comment, duet, and stitch toggles
Feed, Story, or Reel on Facebook and Instagram; LinkedIn documents; per-platform first comments
Example: schedule a GBP Offer post with a coupon code, redemption link, and end date for 6 locations from 1 Claude conversation.
The email and API key live in environment variables only the local server process reads. The model calls a tool; the server signs the request on your machine and sends it straight to the RecurPost API.
No middleman server holds your keys
The AI model never sees the API key
Key revocable from Account Settings any time
Runs as a local process on your machine
Publish to your client’s Facebook, Instagram, Google Business Profile, and all other connected platforms from one conversation. Posts scheduled through the MCP server land in the same calendars, libraries, and workspaces your team already reviews in RecurPost.
Best Fit
Teams drafting client content in Claude Desktop or Claude Code
Conversational scheduling: draft, refine, and queue in one chat
Ad-hoc reporting: pull history and metrics without opening dashboards
Technical freelancers standardizing on MCP-capable assistants
Not the Best Fit
App-event automation with nobody in the loop (use the Zapier integration)
Bulk migration of hundreds of posts (use CSV bulk upload)
Teams that never work inside an AI assistant
Note: Check the RecurPost Schedule and recycle features to combine the MCP server with the calendar, bulk upload, and content import options in the same scheduling tool.
RecurPost’s Agency plan covers 20 client social profiles without a per-user seat charge. The MCP server itself is free, open source, and works on every plan.
The RecurPost MCP server is an official npm package (recurpost-mcp) that lets MCP-capable AI assistants operate RecurPost. It exposes 9 tools covering account discovery, posting, scheduling, recurring libraries, posting history, and AI content generation.
RecurPost’s MCP server works with Claude Desktop, Claude Code, and any client that supports the Model Context Protocol. The server runs locally, started by the client itself.
Claude schedules RecurPost posts to the minute. The post_content tool takes a date and time in YYYY-MM-DD HH:MM:SS format. Omit the time and the post publishes immediately.
The RecurPost MCP server never uses your login password. It authenticates with an API Password Key passed through environment variables only the local process reads. The AI model never sees the key, and you can revoke it without changing your password.
The RecurPost MCP server accepts a separate message for each of the 10 supported networks, plus Google Business Profile CTA buttons, YouTube metadata, TikTok permission toggles, and per-platform first comments. One request carries a distinct version for every network.
The RecurPost MCP server is free and open source under an MIT license. It works with any RecurPost account, from Starter at $9/month to Agency at $79/month.
