content-repurposing-mcp
# Content Repurposing MCP
**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.
## Why This Exists
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.
## 6 Tools
| 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 |
## Install
```bash
npx content-repurposing-mcp
```
```json
{ "mcpServers": { "content-repurposing": { "command": "npx", "args": ["content-repurposing-mcp"] } } }
```
## The Family
Hook it ([content-hooks-mcp](https://github.com/closermethod/content-hooks-mcp)) → **repurpose it (this one)** → schedule it ([social-media-manager-mcp](https://github.com/closermethod/social-media-manager-mcp)) → own the audience ([newsletter-growth-mcp](https://github.com/closermethod/newsletter-growth-mcp)). Full catalog: [MCP Hub](https://elisabethhitz-mcp.netlify.app)
## Built By
[Elisabeth Hitz](https://www.linkedin.com/in/elisabethhitz) — 10+ years enterprise sales, reverse-engineered for creators.
License: MIT
TDQS
Scored across 6 tools
Each tool has a distinct purpose: adapting for a platform, extracting atomic content, getting full context, platform specs, repurpose maps, and workflows. However, `get_full_pack` aggregates outputs of other getters, causing minor potential confusion.
All tools follow a `verb_noun` pattern with snake_case. Most use `get_`, but `adapt_for_platform` and `extract_atomic_content` use different verbs, which is acceptable. Naming is clear and predictable.
With 6 tools, the server is well-scoped for content repurposing guidance. Each tool covers an essential aspect without redundancy or bloat.
The tool set covers the full lifecycle: breaking down content (extract_atomic_content), platform adaptation (adapt_for_platform, get_platform_specs), repurpose mapping (get_repurpose_map), and workflow (get_repurpose_workflow). No obvious gaps.