Skip to main content
MCP server CX Codex

Content — Claude Code MCP server for turning URLs

Content is an MCP server for Claude Code and other IDEs that turns URLs, files and text into transcripts, summaries, translations and PDFs. Agents access it via MCP.

no license ★ 21 updated 2026-10-23

Install into Claude Code · Platform CLI All methods and platforms ↓
claude mcp add --env CONTENT_API_URL=<CONTENT_API_URL> --env CONTENT_MCP_DOWNLOAD_DIR=<CONTENT_MCP_DOWNLOAD_DIR> --transport stdio content -- uvx content-mcp
Open on GitHub

What Content does

Content runs as its own engine under Docker Compose. The backend looks at each source, figures out what it can produce, schedules the job and hands back video, audio, subtitles, a transcript, a translation, chapters, Markdown or PDF. The content-mcp server is one client of that engine, next to the HomeTube and Content Studio web apps, the CLI and the REST API.

The MCP server holds no logic of its own. It forwards tasks to the engine through a shared contract, so Claude Code, Codex, Cursor and the other supported IDEs all see the same features without separate configuration.

You need Docker Compose and the uvx Python package. The engine installs from published images, no cloning required. Files stay in the install folder: database and artifacts under ./data, finished results in ./playground/output. Set CONTENT_DELIVERY_DIR_HOST in .env to deliver to a NAS or media library instead. Without a running engine the MCP server does nothing: it only proxies requests to CONTENT_API_URL.

What it helps with

  • pull a transcript out of a YouTube video
  • build a PDF from a URL or text
  • translate material into another language
  • summarize a long article for an agent
  • hand media files to an agent without manual upload

Example prompts for the agent

  • Transcribe this video and save the file to CONTENT_MCP_DOWNLOAD_DIR
  • Build a PDF from the article at this URL
  • Translate the text in this file to Spanish and return Markdown

How to install Content

Platform CLI

claude mcp add --env CONTENT_API_URL=<CONTENT_API_URL> --env CONTENT_MCP_DOWNLOAD_DIR=<CONTENT_MCP_DOWNLOAD_DIR> --transport stdio content -- uvx content-mcp

Replace <…> with your own values. uvx runs the command named after the package; if the README names another one, use uvx --from content-mcp <command>

Step by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more

Questions about Content

How do I install Content in Claude Code?

First start the engine with Docker Compose: mkdir content && cd content, then curl -fsSLO https://raw.githubusercontent.com/LatentNoise/content/main/deploy/docker-compose.yml, curl -fsSL -o .env https://raw.githubusercontent.com/LatentNoise/content/main/.env.example, docker compose up -d. Then add the MCP server: claude mcp add content -- uvx content-mcp. If the engine is not on localhost, pass environment variables: `claude mcp add --env CONTENT_API_URL=<CONTENT_API_URL> --env CONTENT_MCP_DOWNLOAD_DIR=<CONTENT_MCP_DOWNLOAD_DIR> --transport stdio content -- uvx content-mcp`.

What does Content do?

Turns supported sources — URLs, files and text — into media, transcripts, summaries, translations, images, metadata, Markdown and PDF. The agent sends a job through the MCP server, the engine analyzes the source, plans the work and runs it.

How is Content different from standalone HomeTube?

Standalone HomeTube is a separate container that was not rebuilt on the Content engine. The HomeTube app inside this repository is a new UI on top of the Content engine. Both stay maintained; Content is the platform that carries the same workflow forward.

Similar MCP servers

All MCP servers for Agent setup: memory, context, orchestration →

Project sponsors

Companies that keep this analytics open