media-mcp monorepo
English | 中文
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.
Power your agent
The publisher's own command. Not a PlugMCP endpoint.
Host a copy with our keys and logs.
npx -y @avclabs.ai/[email protected]Claude Code has no install link for a local command. Copy the command below and run it in a terminal.
API_KEY=<secret> claude mcp add io.github.avclabs-media-mcp -- npx -y @avclabs.ai/media-mcp@0.2.0Run in a terminal.
{ "mcpServers": { "io.github.avclabs-media-mcp": { "command": "npx", "args": [ "-y", "@avclabs.ai/[email protected]" ], "env": { "API_KEY": "<secret>" } } }}claude_desktop_config.json
Remote URL or a command on your machine? How the two installs differ
Run on PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
LaunchFrom the publisher
English | 中文
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.
MCP Server for video enhancement and image segmentation (SAM3)
get_*_task_status variant present,
the model picks tools more reliably.The legacy all-in-one @avclabs.ai/media-mcp keeps working unchanged for
existing configurations; see its README for a
migration note.
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).
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/.
npm ci # installs workspaces and builds every package
npm test # rebuild + run all package tests
npm run release:verify # metadata gate + audit + tests + pack dry-run
node 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.
MIT License — see LICENSE.
© 2026 MCP Directory.
MCP Server for video enhancement and image segmentation (SAM3)
{ "mcpServers": { "io.github.avclabs-media-mcp": { "command": "npx", "args": [ "-y", "@avclabs.ai/[email protected]" ], "env": { "API_KEY": "<secret>" } } }}Tools
No tool list yet. Remote servers get one after the first health check.
FAQ
Copy the stdio config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.
The publisher lists these environment variables: API_KEY.
Media runs locally over stdio.
Last checked 2026-11-09. MCP Server for video enhancement and image segmentation (SAM3)