Skip to main content
Glama
Sign In
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

    • neoforge-docs

      Dynastxu
      A
      license
      A
      quality
      C
      maintenance
      Enables local, offline BM25 search and retrieval of NeoForge documentation through MCP tools, including section/doc access, API symbol lookup, page listing, and cross-version comparison.
      6
      MIT

    • 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

    • CodeContext MCP

      dileepreddy27
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables coding agents to search local repositories and retrieve bounded, cited source chunks, look up full indexed chunks, and inspect index statistics through read-only MCP tools over stdio.
      MIT
    Deploy Server
    Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.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

    ActivitySlowing
    ResponsivenessResponsive

    Resources