Kagimcp vs Fetch
A side-by-side look at the Kagimcp and Fetch MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Kagimcp for search & data extraction work as a local process; choose Fetch for search & data extraction as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Kagimcp when
- You need dedicated capabilities in the Search & Data Extraction domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
KAGI_API_KEY. - You want tools like
kagi_search_fetch, kagi_extract.
Choose Fetch when
- You need dedicated capabilities in the Search & Data Extraction domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
fetch.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Search & Data Extraction | Search & Data Extraction |
| Quality signal | 80/100 · Excellent | 80/100 · Excellent |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | API key required | No auth required |
| Pricing | BYOK (pay the provider) | Free |
| Required env vars | KAGI_API_KEY | None listed |
| Verified owner | Verified | Verified |
| GitHub stars | 546 | 91,526 |
| Directory activity | 3 views 0 installs 0 upvotes | 5 views 0 installs 0 upvotes |
| Tools | 2 | 1 |
| Full listing | View Kagimcp | View Fetch |
Tools & capabilities
Kagimcp tools 2
kagi_search_fetchFetch 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_extractExtract 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.
Fetch tools 1
fetchFetches a URL from the internet and extracts its contents as markdown.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Kagimcp
{
"mcpServers": {
"kagisearch-kagimcp": {
"command": "uvx",
"args": [
"kagimcp"
],
"env": {
"KAGI_API_KEY": "YOUR_KAGI_API_KEY_HERE"
}
}
}
}
Fetch
{
"mcpServers": {
"fetch": {
"command": "uvx",
"args": [
"mcp-server-fetch"
]
}
}
}
Frequently asked questions
Kagimcp is categorized under Search & Data Extraction and uses a local stdio subprocess. Fetch belongs to Search & Data Extraction and uses a local stdio subprocess. Pick Kagimcp for search & data extraction work and Fetch for search & data extraction.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Kagimcp is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: api key required. Fetch is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add kagisearch-kagimcp and fetch as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Kagimcp has a quality signal of 80/100 (Excellent) with 3 views, 0 installs and 546 GitHub stars. Fetch has 80/100 (Excellent) with 5 views, 0 installs and 91,526 GitHub stars.