Media Mcp

media-mcp monorepo

English | 中文

[Node.js >=18] [License: MIT]

MCP servers wrapping the AVCLabs hosted media services, published as one function per npm package so an MCP client session only loads the tool definitions it actually uses.

Packages

Why one function per package

• Smaller context: MCP clients inject every tool definition (name, description, JSON schema) of each configured server into the session. A client that only needs image tools no longer pays for video and SAM3 definitions.
• Less tool ambiguity: with a single get_*_task_status variant present, the model picks tools more reliably.
• Independent enablement: expose exactly one function per client or per audience (e.g. SAM3 only for the annotation team).

The legacy all-in-one @avclabs.ai/media-mcp keeps working unchanged for existing configurations; see its README for a migration note.

Quick start

Every server is a stdio MCP server over npx. For example, image tools only:

{  "mcpServers": {    "image-mcp": {      "command": "npx",      "args": ["-y", "-p", "@avclabs.ai/image-mcp@latest", "image-mcp"],      "env": { "API_KEY": "your-api-key" }    }  }}

Each package ships exactly one bin named like the package, so plain npx -y <package> also works; the snippets use the explicit -p <package> <bin> form because it pins the exact binary regardless of how a package's bin set evolves. Each package README (video, image, SAM3) has full install instructions for Claude Code, Cursor, and global installs, plus the configuration variables it reads.

All packages share one API_KEY and the same production host defaults (https://mcp.avc.ai/enhance and https://mcp.avc.ai/sam).

Repository layout

packages/  core/       shared library: tool registration, polling, TOS upload, config  video-mcp/  video enhancement server (3 tools)  image-mcp/  image processing server (4 tools)  sam3-mcp/   SAM3 segmentation server (2 tools)  media-mcp/  legacy all-in-one server (9 tools)

Domain vocabulary shared across the packages lives in CONTEXT.md; decisions are recorded in docs/adr/.

Development and release

npm ci               # installs workspaces and builds every packagenpm test             # rebuild + run all package testsnpm run release:verify   # metadata gate + audit + tests + pack dry-runnode scripts/e2e-check.mjs  # stdio E2E for all four server entries

To iterate on one package: build core once (npm run build -w packages/core), then run npm run dev -w packages/<pkg> (tsc --watch) in another terminal.

Maintainers: see the release guide for publish order (core first), versioning, tags, and smoke tests. Publishing is manual from a clean checkout; the CI workflow runs the same verification gate on Node 22.

License

MIT License — see LICENSE.