pictory-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PICTORY_API_KEY | Yes | Your Pictory API key. Required to authenticate with the Pictory API. |
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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| pictory_videoC | Create, render, preview, and patch Pictory videos. |
| pictory_transcribeC | Transcribe long-form videos/podcasts and automatically extract viral short clips (Shorts/Reels/TikToks). |
| pictory_assetsB | Search stock b-roll, background music, voices, avatars, layouts, and generate AI Studio images & videos. Supported Actions:
|
| pictory_projectsB | Manage Pictory projects and master video templates (full web UI synchronization). Supported Actions:
|
| pictory_integrationsB | Manage third-party cloud integrations (Vimeo & AWS S3), account quotas, AI credits, and job cleanup. Supported Actions:
|
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 5 tools
The five tools are assigned to distinct domains (creation, integration, transcription, assets, projects), and the embedded action lists help clarify intent. However, pictory_video, pictory_projects, and pictory_assets' generate_ai_video can all be mistaken for 'video creation' paths, requiring careful reading.
All five tools follow the same 'pictory_<domain>' pattern, and embedded actions use consistent snake_case verb_noun naming. There is no mixing of casing or verb styles, making the set predictable.
Five top-level tools are well-scoped for a video platform MCP, each covering a major capability area. Though each bundle contains many sub-actions, the high-level count avoids overwhelming agents while keeping groups coherent.
The server covers core video creation, project/template management, asset/media search, integrations, transcription/clip extraction, and account/quota/job operations. It lacks an explicit direct listing/deletion of rendered videos separate from projects and jobs, but agents can work around via project and job operations.