zapcap-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ZAPCAP_API_KEY | Yes | Your ZapCap API key from https://platform.zapcap.ai/dashboard/api-key |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| zapcap_mcp_upload_videoC | Upload video file to ZapCap |
| zapcap_mcp_upload_video_by_urlC | Upload video by URL to ZapCap |
| zapcap_mcp_get_templatesC | Get available templates from ZapCap |
| zapcap_mcp_create_taskC | Create video processing task with full customization options |
| zapcap_mcp_monitor_taskD | Monitor task progress |
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
Each tool has a clearly distinct purpose: create_task for task creation, get_templates for template retrieval, monitor_task for progress tracking, and two upload tools differentiated by source (file vs. URL). No ambiguity exists between these operations.
All tools follow a consistent verb_noun pattern with the prefix 'zapcap_mcp_' (e.g., create_task, get_templates, monitor_task, upload_video, upload_video_by_url). This uniformity makes the set predictable and easy to navigate.
With 5 tools, this server is well-scoped for video processing tasks, covering essential operations like uploading, creating, monitoring, and template retrieval. Each tool earns its place without bloat or thin coverage.
The toolset covers core workflows (upload, create, monitor, templates) effectively, but lacks explicit update or delete operations for tasks or videos. Agents can likely work around this, but the absence is a minor gap in lifecycle coverage.