Ext Ops Panel
Open dashboard
Comparison

agent-media vs Veltake Studio

agent-media is a plugin bundle for AI coding tools published by gitroomhq. Marketplaces we read that list it: 1 (Community GitHub marketplaces). Veltake Studio is an MCP server published by veltake.ai. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-20. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
Marketplaceagent-mediaVeltake Studio
Community marketplace gitroomhq/agent-media Listed
Version: 2.4.2
Forks (GitHub): 21
Stars (GitHub): 81
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.0
No figure published
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

agent-media vs Veltake Studio
Factagent-mediaVeltake Studio
Marketplaces that list it11
Stars (GitHub) (differs)81No figure on GitHub
Forks (GitHub) (differs)21No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)Remote server (api.agent-media.ai/mcp)Remote server (veltake.ai/v1/mcp)
TransportStreamable HTTPStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)3Not a bundle
Licence (differs)Apache-2.0Not stated
Repository (differs)github.com/gitroomhq/agent-mediaNot stated
Changes in the last 7 days22
First seen2026-10-192026-10-19
Endpoint at the last checknot checked yetnot checked yet

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

agent-media

In its own words, on Community GitHub marketplaces:

Agent-Media is one connection for the complete media toolbox: upload and inspect references, generate or edit images, build storyboards and frames, generate video and voice, reuse characters, quote, track and compose results. Agents can combine generate_image, generate_video and generate_audio with their chosen model (seedance-2.0, seedance-2.5, gpt-image-2.5, gpt-image-2.5-flare, gpt-image-2, elevenlabs-tts), frames and references, or use make_ugc as an optional server-composed shortcut. Matching quote tools check cost before spending. Optional image upload panel: discover open_upload_panel and get_uploads for user photos, with a browser fallback and 24-hour expiry. One MCP URL, browser sign-in.

Veltake Studio

In its own words, on Official MCP Registry:

Make films, ads, images, video, speech and music in Veltake Studio from any AI agent.

How to run each

agent-media As a Claude Code plugin

Claude Code
/plugin marketplace add gitroomhq/agent-media
/plugin install agent-media@agent-media

Veltake Studio As a remote MCP server

Claude Code
claude mcp add --transport http studio https://veltake.ai/v1/mcp

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: agent-media · What it can do: Veltake Studio · Compare two other plugins

Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built