
Botverse
- botverse/botverse-mcp
Botverse MCP is a MCP server that lets agents run hosted video transcoding and document conversion jobs with per-job billing via API key or connector URL.
About
Botverse MCP connects coding agents to managed video transcoding and document conversion through Botverse Cloud. Developers often hit a wall when an agent needs to normalize uploads—transcode screen recordings, convert Office exports, or prep assets—without maintaining FFmpeg workers or conversion microservices. Botverse positions itself as per-job billing with no infrastructure, which suits sporadic agent-driven jobs more than always-on media farms. Configuration supports a live API key (bv_live_…) or a session connector URL with token, with the connector path called out for claude.ai and browser clients. The package ships as stdio transport over npm, matching local Claude Code and Cursor workflows. Place it on the Build integrations shelf when your product or internal agent pipeline needs reliable format transforms delegated to a hosted service.
- Video transcoding and document conversion exposed for AI agents via MCP
- Per-job billing with no infrastructure to operate on your side
- stdio npm package botverse-mcp (v1.0.2) with BOTVERSE_API_KEY or connector URL auth
- Connector URL option recommended for claude.ai and browser MCP clients
Botverse by the numbers
- Data as of Jul 7, 2026 (Skillselion catalog sync)
claude mcp add --env BOTVERSE_API_KEY=YOUR_BOTVERSE_API_KEY --env BOTVERSE_CONNECTOR_URL=YOUR_BOTVERSE_CONNECTOR_URL botverse-mcp -- npx -y botverse-mcpAdd your badge
Show developers this MCP server is listed on Skillselion. Paste this into your README.
| Package | botverse-mcp |
|---|---|
| Transport | STDIO |
| Auth | Required |
| Repository | botverse/botverse-mcp ↗ |
What it does
Offload video transcoding and document conversion from your agent to Botverse’s per-job API instead of running FFmpeg pipelines yourself.
Who is it for?
Best when you're adding upload pipelines, content tools, or agent automations that occasionally need heavy media or document format changes.
Skip if: Products that require fully offline conversion, unlimited batch at fixed cost, or fine-grained on-prem codec control.
What you get
After you configure BOTVERSE_API_KEY or the connector URL, your agent can submit conversion jobs through MCP without running media infrastructure.
- Agent-triggered transcoding and document conversion jobs on Botverse Cloud
- MCP integration without operating dedicated conversion servers
By the numbers
- Package version 1.0.2 (botverse-mcp on npm)
- Auth via BOTVERSE_API_KEY or BOTVERSE_CONNECTOR_URL
- Repository: github.com/botverse/botverse-mcp
Recommended MCP Servers
How it compares
Hosted per-job media API via MCP, not a free local FFmpeg skill or static file toolbox.
FAQ
Who is Botverse MCP for?
Botverse MCP is for developers using AI agents who want outsourced video transcoding and document conversion with billing per job instead of self-hosted media workers.
When should I use Botverse MCP?
Use it in Build when your agent workflow must transform user uploads or generated media and you prefer a Botverse API over maintaining conversion infrastructure.
How do I add Botverse MCP to my agent?
Install the botverse-mcp npm package, set BOTVERSE_API_KEY from the Botverse dashboard or BOTVERSE_CONNECTOR_URL for browser clients, and register the stdio MCP server in your agent config.