kagi-session2api-mcp-server

Provides Kagi web search and URL summarization through an MCP server using session tokens.

7|2|Updated May 16, 2026
One-click install
npx skills add https://github.com/reason-machines/mcp-skills --skill kagi-session2api-mcp-server-reason-machines
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: kagi-session2api-mcp-server
Source: https://github.com/reason-machines/mcp-skills/tree/main/skills/kagi-session2api-mcp-server
Command: npx skills add https://github.com/reason-machines/mcp-skills --skill kagi-session2api-mcp-server-reason-machines

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires kagi-session2api-mcp.

What problem does it solve? Accessing Kagi Search and its summarizer from AI coding agents normally requires a paid API key, and wiring search into MCP clients like Claude Desktop or Cursor involves manual setup. This Skill configures a free MCP server that authenticates with Kagi session tokens instead of paid API keys. ## Core Features & Use Cases - Web Search Tool: The kagi_search_fetch tool runs Kagi queries with full operator support (site:, filetype:, lang:, before:/after:) and returns structured titles, URLs, and snippets. - URL Summarization: The kagi_summarizer tool condenses any public URL using four engines (cecil, agnes, daphne, muriel) with prose or bullet output and target-language selection. - Multi-Token Pooling: Round-robin rotation across multiple session tokens with 5 req/s per-token rate limiting and automatic expired-token detection. - Use Case: A researcher asks their agent to find recent arXiv papers on neural networks with a date-filtered site: query, then summarizes the most relevant paper using the daphne engine for a detailed technical digest. ## Quick Start Install the server with uvx kagi-session2api-mcp, add your Kagi session token to your MCP client config, then ask the agent to search the web for a topic or summarize a URL.

Frequently Asked Questions about kagi-session2api-mcp-server

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up a Kagi MCP server without an API key?▼

Install kagi-session2api-mcp via pip or uvx, then copy your session token from Kagi Settings under Account, Session Link. Add the token as KAGI_SESSION_TOKEN in your MCP client config and restart the client.

How to summarize a URL with Kagi in Claude Desktop?▼

Use the kagi_summarizer tool by asking the agent to summarize a URL. You can pass options like summary_type (summary or takeaway), engine (cecil, agnes, daphne, muriel), and target_language in the tool call parameters.

kagi-session2api-mcp vs official kagimcp: what is the difference?▼

kagi-session2api-mcp is free and authenticates with session tokens, while official kagimcp charges per query and uses API keys. The session approach supports multi-token pooling but depends on Kagi's HTML structure and may violate Kagi's Terms of Service.

Does the Kagi MCP server work with Cursor and Windsurf?▼

Yes, it works with any MCP-compatible client including Cursor, Windsurf, Cline, and Claude Desktop. Add the server command and KAGI_SESSION_TOKEN environment variable to .cursor/mcp.json or the equivalent client settings file.

Why does the Kagi session token expire or return 401 errors?▼

Session tokens expire after a period of inactivity on the Kagi account. Generate a new token from Kagi settings and update your configuration; in multi-token pools, expired tokens are automatically disabled.

What are the rate limits and risks of using Kagi session tokens?▼

Each token is limited to 5 requests per second, and throughput scales linearly with pooled tokens. Using session tokens may violate Kagi's Terms of Service and can lead to account suspension, so official API access is recommended for production.