Skip to main content
Glama

Related Servers

Alternatives to fpt-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      A lean MCP server giving LLM agents full access to the ShotGrid / Autodesk Flow Production Tracking API through 15 curated tools, including generic CRUD, schema discovery, and safe writes with a dry_run flag.
      1
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Bridges AI assistants to Autodesk ShotGrid (Flow Production Tracking) data, enabling CRUD, search, batch operations, and schema exploration via typed MCP tools with progressive loading.
      1
      MIT
    • F
      license
      C
      quality
      D
      maintenance
      A Model Context Protocol (MCP) server that provides AI assistants with full access to the ftrack production tracking API, enabling natural language interactions to query projects, manage tasks, update statuses, and more.
      59
      2
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      A lean, standardized MCP server for AYON (Ynput) that enables AI agents to drive an AYON production server through a clean interface, providing 20 tools for CRUD operations, schema discovery, and typed helpers.
      MIT
    • F
      license
      A
      quality
      C
      maintenance
      An MCP server that exposes Autodesk Platform Services (APS) as tools for AI assistants to interact with the APS Data Management API. It enables users to authenticate and manage hubs, projects, and folders through a standardized interface.
      27
      2
      -

    TDQS

    A3.7/5.0

    Scored across 18 tools

    Disambiguation3/5

    Many tools have distinct roles (launch, EDL, schema, path resolve), but several overlap: sg_find vs fpt_reporting's text_search both search entities, sg_create vs fpt_bulk's batch both create, and the publishing surface (tk_publish, openclip_create, plus a referenced-but-absent maya_session publish) is crowded. Descriptions disambiguate intent well, but an agent still faces genuine choice points.

    Naming Consistency4/5

    Names are uniformly snake_case and mostly verb_noun, with subsystem prefixes (sg_, tk_, fpt_) that usefully group capabilities. Minor deviations: some tools are noun-first (session_stats, cut_to_edl) and prefixes are applied unevenly (openclip_create, search_sg_docs, learn_pattern have none), but the pattern stays readable.

    Tool Count4/5

    18 tools is on the heavy side but justified by the broad domain spanning ShotGrid CRUD, DCC launch, Toolkit publish/path resolution, Flame conform, and RAG meta-tools. No tool appears purely redundant, though the meta/RAG trio (search_sg_docs, learn_pattern, session_stats/reset_session_stats) pushes the count up.

    Completeness4/5

    Core ShotGrid lifecycle is covered (find, create, update, upload, download, schema, bulk delete/revive/batch, linking), plus Toolkit and Flame-specific flows. Minor gaps: no single-entity get (must use sg_find), deletion only via the bulk wrapper, and tk_publish references a maya_session native publisher that is not present in this tool set.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues