Skip to main content
Glama
johnnyvincentvitale

touchdesigner-manual

Related Servers

Alternatives to touchdesigner-manual

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      A local-first MCP server for TouchDesigner that provides offline documentation retrieval and live control of TouchDesigner sessions, enabling AI-assisted network building and parameter management.
      MIT
    • A
      license
      B
      quality
      B
      maintenance
      An MCP server for TouchDesigner that lets AI agents inspect, build, wire, optimize, and stabilize live TD networks with 106 tools, plus a technique memory system for reusable patterns.
      100
      14
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that turns a directory of markdown documentation into searchable, citable tools for AI assistants, enabling them to find, read, and reference specific sections with auditable citations.
      -
    • A
      license
      B
      quality
      C
      maintenance
      A token-efficient MCP server for driving TouchDesigner from AI assistants, enabling building whole node networks in one call, searching CHOP channels by glob, inspecting operators compactly, and taking screenshots of TOPs.
      16
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      An intelligent MCP server that enables AI agents to crawl, index, and semantically search official framework documentation using local RAG. It prevents hallucinations by providing precise, up-to-date documentation excerpts directly into the AI's context window.
      1
      -
    • F
      license
      B
      quality
      C
      maintenance
      A MCP server that allows you to search and retrieve content on any wiki site using MediaWiki with LLMs 🤖. wikipedia.org, fandom.com, wiki.gg and more sites using Mediawiki are supported!
      2
      27
      -

    TDQS

    A4.4/5.0

    Scored across 3 tools

    Disambiguation4/5

    The three tools are mostly distinct: browse_manual for orientation/discovery, search_manual for finding passages, and read_page for reading full content. The browse_manual and search_manual could potentially overlap when searching for a specific topic (both filter by family and query), but the descriptions clearly differentiate them by cost tier and use case, so an agent can usually tell them apart.

    Naming Consistency4/5

    The tool names follow a consistent verb_noun pattern (browse_manual, search_manual, read_page), all snake_case. Slight inconsistency in that browse_manual and search_manual both target 'manual' while read_page targets 'page', but the pattern is predictable and readable overall.

    Tool Count4/5

    Three tools is a reasonable count for a documentation/manual retrieval server. It's on the lean side but each tool serves a distinct retrieval stage (discover, search, read). Given the narrow scope of a documentation lookup server, three well-chosen tools feel appropriate, though it borders on thin.

    Completeness3/5

    The core browse-search-read workflow is covered and represents the essential operations for a wiki documentation server. However, there are minor gaps: no way to list all pages in a family without a query, no direct tool for navigating to a specific page by title from scratch (read_page requires knowing the exact title), and no distinction between getting a section vs. full page could be improved. These are workable gaps but notable.

    Maintenance

    ActivityStale
    ResponsivenessNo issues