content-core
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PROMPT_PATH | No | Path to your custom prompt templates directory | |
| GOOGLE_API_KEY | No | Your Google API key | |
| OPENAI_API_KEY | No | Your OpenAI API key for AI-powered processing and transcription | |
| CCORE_URL_ENGINE | No | Force URL engine selection (auto, simple, firecrawl, jina) | auto |
| CCORE_DOCUMENT_ENGINE | No | Force document engine selection (auto, simple, docling) | auto |
| CCORE_AUDIO_CONCURRENCY | No | Number of concurrent audio transcriptions (1-10, default: 3) | 3 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| extract_contentB | Extract content from a URL or file. Does not require an API key for most sources (web pages, PDFs, documents, YouTube transcripts). API key is only needed for audio/video transcription. Args:
url: URL to extract content from (web page, YouTube video, PDF link, etc.)
file_path: Local file path to extract content from
engine: Optional extraction engine override, routed by input type.
With Returns: Extracted text content |
| summarize_contentA | Summarize content using LLM with optional context. Requires OPENAI_API_KEY (or another LLM provider key) to be configured. Args: content: The text content to summarize context: Optional context to guide summarization (e.g., "summarize as bullet points") Returns: Summarized text |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes—extraction vs. summarization—with no functional overlap. Each tool's parameters are also well-differentiated, avoiding ambiguity.
Both tool names follow the same verb_noun pattern (extract_content, summarize_content), providing a predictable and consistent naming convention.
With only 2 tools, the set is borderline thin for a content-processing server. While both are useful, the count is minimal and could be expanded with additional content operations.
The tools cover the core content workflow of extraction and summarization, but lack other common operations (e.g., translation, keyword extraction) that would round out a comprehensive content toolkit. Minor gaps exist.