Kagi MCP Server vs Slack MCP Server

A side-by-side look at pricing, capabilities, pros, cons, and our editorial scores.

	Kagi MCP Server MCP Servers	Slack MCP Server MCP Servers
Tagline	Official Kagi Search MCP server: search and extract the web from any MCP-compatible agent.	Archived reference MCP server that lets Claude and other MCP clients read and post in a Slack workspace via a bot token.
Category	MCP Servers	MCP Servers
Pricing	Paid· Free: $0 USD · Team: $4 USD per user/month · Enterprise: $21 USD per user/month	Free· Free / open-source (MIT). Requires a Slack workspace and a Slack bot token; Slack itself is free/paid.
Model	—	—
Editorial score	—	—
Use cases	agent web search groundingClaude Code documentation lookupdeep-research pipelinesURL to Markdown extraction for RAGnews and video search from an LLMKagi lens-scoped queries in agentscitation gathering for research assistantscoding agent error-message lookups	Channel triage and summarisationAutomated thread digestsPosting AI-generated status updatesCross-channel search and reportingStandup and retro note postingOn-call escalation repliesUser and profile lookup for routingReaction-based workflow signallingMCP server reference implementation
Pros	Official, first-party MCP server maintained by Kagi (not a community wrapper) Two clean tools that cover the 90% agent case: search and full-page Markdown extraction Both hosted (mcp.kagi.com) and local (uvx/Docker) deployment modes Documented setup recipes for Claude Desktop, Claude Code, Codex CLI, Kiro, OpenCode, Smithery MIT-licensed Python code, easy to fork or audit Rides Kagi's ad-free, spam-de-boosted index rather than generic SERP APIs Supports Kagi lenses and filters so agents can scope searches to news, docs, etc.	Official reference implementation from the modelcontextprotocol project — small, readable TypeScript that documents the MCP tool pattern well Covers the eight highest-value Slack primitives (list, post, reply, react, history, thread, users, profile) with minimal ceremony Ships as both an npx package and a Docker image, so it drops straight into Claude Desktop, Cursor, or any MCP client with a JSON config snippet Standard Slack bot-token auth (xoxb-) with clearly scoped OAuth permissions — easy to reason about and to revoke Open-source under MIT, so forking or vendoring for internal hardening is straightforward Good starting point for learning how to write your own MCP server against a REST API
Cons	Requires a paid Kagi API key with pay-per-use billing; not usable free FastGPT and Universal Summarizer tools are currently absent (rewrite in progress) Python + uv toolchain assumption raises the bar vs. a single-binary MCP server Small surface area: no built-in caching, batching, or spend controls beyond Kagi's invoice cap Hosted endpoint means your queries and Bearer token traverse Kagi infra, not a concern for everyone but worth noting for regulated workloads	Archived by the maintainer on 29 May 2025 — no upstream bug fixes, security patches, or Slack API compatibility updates Read-only surface for channels (public channels only by default) and no DM, private-channel, search, files, or canvas support out of the box No pagination helpers or rate-limit backoff beyond what the Slack SDK provides, so bulk history pulls in large workspaces can be fragile Requires a workspace admin to install a bot app and mint a token, which is a real blocker in locked-down enterprise Slack tenants Bot-token model means every action is attributed to the bot user, not the human operating the assistant, which complicates audit trails
Website	github.com	github.com

Pick Kagi MCP Server if

✅ Official, first-party MCP server maintained by Kagi (not a community wrapper)
✅ Two clean tools that cover the 90% agent case: search and full-page Markdown extraction
✅ Both hosted (mcp.kagi.com) and local (uvx/Docker) deployment modes
✅ Documented setup recipes for Claude Desktop, Claude Code, Codex CLI, Kiro, OpenCode, Smithery

Pick Slack MCP Server if

✅ Official reference implementation from the modelcontextprotocol project — small, readable TypeScript that documents the MCP tool pattern well
✅ Covers the eight highest-value Slack primitives (list, post, reply, react, history, thread, users, profile) with minimal ceremony
✅ Ships as both an npx package and a Docker image, so it drops straight into Claude Desktop, Cursor, or any MCP client with a JSON config snippet
✅ Standard Slack bot-token auth (xoxb-) with clearly scoped OAuth permissions — easy to reason about and to revoke

Compare a different pair →