MuAPI Claude Code MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MUAPI_API_KEY | Yes | Your MuAPI API key |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| account_balanceB | Get MuAPI account balance |
| generate_imageC | Generate an image using MuAPI |
| generate_videoC | Generate a video using MuAPI |
| get_predictionC | Get prediction result by request ID |
| list_modelsA | List available MuAPI model categories |
| model_detailsC | Get details about a specific model |
| edit_imageC | Edit an image using MuAPI |
| image_to_videoC | Convert an image into a video |
| upload_fileC | Upload a file to MuAPI |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
Each tool targets a distinct resource and action. While generate_video and image_to_video both produce videos, one is a general generation and the other explicitly converts an image, making them clearly separable. get_prediction, account_balance, list_models, model_details, upload_file, and edit_image each serve a unique purpose.
Most tools follow a verb_noun pattern (generate_image, get_prediction, list_models, edit_image, upload_file). However, account_balance and model_details are noun phrases without a verb, and image_to_video uses a noun_to_noun structure, which are minor deviations from the dominant convention.
The server has 9 tools, which is well within the ideal 3-15 range for a domain-specific MCP server. Each tool covers a necessary aspect of MuAPI's image/video generation workflow without being redundant or excessive.
The tools cover core workflows: account access, model exploration, file upload, image generation and editing, video generation and conversion, and result retrieval. Minor gaps exist, such as no listing of past predictions or cancellation of in-progress tasks, but these are not critical for the server's primary purpose.