# lfnovo/content-core [Health: Active]

**Category:** 🔎 Search & Data Extraction  
**Repository:** https://github.com/lfnovo/content-core  
**GitHub Stars:** 185  
**Views:** 5  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/lfnovo-content-core

## Description
Extract content from URLs, documents, videos, and audio files using intelligent auto-engine selection. Supports web pages, PDFs, Word docs, YouTube transcripts, and more with structured JSON responses.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `uvx` (confidence: high):

```json
"mcpServers": {
  "content-core": {
    "command": "uvx",
    "args": ["content-core"]
  }
}
```

## Documentation

## 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.

_Full upstream README: https://allmcps.com/mcp/lfnovo-content-core/readme_

