Content Core logo

Content Core

by lfnovo

Extracts and summarizes web pages, documents, media, and text through two MCP tools.

Install Content Core

Pick your client, then add it in one click or paste the config.

STDIOPython
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "lfnovo-content-core": {
      "command": "uvx",
      "args": [
        "content-core"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

We couldn’t confirm it starts correctly

The install command installed and started the server, which then stopped for configuration (such as an API key) that our sandbox does not have — expected for servers that connect to your account.

uvx content-core

No response to initialize.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked .

Overview

lfnovo/content-core provides MCP access to content extraction and summarization across URLs, files, text, audio, and video. Its two tools, `extract_content` and `summarize_content`, return plain text while selecting extraction engines automatically or using configured overrides. Supported sources include web pages, YouTube videos, Reddit posts, office documents, PDFs, ebooks, and common media formats. Reach for it when an agent needs to turn external content into readable text or concise summaries.

Use cases

  • Extract text from a PDF or office document for an agent workflow
  • Summarize a web article with additional context
  • Transcribe audio or video into plain text
  • Retrieve readable content from YouTube videos and Reddit posts

Key features

  • MCP tools for extraction and summarization
  • Automatic URL and document engine selection
  • Support for web, document, audio, and video sources
  • Async Python API and command-line interface
  • Configurable LLM and speech-to-text providers
  • Plain-text tool responses

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked

Recent health check succeeded.

17/17 checks healthy over the last 98d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 16h ago via OSV.dev · content-core (PyPI)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars185Stargazers on the source repository.
Last commit8d agoMost recent push to the default branch.
Install checkRunsOur sandbox started it; it then asked for an API key or config.
Directory activity5 viewsConfig copies, upvotes, and views on AllMCPs.

How Content Core works

What lfnovo/content-core does

lfnovo/content-core exposes content processing through a unified Python package, command-line interface, and Model Context Protocol server. The MCP interface presents two tools: extract_content for converting supported sources into text and summarize_content for producing summaries. Both MCP tools return plain text.

Extraction covers URLs, HTML, YouTube videos, Reddit posts, and a range of document and media files. Document formats include PDF, DOCX, PPTX, XLSX, ODT, ODS, ODP, EPUB, HTML, Markdown, and plain text. Audio support includes MP3, WAV, M4A, FLAC, and OGG; video support includes MP4, AVI, MOV, and MKV.

How it works

The package chooses extraction engines automatically based on the source type. URL processing can use auto, simple, firecrawl, jina, or crawl4ai; document processing can use auto, simple, or docling. These choices can be overridden through configuration.

The MCP process can be launched with content-core mcp, or without a local package installation through uvx content-core mcp. Content can also be processed through the Python async API or CLI. The CLI accepts URLs, files, and standard input, and can emit JSON for extraction commands.

Summarization uses a configured LLM provider. Audio and video transcription use a configured speech-to-text provider, with long audio optionally split into segments and processed concurrently.

Setup and configuration

Install the package with pip install content-core, or use uvx for zero-install execution. A Claude Desktop configuration can launch it with the uvx command and the content-core mcp arguments. External service credentials use their standard environment variables, such as OPENAI_API_KEY, FIRECRAWL_API_KEY, and JINA_API_KEY.

Settings can be passed through ContentCoreConfig, CLI configuration commands, environment variables, or ~/.content-core/config.toml. Resolution order is constructor or command flags, environment variables, the configuration file, and then defaults. Configuration includes extraction engines, LLM and speech-to-text providers, model names, audio concurrency, segmentation, YouTube transcript preferences, and proxy settings.

Tools and capabilities

  • summarize_content: summarizes text with optional context or instructions.
  • Automatic selection of URL and document extraction engines.
  • YouTube transcript handling with language, cookie-file, and proxy configuration.
  • Audio transcription and video processing through configured speech-to-text providers.
  • Plain-text MCP results for direct use by AI clients.

Limitations and notes

Some engines require optional dependencies or external services. Selecting docling without its extra installed raises a configuration error, while automatic document selection can fall back to another engine. Crawl4AI can use local browser mode or a Docker API, and Firecrawl supports custom endpoints for self-hosted or compatible backends.

YouTube requests from cloud hosts, VPNs, or other flagged networks may require an exported Netscape-format cookies file or a residential proxy. Cookies must be refreshed when they expire. Summarization and transcription require compatible provider configuration and credentials for the selected services.

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Content Core

lfnovo/content-core is an MCP server that connects AI clients to URLs, files, text, and media through content extraction and summarization tools. Its main MCP tools are extract_content and summarize_content, returning plain text. It supports web pages, documents, YouTube, audio, and video through automatically selected or configured engines.

Install it with pip or run it without installation through uvx. Use `pip install content-core` for a local package, or launch the MCP process with `uvx content-core mcp`.

It provides `extract_content` and `summarize_content`.

Yes. Claude Desktop can launch it through a server entry using the `uvx` command with `content-core mcp` as its arguments. Provider credentials can be supplied through the configuration environment.

Set the URL or document engine through `ContentCoreConfig`, CLI configuration, environment variables, or the configuration file. Supported URL choices include automatic selection, simple, Firecrawl, Jina, and Crawl4AI; document choices include automatic selection, simple, and Docling.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewContent Core AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/lfnovo-content-core?style=directory)](https://allmcps.com/mcp/lfnovo-content-core)
HTML Embed
<a href="https://allmcps.com/mcp/lfnovo-content-core"><img src="https://allmcps.com/api/badge/lfnovo-content-core?style=directory" alt="Content Core on AllMCPs" /></a>