Operational layer for running accounts: calendars, cadence, captions, hashtags, reporting.
The operational layer for running accounts — yours or your clients'. Calendars, cadence, captions, hashtags, engagement, metrics, and client reporting.
Disclaimer. Structured social-management frameworks from documented practice. Cadence and metric ranges are current-practice guidance, not platform guarantees.
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.
| Tool | What it returns |
|---|---|
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 |
npx social-media-manager-mcp
{ "mcpServers": { "social-media-manager": { "command": "npx", "args": ["social-media-manager-mcp"] } } }
Runs on top of content-hooks-mcp (post copy), content-repurposing-mcp (feed the calendar), and personal-brand-mcp (positioning). Full catalog: MCP Hub
Elisabeth Hitz — 10+ years enterprise sales, reverse-engineered for creators.
License: MIT
Source-derived launch command. Check the maintainer’s required arguments and credentials before running:
npx -y social-media-manager-mcpMerge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.
{
"mcpServers": {
"io-github-closermethod-social-media-manager-mcp": {
"command": "npx",
"args": [
"-y",
"social-media-manager-mcp"
]
}
}
}Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.
Claude Desktop setup referencesocial-media-manager-mcpnpmio.github.closermethod/social-media-manager-mcp works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.
~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.~/.cursor/mcp.jsonRestart Cursor for changes to take effect..vscode/mcp.jsonReload VS Code window for changes to take effect.~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect..mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.