
Media Mcp
Give your agent both AVC Labs video enhancement and SAM3 image segmentation from one MCP server while you build media-heavy products.
Overview
io.github.avclabs/media-mcp is an MCP server for the Build phase that exposes AVC Labs video enhancement and SAM3 image segmentation to coding agents through stdio npm.
What is this MCP server?
- npm stdio MCP @avclabs.ai/media-mcp at registry version 0.2.0
- Video enhancement plus SAM3 image segmentation in one server
- Authenticated via single required API_KEY for both service families
- Open-source repo avclabs/media-mcp on GitHub
- Broader than enhance-mcp when you need masks and cuts, not just upscale
- Registry version 0.2.0, package @avclabs.ai/media-mcp, stdio transport
- 2 capability areas documented: video enhancement and image segmentation (SAM3)
- 1 required secret: API_KEY; repo github.com/avclabs/media-mcp
What problem does it solve?
Your agent needs segmentation masks and enhanced video, but juggling separate REST docs slows integration inside the IDE.
Who is it for?
Builders shipping editor-like, ads, or automation features that combine cutouts and quality-enhanced clips.
Skip if: Projects that only need generic text-to-image across hundreds of models—avots-mcp is a better fit.
What do I get? / Deliverables
One MCP registration with API_KEY lets the agent call enhancement and SAM3 tools from the same session.
- Unified MCP tool surface for enhancement and SAM3 segmentation
- Agent workflows that generate masks and enhanced renditions without custom SDK glue
- Documented env var API_KEY in your deploy or local dev MCP profile
Recommended MCP Servers
Journey fit
Segmentation and enhancement land when you integrate multimodal AI into the product, which is core Build work rather than validation or growth analytics. Combines two hosted media APIs behind MCP tools—the textbook integrations subphase for agent-accessible computer-vision services.
How it compares
Dual-purpose AVC Labs media MCP (enhancement + SAM3), not AWS infrastructure or a 300-model creative hub.
Common Questions / FAQ
Who is io.github.avclabs/media-mcp for?
Solo developers building media or vision features who want one MCP entry for enhancement and SAM3 segmentation.
When should I use io.github.avclabs/media-mcp?
During Build integrations when your product needs agent-driven masks, cuts, or enhanced video via AVC Labs APIs.
How do I add io.github.avclabs/media-mcp to my agent?
Add @avclabs.ai/media-mcp with stdio transport, export API_KEY, register in your MCP client, and verify tool lists for enhancement and SAM3.