Operational layer for running accounts: calendars, cadence, captions, hashtags, reporting.
Operational layer for running accounts: calendars, cadence, captions, hashtags, reporting. That is what the social mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.
Content-hooks writes the post and personal-brand sets the positioning — but someone has to RUN the account: plan the calendar, keep the cadence, write the captions, manage the community, read the metrics, and report to the client. That's the SMM's actual daily job, and this MCP is the operating system for it.
Installation goes through your MCP client rather than a global install: point it at social-media-manager-mcp on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
The server publishes 8 tools. What each one is for:
get_posting_cadence — Frequency, best windows, key note per platform (TikTok, IG, LinkedIn, X, YouTube)build_content_calendar — Pillar-first weekly shape, batch-by-task rule, conversion ratioget_caption_framework — Caption structures by goal (hook-expand-CTA, story, list, question-seed)get_hashtag_strategy — Count, mix, and note per platformget_engagement_playbook — First-hour replies, threading, pinned comments, DMs, outbound engagement, handling negativityinterpret_metric — What each metric means + what to do (reach, engagement rate, saves, shares, retention, growth, profile-visit-to-follow)get_client_report_template — The 5-part client report + report-on-the-goal ruleget_full_pack — Everything in one payloadPlenty of planning and project tracking servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Social's toolset — get_posting_cadence, build_content_calendar, get_caption_framework and 5 more — is a fair guide to whether it matches your workflow. It is maintained by closermethod; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| get_posting_cadence | Frequency, best windows, key note per platform (TikTok, IG, LinkedIn, X, YouTube) |
| build_content_calendar | Pillar-first weekly shape, batch-by-task rule, conversion ratio |
| get_caption_framework | Caption structures by goal (hook-expand-CTA, story, list, question-seed) |
| get_hashtag_strategy | Count, mix, and note per platform |
| get_engagement_playbook | First-hour replies, threading, pinned comments, DMs, outbound engagement, handling negativity |
| interpret_metric | What each metric means + what to do (reach, engagement rate, saves, shares, retention, growth, profile-visit-to-follow) |
| get_client_report_template | The 5-part client report + report-on-the-goal rule |
| get_full_pack | Everything in one payload |
```json
{ "mcpServers": { "social-media-manager": { "command": "npx", "args": ["social-media-manager-mcp"] } } }Configuration as documented by the project. Restart the client after saving.
Your workspace, on speaking terms with AI — search, read and write Notion pages and databases.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Search and read your Drive — Docs, Sheets and files become context your assistant can actually use.
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Stop letting your assistant hallucinate n8n node parameters — this server hands it the real schemas, templates and validation.