Use them when developing the ZapCap server, including video uploads, URL-based uploads, template retrieval and processing-task creation or monitoring.

They give an agent the context needed to work in the repository without guessing how it is organised or how dependencies are managed. This reduces mistakes when changing or extending the integration.

How bogdanminko/zapcap-mcp-server configures Claude Code

Q: What is zapcap-mcp-server CLAUDE.md?

Project instructions for an unofficial server that connects coding agents to ZapCap, a video-processing and caption-generation service. They describe the project structure, package management and available server tools.

Reuse

Borrowing it

Nothing to install: this file belongs to bogdanminko/zapcap-mcp-server. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/bogdanminko/zapcap-mcp-server/main/CLAUDE.md

Clone the repo

git clone --depth 1 https://github.com/bogdanminko/zapcap-mcp-server

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/bogdanminko/zapcap-mcp-server/claude-md/github.svg)](https://agentmods.dev/instructions/bogdanminko/zapcap-mcp-server/claude-md)

Your own site

<a href="https://agentmods.dev/instructions/bogdanminko/zapcap-mcp-server/claude-md"><img src="https://agentmods.dev/badge/instructions/bogdanminko/zapcap-mcp-server/claude-md/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/bogdanminko/zapcap-mcp-server/claude-md"><img src="https://agentmods.dev/badge/instructions/bogdanminko/zapcap-mcp-server/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 646 This file is loaded in full into every session.

When invoked 646 The same file — it is already loaded in full.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00646	$0.00646
Opus 5	$0.00323	$0.00323
Sonnet 5	$0.00129	$0.00129
Haiku 4.5	$0.00065	$0.00065

Measured 9d ago against content hash 91b6acaa810c, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

zapcap-mcp-server CLAUDE.md scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

CLAUDE.md · 66 lines

How it starts

The opening of the file, as written. The whole thing — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.

ZapCap MCP Server

Overview

This is an unofficial MCP (Model Context Protocol) server implementation for ZapCap.ai - a video processing and caption generation service. The server provides tools for uploading videos, creating processing tasks, and monitoring their progress through the ZapCap API.

Project Structure

zapcap-mcp-server/
├── src/
│   └── server.py          # Main MCP server implementation
├── main.py                # Entry point (placeholder)
├── pyproject.toml         # Project configuration and dependencies
├── README.md              # Basic project documentation
└── uv.lock               # Lock file for uv package manager

Package Management

This project uses uv as the package manager instead of pip. All dependencies are managed through pyproject.toml and locked in uv.lock.

Architecture

The server is built using the FastMCP framework and provides the following tools:

Available Tools

zapcap_mcp_upload_video - Upload video files to ZapCap
zapcap_mcp_upload_video_by_url - Upload videos by URL
zapcap_mcp_get_templates - Get available processing templates
zapcap_mcp_create_task - Create video processing tasks with full customization
zapcap_mcp_monitor_task - Monitor task progress

Dependencies

mcp[cli]>=1.10.1 - MCP server framework
httpx>=0.28.1 - HTTP client for API requests
pydantic>=2.11.7 - Data validation and serialization

Configuration

The server requires the ZAPCAP_API_KEY environment variable to be set for authentication with the ZapCap API.

API Integration

The server integrates with the ZapCap API endpoints:

https://api.zapcap.ai/videos - Video upload
https://api.zapcap.ai/videos/url - Upload by URL
https://api.zapcap.ai/videos/{video_id}/task - Task creation
https://api.zapcap.ai/videos/{video_id}/task/{task_id} - Task monitoring

Data Models

The server defines several Pydantic models for request validation:

UploadVideo - File path for video upload
UploadVideoByUrl - URL for video upload
CreateTask - Task creation parameters with full customization options
MonitorTask - Task monitoring parameters

Read the full file on GitHub · 66 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

9d ago First seen · 66 lines · 646 tokens per session scan A 91b6acaa810c

Subscribe to this mod's changes

zapcap-mcp-server CLAUDE.md is an instructions file published in the GitHub repository bogdanminko/zapcap-mcp-server (1 stars, last pushed 12mo ago), licensed MIT. It adds 646 tokens to every session, about $0.0032 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Creative and media

next.js AGENTS.md

AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,296 tokens

codex AGENTS.md

AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.

openai/codex · 5,153 tokens

vscode buildNext.instructions.md

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 6,785 tokens

zapcap-mcp-server: Instructions file for Claude Code