@retomagic/mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MAGICLY_API_KEY | Yes | Your Magicly developer API key (sk_live_...) | |
| MAGICLY_API_URL | No | API base URL (override for staging) | https://api.magicly.ai/v1 |
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_modelsA | List the available Magicly models with their id, media type, price ($) and supported inputs. |
| generateA | Generate an image or video with a Magicly model. Creates a prediction and (by default) waits for the result, returning the output URL(s). Use list_models to discover model ids and their inputs. |
| get_predictionA | Get the current status and output of a prediction by its id. |
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 3 tools
Each tool has a clearly distinct purpose: generating content, checking prediction status, and listing available models. There is no overlap or ambiguity.
All tool names follow a consistent verb_noun pattern with lowercase and underscores (generate, get_prediction, list_models), making them predictable and easy to understand.
Three tools is appropriate for the server's scope: model discovery, content generation, and result retrieval. Each tool serves a necessary function without excess or deficiency.
The tool surface covers the full workflow: listing models to know available options, generating content with optional polling, and checking results asynchronously. No obvious gaps for the intended purpose.