ftrack MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FTRACK_SERVER | Yes | Your ftrack server URL (e.g., https://your-workspace.ftrackapp.com) | |
| FTRACK_API_KEY | Yes | Your ftrack API key | |
| FTRACK_API_USER | Yes | Your ftrack username |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| ftrack_queryB | Execute a query using ftrack query language. Example: "select id, name from Project where status is active" |
| ftrack_parse_queryA | Parse a query expression without executing it (useful for validation) |
| ftrack_query_schemasA | Query all available entity schemas in ftrack |
| ftrack_query_server_informationA | Get ftrack server information including version and configuration |
| ftrack_searchB | Full-text search across ftrack entities |
| ftrack_createC | Create a new entity in ftrack |
| ftrack_updateC | Update an existing entity in ftrack |
| ftrack_deleteC | Delete an entity from ftrack |
| ftrack_add_user_security_roleA | Add a security role to a user |
| ftrack_remove_user_security_roleB | Remove a security role from a user |
| ftrack_update_user_security_roleC | Update a user security role (e.g., activate/deactivate) |
| ftrack_grant_user_security_role_projectB | Grant a user security role access to a specific project |
| ftrack_revoke_user_security_role_projectA | Revoke a user security role access from a specific project |
| ftrack_assume_userA | Assume another user identity (requires admin privileges) |
| ftrack_un_assume_userA | Stop assuming another user identity and return to original identity |
| ftrack_send_user_inviteB | Send an invitation email to a user |
| ftrack_grant_api_key_projectB | Grant an API key access to a project |
| ftrack_revoke_api_key_projectB | Revoke an API key access from a project |
| ftrack_grant_api_key_security_roleA | Grant a security role to an API key |
| ftrack_revoke_api_key_security_roleB | Revoke a security role from an API key |
| ftrack_configure_otpC | Configure OTP (One-Time Password) for a user |
| ftrack_configure_totpC | Configure TOTP (Time-based One-Time Password) for a user |
| ftrack_generate_totpC | Generate a new TOTP secret for a user |
| ftrack_disable_2faB | Disable two-factor authentication for a user |
| ftrack_get_upload_metadataC | Get metadata required for uploading a file to ftrack |
| ftrack_complete_multipart_uploadA | Complete a multipart upload after all parts have been uploaded |
| ftrack_generate_signed_urlB | Generate a signed URL for accessing or uploading a component |
| ftrack_encode_mediaB | Trigger media encoding/transcoding for a component |
| ftrack_convert_entityB | Convert an entity from one type to another |
| ftrack_permissionsC | Check permissions for an entity |
| ftrack_storage_usageC | Get storage usage information |
| ftrack_send_review_session_inviteC | Send an invitation to participate in a review session |
| ftrack_reset_remote_api_keyB | Reset a user remote API key |
| ftrack_reset_remote_passwordB | Reset a user remote password |
| ftrack_csv_import_delayed_jobC | Create a CSV import delayed job |
| ftrack_delete_delayed_jobC | Create a delete delayed job for batch entity deletion |
| ftrack_export_review_session_feedback_delayed_jobB | Export review session feedback as a delayed job |
| ftrack_iconik_sync_structure_delayed_jobB | Sync structure to iconik as a delayed job |
| ftrack_sync_ldap_users_delayed_jobC | Sync LDAP users as a delayed job |
| ftrack_batchA | Execute multiple operations in a single transaction (all succeed or all fail) |
| ftrack_list_projectsB | List all projects (convenience wrapper for query) |
| ftrack_list_tasksC | List tasks for a project or context |
| ftrack_list_usersC | List all users |
| ftrack_list_asset_versionsB | List asset versions for a task or asset |
| ftrack_list_statusesB | List all available statuses |
| ftrack_list_typesA | List all available task/object types |
| ftrack_list_prioritiesA | List all available priorities |
| ftrack_get_entityA | Get a single entity by type and ID with specified projections |
| ftrack_create_noteC | Create a note on an entity |
| ftrack_list_notesB | List notes for an entity |
| ftrack_update_task_statusC | Update the status of a task |
| ftrack_assign_user_to_taskC | Assign a user to a task |
| ftrack_list_security_rolesB | List all security roles |
| ftrack_list_review_sessionsC | List review sessions |
| list_shotsA | List shots for a project or parent sequence |
| list_asset_buildsB | List asset builds for a project |
| get_project_structureB | Get the top-level structure of a project (immediate children such as sequences, episodes, folders) |
| list_user_assignmentsA | List all tasks assigned to a user, optionally filtered by project or status |
| list_milestonesC | List milestones for a project |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 59 tools
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.
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.
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.
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.