Enhance Mcp
Wire Claude Code or Cursor to AVC Labs’ HTTP video-enhancement API so agents can upscale, denoise, or restore footage without hand-rolling REST calls.
Overview
io.github.avclabs/enhance-mcp is an MCP server for the Build phase that lets AI agents call AVC Labs’ video enhancement API over HTTP through a stdio npm bridge.
What is this MCP server?
- Stdio MCP transport via npm package @avclabs.ai/enhance-mcp (registry version 0.1.8)
- HTTP client-server bridge to AVC Labs video enhancement REST API
- Single required secret: HTTP_API_KEY for authenticated API calls
- GitHub source at avclabs/enhance-mcp for audit and local overrides
- Agent-callable enhancement workflows instead of manual dashboard uploads
- Server schema version 0.1.8 on npm identifier @avclabs.ai/enhance-mcp
- Transport type stdio with 1 required secret environment variable (HTTP_API_KEY)
- Repository: github.com/avclabs/enhance-mcp
What problem does it solve?
You want your agent to enhance video in your pipeline, but ad-hoc curl scripts and dashboard uploads break flow inside Claude Code or Cursor.
Who is it for?
Indie builders adding AI upscaling or restoration to a SaaS, CLI, or agent workflow who already have an AVC Labs API key.
Skip if: Teams that only need SAM3 image segmentation without enhancement—use media-mcp—or anyone unwilling to manage a paid HTTP API key.
What do I get? / Deliverables
After registering the server with HTTP_API_KEY set, your agent can invoke enhancement operations as MCP tools while you stay in the repo.
- Registered stdio MCP server entry pointing at @avclabs.ai/enhance-mcp
- Agent-invokable tools backed by AVC Labs video enhancement HTTP endpoints
- Repeatable enhancement steps you can script from build and ship workflows
Recommended MCP Servers
Journey fit
Video enhancement is wired while you are building product features and agent tooling, not during early idea research or post-launch SEO. This npm stdio MCP server is an external API bridge—exactly the integrations lane where solo builders connect third-party media services to their stack.
How it compares
Focused video-enhancement MCP bridge, not a multi-model generative gateway like avots-mcp.
Common Questions / FAQ
Who is io.github.avclabs/enhance-mcp for?
Solo builders and small teams that ship video features and want their coding agent to call AVC Labs enhancement from the IDE via MCP.
When should I use io.github.avclabs/enhance-mcp?
Use it in the Build integrations step when you are connecting your app or agent workflow to hosted video enhancement and need stdio MCP tooling.
How do I add io.github.avclabs/enhance-mcp to my agent?
Install @avclabs.ai/enhance-mcp from npm, set HTTP_API_KEY, add the server to your MCP config with stdio transport, then restart Claude Code, Cursor, or another compatible client.