In-depth architectural comparison of the Searchcraft MCP Server and Fetch 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
Searchcraft MCP Server
Search & Data Extraction · Local stdio
Quality: 48/100 (Fair) | Auth: API Key required
Fetch MCP
Search & Data Extraction · Local stdio
Quality: 60/100 (Good) | Auth: No auth required
Verdict Summary: Choose Searchcraft MCP Server if you need specialized Search & Data Extraction tools running via a local process. Choose Fetch 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 Searchcraft MCP Server 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 (BYOK (Pay Provider Direct)).
Official MCP server for managing Searchcraft clusters, creating a search index, generating an index dynamically given a data file and for easily importing data into a search index given a feed or local json file.
An MCP server to flexibly fetch JSON, text, and HTML data
Category & Scope
Tools & Capabilities Breakdown
Searchcraft MCP Server Tools (48)
create_index
Create a new index with the specified schema. This will empty the index if it already exists.
delete_index
Delete an index and all its documents permanently.
get_all_index_stats
Get document counts and statistics for all indexes.
get_index_schema
Get the schema definition for a specific index.
get_index_stats
Get statistics and metadata for a specific index (document count, etc.).
list_all_indexes
Get a list of all indexes in the Searchcraft instance.
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).
Searchcraft MCP Server is categorized under Search & Data Extraction and uses a local stdio subprocess. In contrast, Fetch MCP belongs to Search & Data Extraction using local stdio subprocess. Select Searchcraft MCP Server when you need capabilities focused on search & data extraction and Fetch MCP when you require tools for search & data extraction.
Make partial configuration changes to an index schema (search_fields, weight_multipliers, etc.).
update_index
Replace the entire contents of an existing index with a new schema definition.
add_documents
Add one or multiple documents to an index. Documents should be provided as an array of JSON objects.
delete_all_documents
Delete all documents from an index. The index will continue to exist after all documents are deleted.
delete_document_by_id
Delete a single document from an index by its internal Searchcraft ID (_id).
delete_documents_by_field
Delete one or several documents from an index by field term match (e.g., {id: 'xyz'} or {title: 'foo'}).
+36 more tools listed on main page
Fetch MCP Tools (6)
fetch_html
Fetch a website and return its raw HTML content.
fetch_markdown
Fetch a website and return its content converted to Markdown.
fetch_txt
Fetch a website and return plain text with HTML tags, scripts, and styles removed.
fetch_json
Fetch a URL and return the JSON response.
fetch_readable
Fetch a website and extract the main article content using [Mozilla Readability](https://github.com/mozilla/readability), returned as Markdown. Strips navigation, ads, and boilerplate. Ideal for articles and blog posts.
fetch_youtube_transcript
Fetch a YouTube video's captions/transcript. Uses `yt-dlp` if available, otherwise extracts directly from the page. Accepts an additional `lang` parameter (default: `"en"`) to select the caption language.