Skip to main content
Glama
KSroido

kagi-session2api-mcp

by KSroido

Related Servers

Alternatives to kagi-session2api-mcp

No user-submitted related servers found.

    Related Servers

    • 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
    • A
      license
      A
      quality
      D
      maintenance
      MCP server for Kagi Search that uses your session token for web and news search without a separate API subscription.
      3
      6 npm
      MIT
    • 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.
      4 npm
      3
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Free web search MCP server using SearXNG, supporting web search, news search, and search summaries.
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables any MCP client to run keyless multi-engine web searches with RRF fusion, fetch pages and documents as Markdown, and full-text search a local SQLite index. It keeps queries and cached content on the user's machine, degrading gracefully across engine tiers when providers are blocked or rate-limited.
      8
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients and a terminal CLI to run web searches through a user's own SearXNG instance, saving every query as a reusable session and optionally generating AI-synthesized answers.
      48 npm
      MIT

    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