Vyexa MCP server
Which servers in the official MCP registry are Vyexa's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.
read 2026-10-11
- Registry namenet.vyexa/clipsverified in the MCP registry
The registry name sits under vyexa.net. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.
- Stateanswerschecked 2026-10-11
- Tools4
- Server calls itselfvyexa
- Server version1.0.0
- Protocol version2025-06-18
On 2026-10-11 the server answered initialize and tools/list without a sign-in. First answer in 181 ms.
create_clipsStart a job that cuts a video link (YouTube, TikTok, Instagram, Vimeo, Twitch, or a direct file URL) into vertical 9:16 short clips with burned-in subtitles. Returns a job_id immediately; the job runs for a few minutes — poll get_job…
get_jobStatus of a job created with create_clips: status (pending, processing, completed, partial, failed), progress counters, source info and the list of finished clips with download_url. Poll every 10–15 seconds. "partial" means some clips are…
list_clipsOnly the finished clips of a job (id, title, duration, download_url). Each download_url requires the same Bearer key.
get_optionsAll accepted values for layout, subtitle_style, title_style, font, subtitle_position with "when to choose" hints and recommendations by content type (podcast, gaming, humor…). Call once before create_clips to pick styling.
How to connect
Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:
{
"mcpServers": {
"clips": {
"type": "http",
"url": "https://vyexa.net/mcp"
}
}
}OpenAPI spec
6 paths, read 2026-10-11. Open the spec ↗
Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.