In-depth architectural comparison of the Reefapi MCP 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
Reefapi MCP
Search & Data Extraction · Remote HTTP/SSE
Quality: 53/100 (Good) | Auth: API Key required
Kagimcp
Search & Data Extraction · Local stdio
Quality: 82/100 (Excellent) | Auth: API Key required
Verdict Summary: Choose Reefapi MCP if you need specialized Search & Data Extraction tools running via a hosted cloud SSE transport. 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 Reefapi MCP when:
You need dedicated capabilities in the Search & Data Extraction domain.
You prefer remote streaming HTTP/SSE transport architecture.
Your security boundary fits: API Key required (Freemium).
You have access to required keys: REEFAPI_KEY, MCP_TRANSPORT.
Primary tools included: Discover engines by intent with search_engines, Browse the full engine catalog, Inspect engine and action schemas.
One MCP for 160+ live web-data APIs — search engines, social (Reddit, TikTok, Threads, Bluesky), e-commerce (Amazon, eBay, AliExpress, Etsy), real estate (Zillow, Redfin), jobs, travel, news, finance and company/people intel. Clean JSON from sites that block scrapers; one key, one shared credit pool, free tier. Remote streamable-http at api.reefapi.com/mcp.
The Official Model Context Protocol (MCP) server for Kagi Search & other tools.
Tools & Capabilities Breakdown
Reefapi MCP Tools (6)
Discover engines by intent with search_engines
Browse the full engine catalog
Inspect engine and action schemas
Call engines with structured parameters
Return clean JSON with data, metadata, and errors
Support remote streamable HTTP and local stdio transports
Kagimcp Tools (2)
kagi_search_fetch
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).
Reefapi MCP is categorized under Search & Data Extraction and uses a remote streaming HTTP/SSE transport. In contrast, Kagimcp belongs to Search & Data Extraction using local stdio subprocess. Select Reefapi MCP when you need capabilities focused on search & data extraction and Kagimcp when you require tools for search & data extraction.
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.