A
licenseA
qualityB
maintenanceMCP server for AI-powered image, audio, and video generation, enabling media creation directly from Claude, Cursor, and other MCP clients.
11
39 npm
MIT
@lweight/xbrush-api-mcp
by lweight
Related Servers
Alternatives to @lweight/xbrush-api-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceAn MCP server that enables generating images via OpenAI and images/videos via Google Gemini (including Veo video generation), saving outputs to local asset folders. It integrates with Claude Code and any MCP client using your own API keys.3MIT
- FlicenseNot gradedqualityCmaintenanceRemote MCP server for Claude to generate images and videos using Higgsfield AI. Supports photo, reference-based image, and video generation.-
- AlicenseNot gradedqualityDmaintenanceMCP server that enables Claude Code to generate images using Google's Gemini image generation models.MIT
- AlicenseAqualityCmaintenanceMCP server for Claude Code that enables image generation and editing via Azure AI Foundry's MAI Image API, writing files to disk and returning only the path.3MIT
- AlicenseAqualityCmaintenanceA local MCP server that enables Claude Code and Claude Desktop to generate and edit images via OpenAI's Images API, saving finished files into the project and returning previews for iterative refinement.3MIT
TDQS
A4.2/5.0
Scored across 21 tools
Disambiguation5/5
Each tool targets a distinct resource and action: image generation/edit/upscale/remove-bg, video generation/upscale/extend/retake/lip-sync, TTS/music/sound-effect generation, chat, watermarking, moderation, and request/model/file utilities. There is no significant overlap; even similar operations like video_extend and video_retake are clearly differentiated by their descriptions and parameters.
Naming Consistency4/5
All tool names share the 'xbrush_' prefix and use domain prefixes (image_, video_, tts_, etc.) for most operations, which is predictable. However, verb placement is inconsistent: some are noun_verb (image_generate, video_extend) while others are verb_noun (list_models, get_request, check_health). This minor deviation does not hinder readability but breaks a strict pattern.
Tool Count4/5
With 21 tools, the set is on the heavier side but appropriate for a multi-modal generative AI API spanning image, video, audio, text, file upload, request polling, and model listing. Each tool serves a distinct function, and the breadth justifies the count without redundancy.
Completeness5/5
The tool surface is comprehensive: it covers the full creative lifecycle including model discovery, file upload, image generation/editing/upscaling/background removal, video generation/extension/retaking/lip-sync, audio generation (TTS, music, sound effects), chat, watermarking, moderation, and request status retrieval. Async operations uniformly reference xbrush_get_request, and there are no obvious dead ends or missing critical operations.
Maintenance
ActivityMaintained
ResponsivenessNo issues