Sofya vs TinySearch

A side-by-side look at the Sofya and TinySearch MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

S
SofyaSearch & Data Extraction · Remote HTTP/SSE
Web search, fetch, extract, and research for AI agents. Markdown output + AI-synthesized answers.39FairAuth: no auth required
TinySearch logoTinySearchSearch & Data Extraction · Local subprocess (stdio)Self-hosted web research for MCP agents: search (SearXNG, with DuckDuckGo fallback), crawl, dense+BM25 rerank, and dedupe into a source-grounded, cited prompt. Local ONNX embeddings by default, or bring an OpenAI-compatible embedding API.56GoodAuth: no auth required

Verdict: choose Sofya for search & data extraction work over a hosted endpoint; choose TinySearch for search & data extraction as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

S
Choose Sofya when

  • You need dedicated capabilities in the Search & Data Extraction domain.
  • You prefer a remote HTTP/SSE transport.
  • Its auth model fits you: No auth required.
Explore Sofya

TinySearch logoChoose TinySearch when

  • You need dedicated capabilities in the Search & Data Extraction domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: No auth required.
Explore TinySearch

Feature & specification comparison

Rows where the two servers differ are marked.

Spec
S
Sofya
TinySearch logoTinySearch
CategorySearch & Data ExtractionSearch & Data Extraction
Quality signal39/100 · Fair56/100 · Good
Install commandConfirmedConfirmed
TransportRemote HTTP/SSELocal subprocess (stdio)
AuthNo auth requiredNo auth required
PricingNot declaredFree
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars—234
Directory activity 0 views 0 installs 0 upvotes 2 views 0 installs 0 upvotes
ToolsNot listedNot listed

Tools & capabilities

Sofya tools

No tool names declared yet. Check the project README from the listing page.

TinySearch tools

No tool names declared yet. Check the project README from the listing page.

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

Sofya

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "sofya": {
      "command": "npx",
      "args": [
        "-y",
        "sofya"
      ]
    }
  }
}

TinySearch

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "marcellm01-tinysearch": {
      "command": "uvx",
      "args": [
        "--from",
        "tinysuite-search[server]",
        "tinysearch"
      ]
    }
  }
}

Frequently asked questions

Sofya is categorized under Search & Data Extraction and uses a remote HTTP/SSE transport. TinySearch belongs to Search & Data Extraction and uses a local stdio subprocess. Pick Sofya for search & data extraction work and TinySearch for search & data extraction.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.

Sofya has no declared pricing — check the project's own site. Auth: no auth required. TinySearch is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add sofya and marcellm01-tinysearch as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Sofya has a quality signal of 39/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. TinySearch has 56/100 (Good) with 2 views, 0 installs and 234 GitHub stars.