F
licenseNot graded
qualityF
maintenanceA Model Context Protocol (MCP) server that provides AI assistants full access to the Motion task and project management API, enabling task, project, and schedule management.
-
ftrack MCP Server
Related Servers
Alternatives to ftrack MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceMCP server for Autodesk Flow Production Tracking (ShotGrid) enabling AI assistants to query, create, update, and delete entities via the ShotGrid API with built-in RAG anti-hallucination and safety layers.181MIT
- AlicenseNot gradedqualityBmaintenanceA Model Context Protocol (MCP) server implementation that enables AI assistants to interact with Anytype's API through natural language, allowing users to manage their knowledge base through conversation.637 npm521MIT
- AlicenseBqualityDmaintenanceA Model Context Protocol server providing AI assistants with comprehensive project, task, and subtask management capabilities with project-specific storage.2912 npm89MIT
- AlicenseBqualityBmaintenanceA Model Context Protocol (MCP) server providing AI assistants with comprehensive ClickUp integration, covering the full API surface across 87 consolidated tools.87174 npmMIT
Contentfulofficial
AlicenseNot gradedqualityAmaintenanceA Model Context Protocol (MCP) server that provides AI assistants with comprehensive tools to interact with Contentful APIs.139 npm60MIT
TDQS
C2.9/5.0
Scored across 59 tools
Disambiguation4/5
Most tools target distinct actions and resources, with clear separation between querying, CRUD, security roles, API keys, uploads, and delayed jobs. Some potential confusion exists between convenience list_* wrappers and ftrack_query, or between ftrack_convert_entity and ftrack_update, but descriptions help clarify.
Naming Consistency3/5
Most tools follow a 'ftrack_verb_noun' pattern, but there are deviations: the last five tools lack the ftrack_ prefix, 'ftrack_un_assume_user' has an awkward underscore, and delayed job tools mix nomenclature. Overall, the pattern is readable but not fully consistent.
Tool Count2/5
With 59 tools, the server is heavily over-scoped for an MCP interface. While the domain is complex, many niche operations (e.g., multiple delayed job tools, granular security role grants) could be consolidated or exposed via a more compact API surface. The count feels excessive and likely overwhelms agents.
Completeness4/5
The tool set covers a broad range of ftrack functionality: general query and CRUD, user/security management, uploads, media encoding, review sessions, task management, and project structure. Minor gaps exist (e.g., no note update/delete, no asset version creation) but core workflows are well-supported.
Maintenance
ActivityInactive
ResponsivenessNo issues