Content Repurposing Mcp

io.github.closermethodPublished by GitHub account closermethodv1.0.1Updated Oct 24, 2026

One asset, every platform: repurpose maps, platform specs, and the film-once-cut-many workflow.

VerifiedSTDIODesktop onlyProductivity & WorkflowMedia & Design

Overview

AI-generated overview

A local MCP server that gives an assistant structured frameworks for turning one content asset into adapted posts for multiple platforms.

What you can do
  • Get a repurposing map showing every format a source asset (long video, podcast, blog, short) can become
  • Look up per-platform specs for aspect ratio, length, caption style, hashtags and hook rules
  • Get adaptation rules for reshaping content for one platform, including what to avoid
  • Extract atomic pieces from an asset: pull quotes, clips, stats, steps, story beats and questions
  • Retrieve the film-once-cut-many batch workflow step by step, or all of it in one payload
When to use it
Useful when a creator or marketer wants an assistant to plan how one strong piece of content can be adapted across TikTok, Reels, Shorts, carousels, X threads, LinkedIn and newsletters, rather than reposting the same file everywhere.
Requirements
Runs as a local process via npx from the npm package content-repurposing-mcp; Node.js is needed. No accounts, API keys, environment variables or headers are declared. Desktop-only; not executable in a web client.
Before you install
The README states platform specs drift and should be treated as current-practice ranges, so figures may be outdated. It returns guidance text only and does not publish or schedule anything itself.

Installation

In SourceWeft

  1. Open Content Repurposing Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

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

ToolWhat it returns
get_repurpose_mapFor a source (long video, podcast, blog, single short), every format it becomes + how to adapt it
get_platform_specsAspect, length, caption style, hashtags, hook rule per platform (TikTok, Reels, Shorts, carousel, X thread, LinkedIn, newsletter)
adapt_for_platformThe adaptation rules to reshape content for one platform, and what NOT to do
extract_atomic_contentThe 6 atomic pieces to pull from one asset (pull quotes, clips, stats, steps, story beats, questions)
get_repurpose_workflowThe film-once-cut-many batch workflow, step by step
get_full_packEverything 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) → repurpose it (this one) → schedule it (social-media-manager-mcp) → own the audience (newsletter-growth-mcp). Full catalog: MCP Hub

Built By

Elisabeth Hitz — 10+ years enterprise sales, reverse-engineered for creators.

License: MIT

Source: README.md at commit 3ed6292

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.1LatestSep 16, 2026

Score

40% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.