LinkedIn Content Planner MCP
Pricing
Pay per usage
LinkedIn Content Planner MCP
MCP server that lets an AI agent draft, format and move LinkedIn posts through a review pipeline, while a person comments on and approves every post before it goes live.
Pricing
Pay per usage
Rating
0.0
(0)
Developer
Theona
Maintained by CommunityActor stats
1
Bookmarked
1
Total users
0
Monthly active users
a day ago
Last modified
Categories
Share
An MCP server for planning LinkedIn content with an AI agent. The agent drafts posts, formats them for LinkedIn and moves them through a review pipeline; a person reviews, comments and approves each post in the planner's web app before it goes live — the same shape as reviewing a pull request before it is merged.
Every call is scoped to one workspace, so an agent sees only that workspace's posts.
Tools
| Area | Tools |
|---|---|
| Posts | create_post, list_posts, get_post, update_post_content, str_replace_post_content, set_post_state, set_post_date, delete_post |
| Versions | list_versions, get_version_diff, revert_to_version |
| Review | submit_review, list_reviews |
| Comments | add_comment, list_comments, resolve_comment |
| Attachments | prepare_attachment_upload, attach_file, list_attachments |
| Preview | render_preview |
| Webhooks | create_webhook, list_webhooks, update_webhook, delete_webhook, list_webhook_deliveries |
Posts move through backlog → todo → in_progress → in_review → ready → posted. render_preview shows how a post will look on LinkedIn, and webhooks notify you of post lifecycle events.
Credentials
Two are needed:
- Your Apify API token, in the
Authorizationheader, as for any Apify MCP server. - A planner access key, in the
X-Theona-Api-Keyheader. It opens one workspace as you. Sign in with your Theona account and create the key at linkedin-mcp.theona.app/connect; you can revoke it on the same page.
Claude Code
claude mcp add --transport http linkedin-planner \https://theona--linkedin-content-planner-mcp.apify.actor/mcp \--header "Authorization: Bearer <APIFY_TOKEN>" \--header "X-Theona-Api-Key: <PLANNER_ACCESS_KEY>"
Clients that accept custom headers
{"mcpServers": {"linkedin-planner": {"url": "https://theona--linkedin-content-planner-mcp.apify.actor/mcp","headers": {"Authorization": "Bearer <APIFY_TOKEN>","X-Theona-Api-Key": "<PLANNER_ACCESS_KEY>"}}}}
Costs
Apify bills the platform usage of the Standby run.
Support
Open an issue on this Actor's Issues tab.