What is the key difference between Content Core and Agent Search MCP?

Content Core belongs to the Search & Data Extraction category with local stdio execution, while Agent Search MCP belongs to the Search & Data Extraction category with local stdio execution.

How do I install Content Core or Agent Search MCP in Claude Desktop or Cursor?

Copy the mcpServers JSON configuration snippet provided on this page into your claude_desktop_config.json or ~/.cursor/mcp.json file and restart your AI client.

Are Content Core and Agent Search MCP free or paid?

Content Core operates under a Free / Open Source model (API Key required). Agent Search MCP operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

Content Core lists 5 tools with 3 views and 171 GitHub stars. Agent Search MCP lists 7 tools with 4 views and 108 GitHub stars.

Can I use both Content Core and Agent Search MCP together in the same MCP host?

Yes! MCP hosts like Claude Desktop, Cursor, Windsurf, Cline, and VS Code support configuring multiple servers under the mcpServers object simultaneously.

Side-by-Side Model Context Protocol Comparison

Content Core vs Agent Search MCP

In-depth architectural comparison of the Content Core and Agent Search MCP MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

At a Glance & Executive Verdict

Content Core

Search & Data Extraction · Local stdio

Quality: 55/100 (Good) | Auth: API Key required

Agent Search MCP

Search & Data Extraction · Local stdio

Quality: 68/100 (Great) | Auth: No auth required

Verdict Summary: Choose Content Core if you need specialized Search & Data Extraction tools running via a local process. Choose Agent Search MCP if your workspace requires Search & Data Extraction integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

Choose Content Core when:

You need dedicated capabilities in the Search & Data Extraction domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (Free / Open Source).
Primary tools included: URL, file, and text extraction, PDF, office, ebook, and markup support, Audio and video transcription.

Explore Content Core Details

Choose Agent Search MCP when:

You need dedicated capabilities in the Search & Data Extraction domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Primary tools included: free_search, free_search_advanced, free_extract.

Explore Agent Search MCP Details

Feature & Specification Comparison

Specification	Content Core lfnovo Search & Data Extraction	Agent Search MCP lennney Search & Data Extraction
Summary	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.	Free multi-engine MCP search server — 8 free engines (DDG, Sogou, Bing, Baidu, Wikipedia, Startpage, Yandex, Mojeek), waterfall progressive search, multi-source verification, content enrichment, news search, language auto-detection, CLI. Zero API keys needed. npx agent-search-mcp
Category & Scope

Tools & Capabilities Breakdown

Content Core Tools (5)

URL, file, and text extraction

PDF, office, ebook, and markup support

Audio and video transcription

Configurable extraction engines

MCP tools for extraction and summarization

Agent Search MCP Tools (7)

free_search

Search the web with an explicit adapter set and bounded fallback. Best for: Quick fact-finding, general search, when date/domain filters are not needed. Not recommended for: Filtered or verified-only results — use free_search_advanced. For full page content — use free_extract. Twelve adapters are selectable; the default request uses DuckDuckGo + Sogou only. Adapters that share one upstream family are tried sequentially on failure and never double-count as corroboration. Explicitly requested optional API adapters run only when credentials are present and the free basket is short or below the quality gate. Results are deduplicated and include separate confidence, relevance, and source-count signals. @readOnly true @idempotent true — makes outbound HTTP requests to configured search engines. Injection detection and SSRF protection active.

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

Content Core Configuration

mcpServers (Claude Desktop / Cursor)

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

Agent Search MCP Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "lennney-agent-search-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "agent-search-mcp"
      ]
    }
  }
}

Frequently Asked Questions

Content Core is categorized under Search & Data Extraction and uses a local stdio subprocess. In contrast, Agent Search MCP belongs to Search & Data Extraction using local stdio subprocess. Select Content Core when you need capabilities focused on search & data extraction and Agent Search MCP when you require tools for search & data extraction.

More alternatives to Content Core More alternatives to Agent Search MCP Search & Data Extraction category hub Canonical compare URL