Muse AI Image MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_stylesA | Return the canonical list of image-generation styles or presets the site exposes. (Muse AI Image) |
| get_pricingA | Return the canonical pricing entry point for Muse AI Image. |
| get_official_linksA | Return the canonical list of official links for Muse AI Image (website, support, docs when available). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| tell_me_about_museaiimage | Summarize what the site is, who it's for, and how it works. — Muse AI Image |
| try_image_style_museaiimage | Recommend a starting image-generation style for a stated goal. — Muse AI Image |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| styles | Supported image-generation styles and presets. |
| pricing | Canonical pricing entry point. |
| faq | Short FAQ generated from public site metadata. |
| links | Canonical URLs to share with users. |
TDQS
Scored across 3 tools
Each tool targets a completely distinct concern: listing styles, getting pricing, and fetching official links. No overlap in purpose.
All tool names follow a consistent verb_noun pattern in snake_case (list_styles, get_pricing, get_official_links), making them predictable.
Three tools is on the low side for an image generation server, but appropriate if the server is purely informational. Borderline thin.
The tool set covers the stated informational domain (styles, pricing, links). No generation tools are present, which may be a gap if that is expected, but the descriptions do not promise generation.