English Français العربية

io.github.avclabs/media-mcp

السجل الرسمي الوسائط والتصميم

MCP Server for video enhancement and image segmentation (SAM3)

الشيفرة المصدرية التوثيق

التثبيت

أضف هذا إلى إعدادات MCP في عميلك (Claude Desktop: claude_desktop_config.json، وCursor: ‏.cursor/mcp.json، ويستخدم VS Code وغيره الصيغة نفسها «mcpServers»).

NPM package @avclabs.ai/media-mcp
Claude Code 
claude mcp add media-mcp -e 'API_KEY=<your api_key>' -- npx -y @avclabs.ai/media-mcp@0.2.0
إعداد JSON (Claude Desktop وCursor وVS Code) 
{
    "mcpServers": {
        "media-mcp": {
            "command": "npx",
            "args": [
                "-y",
                "@avclabs.ai/media-mcp@0.2.0"
            ],
            "env": {
                "API_KEY": "<your api_key>"
            }
        }
    }
}

متغيرات البيئة

  • API_KEY إلزامي سري API Key for video enhancement and SAM3 services

التوثيق

مأخوذ من ملف README للمشروع على GitHub ويُحدَّث أسبوعيًا. تفتح الروابط على GitHub.

المحتويات
  1. media-mcp monorepo
  2. Packages
  3. Why one function per package
  4. Quick start
  5. Repository layout
  6. Development and release
  7. License

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.

Packages

PackageFunctionToolsBin
@avclabs.ai/video-mcpVideo enhancementcreate_task, get_task_status, enhance_video_syncvideo-mcp
@avclabs.ai/image-mcpImage enhancement / colorization / denoisingenhance_image_sync, colorize_image_sync, denoise_image_sync, get_image_task_statusimage-mcp
@avclabs.ai/sam3-mcpSAM3 image segmentationsam3_predict, get_sam3_task_statussam3-mcp
@avclabs.ai/media-mcpLegacy all-in-one (all 9 tools)everything abovemedia-mcp
@avclabs.ai/media-mcp-coreShared internal library (not an MCP server)——

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 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.

License

MIT License — see LICENSE.

الأسئلة الشائعة

ما هو io.github.avclabs/media-mcp؟

MCP Server for video enhancement and image segmentation (SAM3)

كيف أثبّت io.github.avclabs/media-mcp؟

يعمل على جهازك. في Claude Code: claude mcp add media-mcp -e 'API_KEY=<your api_key>' -- npx -y @avclabs.ai/media-mcp@0.2.0. وفي العملاء الآخرين، الصق إعداد JSON من هذه الصفحة في إعدادات MCP الخاصة بهم.

هل يحتاج io.github.avclabs/media-mcp إلى مفتاح API؟

نعم. يتطلب API_KEY، وتضبطها في إعداداته.

هل io.github.avclabs/media-mcp مفتوح المصدر؟

نعم. شيفرته متاحة على GitHub بترخيص MIT.

من يصون io.github.avclabs/media-mcp؟

ينشره avclabs. يدرجه AI.tn لكنه لا يصونه ولا يوصي به.

من سجل MCP الرسمي. الإدراج ليس توصية: راجع شيفرة الخادم وصلاحياته قبل منحه الوصول إلى بياناتك.