vidhook-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| VIDHOOK_API_KEY | Yes | Your vidhook API key. Missing/empty fails startup (fail-closed). | |
| VIDHOOK_API_BASE_URL | No | API base URL. | https://api.vidhook.app |
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 |
|---|---|
| validateA | Validate a Movie definition (and optional webhook) WITHOUT starting a render or consuming any credits, and return the estimated credit cost. Use this to preview cost and catch errors before calling render. estimatedCredits equals the credits render would reserve for the same body. Invalid Movies or SSRF-rejected webhook URLs are returned as errors (HTTP 400) from the API. Authentication and watermarking are set by the VIDHOOK_API_KEY environment variable only (never a tool argument): vh_test_… renders a free/watermarked draft, vh_live_… renders clean/paid. The target environment is selected independently by VIDHOOK_API_BASE_URL (base URL), not by the key type. |
| renderA | Submit a Movie definition (and optional webhook) and start an asynchronous render. Reserves credits and returns renderId, bucketName, and reservedCredits. Poll progress with get_status using the returned renderId and bucketName. All asset references must be URLs (vidhook does not generate assets). Insufficient credits return an error (HTTP 402). Authentication and watermarking are set by the VIDHOOK_API_KEY environment variable only (never a tool argument): vh_test_… renders a free/watermarked draft, vh_live_… renders clean/paid. The target environment is selected independently by VIDHOOK_API_BASE_URL (base URL), not by the key type. |
| get_statusA | Poll the progress of a render started with the render tool. When done is true and fatalErrorEncountered is false, outputFile holds the result video URL. Pass the renderId and bucketName returned by render. |
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 3 tools
Each tool has a distinct purpose: render starts an async render, get_status polls its progress, and validate checks definitions without consuming credits. No overlap.
All tool names follow a consistent verb_noun pattern (get_status, render, validate), making them predictable and clear.
Three tools is appropriate for the server's purpose—submitting renders, polling status, and validating definitions—without being too few or excessive.
The tools cover the essential workflow (validate, render, get_status) for the video rendering service. No obvious gaps given the API's scope.