FlowMusicAI 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 |
|---|---|
| get_pricingA | Return the canonical pricing entry point for the site so an agent can cite plans without scraping. (FlowMusicAI) |
| get_official_linksA | Return the canonical list of official links for FlowMusicAI (website, support, docs when available). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| tell_me_about_flowmusicai | Summarize what the site is, who it's for, and how it works. — FlowMusicAI |
| compare_pricing_flowmusicai | Compare available plans for a stated workload and pick one. — FlowMusicAI |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| plans | Public plan information surfaced on the pricing page. |
| pricing | Canonical pricing entry point. |
| docs | Canonical documentation entry point. |
| faq | Short FAQ generated from public site metadata. |
| links | Canonical URLs to share with users. |
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: one retrieves pricing plans, the other retrieves official links. There is no overlap or ambiguity.
Both tools follow a consistent verb_noun pattern (get_pricing, get_official_links), using snake_case and the verb 'get'.
With only 2 tools, the count is slightly low, but for a server focused solely on providing static informational resources (pricing and links), the scope is narrow enough that this number is reasonable.
The server covers only two informational needs. For a music AI service, tools for features, documentation, or support are missing, leaving significant gaps that agents may need to work around.