One asset, every platform: repurpose maps, platform specs, and the film-once-cut-many workflow.
One asset, every platform. The film-once-cut-many engine, with real per-platform adaptation rules.
Disclaimer. Structured repurposing frameworks from documented practice. Platform specs drift; treat numbers as current-practice ranges.
Creators burn out making NEW content daily. The leverage is making ONE strong thing and adapting it correctly for each platform — not reposting the identical file (which the algorithm and the audience both punish). This MCP maps any source asset to every format and gives the exact adaptation rules.
| Tool | What it returns |
|---|---|
get_repurpose_map | For a source (long video, podcast, blog, single short), every format it becomes + how to adapt it |
get_platform_specs | Aspect, length, caption style, hashtags, hook rule per platform (TikTok, Reels, Shorts, carousel, X thread, LinkedIn, newsletter) |
adapt_for_platform | The adaptation rules to reshape content for one platform, and what NOT to do |
extract_atomic_content | The 6 atomic pieces to pull from one asset (pull quotes, clips, stats, steps, story beats, questions) |
get_repurpose_workflow | The film-once-cut-many batch workflow, step by step |
get_full_pack | Everything in one payload |
npx content-repurposing-mcp
{ "mcpServers": { "content-repurposing": { "command": "npx", "args": ["content-repurposing-mcp"] } } }
Hook it (content-hooks-mcp) → repurpose it (this one) → schedule it (social-media-manager-mcp) → own the audience (newsletter-growth-mcp). 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 content-repurposing-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-content-repurposing-mcp": {
"command": "npx",
"args": [
"-y",
"content-repurposing-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 referencecontent-repurposing-mcpnpmio.github.closermethod/content-repurposing-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.