Skip to main content
Glama
martoc

MCP Spark Documentation Server

by martoc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to MCP Spark Documentation Server

No user-submitted related servers found.

    Related Servers

    • anydocs

      kiyeonjeon21
      A
      license
      A
      quality
      A
      maintenance
      Provides fast, token-efficient search over coding agent documentation (e.g., Claude Code, Cursor) using local SQLite FTS5 indexing, with tools for searching snippets, reading pages, and grepping markdown.
      5
      MIT

    • obsidian-web-mcp-fts

      sebastian-stadelmann
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides ranked full-text search over Obsidian vaults using SQLite FTS5, BM25 scoring, and multilingual stemming, adding a vault_fts_search tool to find relevant notes beyond exact line matches.
      MIT

    • Hermes Docs MCP Server

      JPeetz
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP clients to search, navigate, and read the complete Hermes Agent documentation through a local SQLite FTS5 index, with tools for full-text search, page reading, and browsing documentation structure.
      MIT

    • my-kb

      alexiuhubhiu
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables agents to search a local, fully offline personal document library (Markdown/txt/PDF/docx) via SQLite FTS5 trigram search with subject-terminology expansion, returning every hit with its domain, document title, section path, and page or offset provenance. It also exposes domain statistics, incremental ingestion, and document deprecation as tools, alongside a read-only, runtime-persona-scoped ask/coverage mode.
      -
    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

    A4.4/5.0

    Scored across 2 tools

    Disambiguation5/5

    Search and read are completely distinct operations with no overlap. Search finds relevant pages, read retrieves content, and each has clearly defined inputs.

    Naming Consistency5/5

    Both tools follow the consistent verb_noun pattern (search_documentation, read_documentation) with snake_case, making the API predictable and clean.

    Tool Count3/5

    Two tools is borderline for a minimal server, but for a documentation-specific purpose, search and read are the essential operations. It feels slightly thin but not unreasonable.

    Completeness4/5

    The tool surface covers core documentation workflows: discovering relevant pages and reading their content. Minor gaps like listing all sections or navigating a table of contents exist, but they are non-blocking.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources