In-depth architectural comparison of the Searchcraft MCP Server and Kagimcp 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
Kagimcp
Search & Data Extraction · Local stdio
Quality: 82/100 (Excellent) | Auth: API Key required
Verdict Summary: Choose Searchcraft MCP Server if you need specialized Search & Data Extraction tools running via a local process. Choose Kagimcp 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)).
Searchcraft MCP Server is categorized under Search & Data Extraction and uses a local stdio subprocess. In contrast, Kagimcp belongs to Search & Data Extraction using local stdio subprocess. Select Searchcraft MCP Server when you need capabilities focused on search & data extraction and Kagimcp 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
Kagimcp Tools (2)
kagi_search_fetch
Fetch web results for a query using the Kagi Search API. Use for general search and when the user explicitly tells you to 'fetch' results/information. Results are numbered so that a user may refer to a result by a specific number.
kagi_extract
Extract the content of a web page as markdown using the Kagi Extract API. Use this to read the full content of a page when needed.
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.
The Official Model Context Protocol (MCP) server for Kagi Search & other tools.