Skip to main content
Glama
deenesjakoruzh
KSroido

kagi-session2api-mcp

by KSroido
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Servidor MCP Kagi Session2API

Un servidor MCP (Model Context Protocol) gratuito para Kagi Search: accede a la búsqueda y al resumidor de Kagi mediante tokens de sesión, sin necesidad de clave API. Funciona con Claude Desktop, Cursor, Windsurf, Cline, Hermes y cualquier asistente/agente de codificación de IA compatible con MCP.

Inglés | Documentación en chino

⚠️ Advertencia para el usuario final: Este proyecto utiliza tokens de sesión de Kagi para acceder a las funciones de búsqueda y resumen sin la API oficial de pago. Esto puede violar los Términos de servicio de Kagi. Las posibles consecuencias incluyen la suspensión de la cuenta o la prohibición permanente. Úselo bajo su propio riesgo. Los autores no asumen ninguna responsabilidad por las acciones tomadas por Kagi contra su cuenta.

⚠️ Advertencia de seguridad: Su token de sesión de Kagi proporciona acceso completo a la cuenta. Trátelo como una contraseña. Nunca lo comparta ni lo incluya en el control de versiones.

Características

  • Acceso basado en sesión: Utiliza tokens de sesión de Kagi en lugar de la API oficial ($25/1000 consultas), totalmente gratuito.

  • Grupo de tokens múltiples: Configure varios tokens para un mayor rendimiento con rotación round-robin.

  • Limitación de tasa por token: 5 req/s por token con algoritmo de token bucket.

  • Salida compatible con API: Devuelve resultados en el mismo formato que el kagimcp oficial.

  • Dos herramientas: kagi_search_fetch (búsqueda web) y kagi_summarizer (resumen de URL).

  • Suplantación de UA de Firefox: Imita un navegador Firefox real para el acceso basado en sesión.

  • Desactivación automática de tokens caducados: Los tokens caducados se detectan y omiten automáticamente.

  • Operadores de búsqueda: Admite operadores de Kagi (site:, lang:, filetype:, etc.).

Related MCP server: Kagi MCP Server

Plataformas compatibles

Funciona con cualquier cliente compatible con MCP:

Instalación rápida (para agentes de IA)

Simplemente pegue este prompt en su agente de IA:

Install the Kagi Session2API MCP server from https://pypi.org/project/kagi-session2api-mcp/.
Then add it to my MCP:
`uvx kagi-session2api-mcp`
set env KAGI_SESSION_TOKEN to my token (ask me if you don't have it).
If I have multiple tokens, use KAGI_SESSION_TOKENS (comma-separated) instead,
or create a config file at ~/.config/kagi-session2api-mcp/config.toml with:
[kagi]
session_tokens = ["TOKEN_1", "TOKEN_2"]
summarizer_engine = "cecil"
[client]
timeout = 30
max_retries = 2
and set env KAGI_SESSION_CONFIG to that path.

Instalación manual

pip install kagi-session2api-mcp

O con uvx:

uvx kagi-session2api-mcp

Configuración

Opción 1: Variable de entorno (token único)

{
  "mcpServers": {
    "kagi-session": {
      "command": "uvx",
      "args": ["kagi-session2api-mcp"],
      "env": {
        "KAGI_SESSION_TOKEN": "YOUR_SESSION_TOKEN_HERE"
      }
    }
  }
}

Opción 2: Variable de entorno (múltiples tokens)

{
  "mcpServers": {
    "kagi-session": {
      "command": "uvx",
      "args": ["kagi-session2api-mcp"],
      "env": {
        "KAGI_SESSION_TOKENS": "TOKEN_1,TOKEN_2,TOKEN_3"
      }
    }
  }
}

Opción 3: Archivo de configuración (recomendado para múltiples tokens)

Cree ~/.config/kagi-session2api-mcp/config.toml:

[kagi]
session_tokens = [
    "YOUR_TOKEN_1_HERE",
    "YOUR_TOKEN_2_HERE",
]

summarizer_engine = "cecil"

[client]
timeout = 30
max_retries = 2

Luego configure:

{
  "mcpServers": {
    "kagi-session": {
      "command": "uvx",
      "args": ["kagi-session2api-mcp"],
      "env": {
        "KAGI_SESSION_CONFIG": "/path/to/config.toml"
      }
    }
  }
}

Obtención de su token de sesión

  1. Inicie sesión en kagi.com

  2. Vaya a Settings → Account → Session Link

  3. Copie el token de la URL de sesión: https://kagi.com/search?token={ESTA_PARTE}&q=test

  4. Utilice este token en su configuración

Uso

Herramientas MCP

kagi_search_fetch

Busque en la web usando Kagi:

Search for "Python async tutorial"

Admite operadores de búsqueda de Kagi:

  • site:github.com - Restringir al dominio

  • -site:reddit.com - Excluir dominio

  • filetype:pdf - Filtro de tipo de archivo

  • intitle:python - Filtro de título

  • lang:zh - Filtro de idioma

  • before:2024-01-01 / after:2024-01-01 - Filtros de fecha

  • "frase exacta" - Coincidencia exacta

kagi_summarizer

Resuma cualquier URL:

Summarize https://example.com/article

Opciones:

  • summary_type: "summary" (prosa) o "takeaway" (puntos clave)

  • engine: "cecil" (predeterminado), "agnes", "daphne", "muriel"

  • target_language: Código de idioma (p. ej., "ES")

⚠️ El resumidor es experimental: utiliza el endpoint interno de Kagi que puede cambiar.

Modos de transporte

Stdio (predeterminado, para Claude Desktop):

kagi-session2api-mcp

HTTP (para acceso remoto):

kagi-session2api-mcp --http --host 0.0.0.0 --port 8000

Arquitectura

MCP Client → FastMCP Server → TokenPool (round-robin) → httpx.AsyncClient → kagi.com
                                ↓
                          TokenBucket (5 req/s per token)
                                ↓
                          Auto-disable expired tokens

Comportamiento del grupo de tokens

Configuración

Límite de tasa

Tasa efectiva

1 token

5 req/s

5 req/s

2 tokens

5 req/s cada uno

10 req/s

N tokens

5 req/s cada uno

5×N req/s

Cuando un token caduca (detectado mediante 401/403 o redirección al inicio de sesión), se desactiva automáticamente. Los tokens restantes continúan atendiendo solicitudes.

Diferencias con el kagimcp oficial

Aspecto

kagimcp oficial

kagi-session2api-mcp

Autenticación

Clave API ($25/1000)

Token de sesión (gratis)

Endpoint de búsqueda

/api/v0/search

/html/search (scraping HTML)

Resumidor

/api/v0/summarize

/mother/summary_labs (interno)

Limitación de tasa

Lado del servidor

Lado del cliente (token bucket)

api_balance

Devuelve saldo

Siempre null

Costo

De pago

Gratis (usa la sesión existente)

Riesgos

  • Kagi puede cambiar su estructura HTML, rompiendo el analizador.

  • El acceso basado en sesión puede violar los Términos de servicio de Kagi.

  • Es posible la suspensión de la cuenta o la prohibición permanente.

  • El endpoint del resumidor es interno y puede cambiar sin previo aviso.

  • Úselo bajo su propio riesgo. Los autores no asumen ninguna responsabilidad por las consecuencias, incluidas, entre otras, las acciones tomadas por Kagi contra su cuenta.

Licencia

MIT

Available Tools

2 tools
kagi_search_fetchA

Fetch web results based on one or more queries using Kagi Search.

Use for general search and when the user explicitly tells you to 'fetch' results/information. Results are from all queries given. They are numbered continuously, so that a user may be able to refer to a result by a specific number.

ParametersJSON Schema
NameRequiredDescriptionDefault
queriesYesOne or more concise, keyword-focused search queries. Include essential context within each query for standalone use. Supports Kagi operators: site:, -site:, filetype:/ext:, intitle:, inurl:, lang:, loc:, before:, after:, "exact phrase", +term, -term
limitNoMaximum number of results per query. Default: all available.

Output Schema

ParametersJSON Schema
NameRequiredDescription
resultYes

TDQS

A4.2/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden. It mentions numbering and that results are from all queries, but fails to disclose other behavioral traits such as pagination, caching, or auth requirements.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise, with three sentences that are front-loaded with purpose. Every sentence adds value without redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the presence of an output schema, return values need not be explained. The description is adequate for basic usage, though it could mention rate limits or error handling for completeness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, and the description adds meaning by specifying that queries should be concise and keyword-focused, with essential context. The limit parameter's default behavior is explained.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it fetches web results using Kagi Search, for general search and when the user explicitly asks to 'fetch'. It distinguishes from the sibling tool kagi_summarizer by focusing on search results rather than summaries.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explains when to use (general search, explicit fetch) and notes that results from all queries are numbered continuously. While it doesn't explicitly state when not to use, the sibling context implies summarization is separate.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

kagi_summarizerA

Summarize content from a URL using the Kagi Summarizer.

The Summarizer can summarize any document type (text webpage, video, audio, etc.)

Note: This tool uses Kagi's internal summarizer endpoint accessed via session token. This is experimental and may break if Kagi changes their internal API.

ParametersJSON Schema
NameRequiredDescriptionDefault
urlYesA URL to a document to summarize.
summary_typeNoType of summary to produce. Options are 'summary' for paragraph prose and 'takeaway' for a bulleted list of key points.summary
target_languageNoDesired output language using language codes (e.g., 'EN' for English). If not specified, the document's original language influences the output.
engineNoSummarizer engine to use. 'cecil' is the default. Note: This is an experimental feature — the summarizer endpoint may change without notice.cecil

Output Schema

ParametersJSON Schema
NameRequiredDescription
resultYes

TDQS

A3.6/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries full responsibility for behavioral disclosure. It clearly states the experimental nature, potential breakage, and support for various content types. It does not detail error handling or rate limits, but the explicit warning about instability adds significant transparency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise and structured: a clear purpose statement, a brief capability note, and a critical caution. Each sentence serves a purpose, though the capability note could be integrated into the first sentence.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's 4 parameters and existing output schema (not shown), the description provides enough context to understand the tool's function and risks. However, it lacks guidance on error handling, prerequisites (e.g., need for a valid session token), and typical usage scenarios, which would enhance completeness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 100% description coverage, so the baseline is 3. The description adds limited value, only restating the summary_type and engine options in a mildly explanatory way. It does not introduce new meaning beyond the schema's own descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool summarizes content from a URL using Kagi Summarizer, including support for various document types. It distinguishes from the sibling tool (kagi_search_fetch) by focusing on summarization rather than search, though no explicit comparison is made.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description warns that the tool is experimental and may break due to internal API changes, which provides important context. However, it does not specify when to use this tool over alternatives or when not to use it, leaving the agent to infer from the sibling tool's purpose.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 2 tool updatesv0.2.1
    • First observedkagi_search_fetch
    • First observedkagi_summarizer
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A3.9/5.0

Scored across 2 tools

Disambiguation5/5

The two tools have clearly distinct purposes: one fetches search results, the other summarizes content from URLs. There is no overlap or ambiguity in their functionality.

Naming Consistency5/5

Both tools follow a consistent verb_noun pattern with the 'kagi_' prefix ('kagi_search_fetch', 'kagi_summarizer'), making the naming predictable and understandable.

Tool Count3/5

With only 2 tools, the server feels minimal but still reasonable for its narrow focus on Kagi search and summarizer APIs. The experimental nature of the summarizer tool might warrant additional tools in the future.

Completeness4/5

The tool surface covers the two core operations of the Kagi API: search and summarization. While there are no additional utilities like listing or filtering, the basic workflow is supported without obvious dead ends.

Maintenance

ActivityInactive
ResponsivenessSlow

Resources

Related MCP Connectors

Related MCP Servers

  • kagi-kan-mcp

    czottmann
    A
    license
    A
    quality
    C
    maintenance
    Unofficial MCP server for working with Kagi without API access (you'll need to be a customer, tho). Searches and summarizes. Uses Kagi session token for easy authentication.
    2
    42
    MIT

  • Kagi MCP Server

    z23cc
    A
    license
    Not graded
    quality
    D
    maintenance
    Enables integration with Kagi search engine services including web search, content summarization from URLs, and AI assistant conversations. Uses session tokens to access Kagi's search API, summarizer, and AI models directly within MCP-compatible applications.
    8 npm
    3
    MIT

  • Search MCP Server

    kikohz
    A
    license
    Not graded
    quality
    D
    maintenance
    Free web search MCP server using SearXNG, supporting web search, news search, and search summaries.
    MIT

  • kagi-mcp

    real-jiakai
    A
    license
    A
    quality
    B
    maintenance
    MCP server for Kagi Search that uses your session token for web and news search without a separate API subscription.
    3
    27 npm
    MIT