Skip to main content
Glama
fxckcode

tauri-docs-mcp

by fxckcode
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to tauri-docs-mcp

No user-submitted related servers found.

    Related Servers

    • official-docs

      pittzhang20260507
      A
      license
      A
      quality
      B
      maintenance
      Enables MCP clients to query upstream documentation through a single search tool, backed by a bundled sample corpus, Vertex AI Search, or an SSH endpoint, returning cited source passages and refusing when nothing relevant is found.
      1
      Apache 2.0

    • Yandex Cloud Docs MCP

      selivanov-tech
      A
      license
      Not graded
      quality
      C
      maintenance
      Provides offline, read-only full-text search over a local Yandex Cloud documentation checkout via MCP, with ranked search, line-numbered excerpts, and index status tools.
      Apache 2.0

    • docs-search-engine

      wanyingng
      F
      license
      A
      quality
      D
      maintenance
      Enables searching documentation from GitHub repositories and web pages via MCP tools, with in-memory indexing and caching for fast retrieval.
      3
      -

    • docs-mcp

      kislevlevy
      F
      license
      Not graded
      quality
      B
      maintenance
      Local documentation search server for AI models using hybrid retrieval (phrase, keyword, vector). Provides MCP tools to search and fetch documentation from bundled or custom doc sets without any external API keys.
      -
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    A3.7/5.0

    Scored across 3 tools

    Disambiguation4/5

    resolve_tauri_docs (metadata lookup) and query_tauri_docs (content retrieval) are clearly distinct purposes, and search_tauri_docs is explicitly documented as a compatibility alias for the resolve+query pair. The remaining ambiguity is that an agent might still reach for search, but the description steers it correctly.

    Naming Consistency5/5

    All three tools follow an identical verb_noun_topic pattern (resolve/query/search + _tauri_docs) in consistent snake_case. The naming is fully predictable.

    Tool Count4/5

    Three tools is slightly thin but appropriate for a documentation lookup server with a small bounded domain. Each tool covers a distinct retrieval phase with no filler.

    Completeness4/5

    The resolve-then-query lifecycle plus a compatibility search covers discovery and content retrieval for the Tauri doc corpus. A browse/list-all-identifiers operation is absent, but search largely covers that need.

    Maintenance

    ActivityMaintained
    ResponsivenessResponsive

    Resources