Axcel MCP
Related Servers
Alternatives to Axcel MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to generate professional storyboards and videos from scripts or creative descriptions via MCP-compatible clients.20 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables MCP-compatible clients to generate images and videos, synthesize speech, clone and design voices, and dynamically configure API interactions.280 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables MCP-compatible clients to generate and upscale AI images, videos, music, and sound effects, manage generation jobs, access model catalogs, and track credits.3MIT
- AlicenseNot gradedqualityCmaintenanceExposes video generation and editing tools to MCP-capable clients, enabling text-to-video, image-to-video, video editing, reusable voice and character profiles, and task status queries through natural language.4MIT
- AlicenseNot gradedqualityAmaintenanceEnables MCP-compatible clients to generate images and videos, synthesize text-to-speech audio, and clone or design custom voices. It also supports flexible output handling (URLs or local files) and multiple transport modes including stdio, REST, and SSE.280 npmMIT
- FlicenseNot gradedqualityBmaintenanceEnables AI clients like Claude and ChatGPT to generate images and videos, animate images, create lip-synced videos, list TTS voices, and manage media via remote MCP tools.-
TDQS
Scored across 34 tools
Most tools map to a distinct resource+action (generate_video, generate_image, job_status, history_get, folder_create), so boundaries are largely clear. A few pairs could be confused — axcel_job_status vs axcel_sequence_status vs axcel_active_jobs, and axcel_view vs axcel_extract_frame — but descriptions differentiate them adequately.
All tools share the axcel_ prefix, which helps grouping, but the ordering convention is mixed: noun_action (folder_list, library_list, history_list, job_status) alongside verb_noun (list_models, generate_video, extract_frame, concat_videos), plus bare nouns (status, help, billing_plans, active_jobs). It stays readable, but no single predictable pattern governs the set.
34 tools is heavy and above the comfortable 3-15 band, creating real discovery overhead. However, the surface spans several genuinely distinct areas (auth, billing, generation, jobs, history, library, folders, editing), so each tool is defensible rather than redundant.
Coverage is broad and near-complete: full auth lifecycle, generation, job handling, history CRUD, library CRUD plus move, and folder CRUD with ZIP export. Minor gaps exist (no job cancel/delete, no library rename, no history save-to-library), but agents can work around them.