Field-by-field comparison

Compare the evidence before choosing an MCP.

Each signal stays separate, missing facts remain visible, and the column order follows your selection.

MCPs in this comparison

Perplexity MCPKagi Search MCP

Uncheck an MCP to remove it. Comparing two or three keeps each signal in its own row.

Comparable alternatives

Context7 MCPMCP100 RecommendedHugging Face MCPMCP100 RecommendedExa MCPMCP100 RecommendedGitHub MCPMCP100 Recommendedio.github.blazickjp/arxiv-mcp-serverMCP100 RecommendedMCPVault for ObsidianMCP100 Recommended

Shown only when capability or industry context overlaps.

Side-by-side MCP evidence comparison
Evidence field	Perplexity MCPMCP100 Recommended	Kagi Search MCPMCP100 Recommended
Task fit
Best for	Current web search and cited question answering with Perplexity APIs Research workflows that need a focused search/reasoning MCP rather than browser automation	Web/news/media search with Kagi's index Fetching page content as Markdown through a focused two-tool surface
Not ideal for	Offline or private-network-only workflows Users who want browser control, arbitrary website mutation, or a free unlimited search service	Teams that require OAuth instead of bearer API keys Workloads that need browser automation or site mutation
Avoid when	You cannot safely store a Perplexity API key You plan to expose the local HTTP transport publicly without adding inbound authentication and explicit host/origin allowlists	You cannot safely store or pass a Kagi API key You need a broader crawl/browser automation toolset
Provenance
Provenance details	First-party MCP Perplexity · Publisher source ↗	First-party MCP reviewed-detail:kagi-search-mcp · Publisher source ↗
Maintenance
Maintenance details	Repo: Aug 27, 2026 Package: Sep 21, 2026	Repo: Jul 7, 2026 Package: Not documented
Popularity evidence
GitHub stars	2,539 GitHub stars · checked 2026-09-24T04:14:26.310000Z	527 GitHub stars · checked 2026-09-24T04:14:47.715000Z
Package downloads / 30 days	135,602 package downloads / 30 days · checked 2026-09-24T04:17:38.844000Z	4,745 package downloads / 30 days · checked 2026-09-24T04:18:14.564000Z
Client coverage
Client coverage details	Claude Code✓ Local stdio Claude Desktop✓ Local stdio Codex✓ Local stdio VS Code✓ Local stdio Cursor✓ Local stdio OpenCode✓ Local stdio	Not documented
Client coverage note	Local stdio runs on your computer. Streamable HTTP connects to a remotely hosted MCP server.
Access and data
Authentication	Hosted MCP and local stdio use a Perplexity API key. The hosted Streamable HTTP endpoint accepts Authorization: Bearer <API key>. The local HTTP transport uses PERPLEXITY_API_KEY for outbound Perplexity API calls but does not authenticate inbound MCP callers.	Hosted and local modes use a Kagi API key; hosted HTTP uses Authorization: Bearer <key>. OAuth2 is not supported yet.
Cost	Perplexity API access is pay-as-you-go using separately purchased API credits; a Perplexity Pro subscription is not required. Search/research calls can incur API usage charges.	Kagi API billing is separate from a Kagi subscription and depends on API usage.
Permissions	The MCP is limited to four Perplexity search/reasoning/research tools. Effective quota and billing exposure are those of the supplied API key; it does not expose unrelated Perplexity account-management actions.	The MCP exposes Kagi search and page extraction only; it does not provide browser-control or general write actions.
Data handling	Queries are sent to Perplexity's Search API and Agent API and results are returned to the MCP client. Search/research output contains third-party web content and should be treated as untrusted external data.	Search queries and extraction URLs are sent to Kagi; returned web content should be treated as untrusted external data.
Limitations
Tradeoffs	The four-tool surface is focused and easier to reason about than broad browser MCPs, but requests and usage are billed through the Perplexity API Platform The hosted remote server is easiest to operate; self-hosted HTTP requires the operator to secure inbound access because the server intentionally does not authenticate inbound callers	Small tool surface reduces complexity, but it is narrower than full web-automation MCPs Hosted and self-hosted modes still send search/extraction requests to Kagi APIs
Risk context	Medium. Protect the API key and monitor quota/cost. Web results can contain prompt injection. For self-hosted HTTP, default loopback/deny-all origin/host protections are important because inbound callers are otherwise unauthenticated.	Medium. Main concerns are API-key handling, query privacy, untrusted web content, and cost/rate usage rather than destructive side effects.
Evidence date
Editorial review	2026-09-11	2026-09-11
Candidate evidence	2026-09-24T04:25:05.554391Z	2026-09-24T04:25:05.554391Z

Popularity, maintenance, fit, permissions, and client support are independent evidence fields.

Read the evidence method →