FlowMusicAI MCP Server
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@FlowMusicAI MCP ServerWhat are the pricing plans?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
FlowMusicAI MCP Server
Flow Music AI - Free AI Music Generator for Full Songs
A Model Context Protocol server that exposes the canonical FlowMusicAI knowledge surface — plans and pricing, pricing, docs, FAQ, official links — to MCP-compatible AI clients such as Claude Desktop, Cursor, Windsurf, and Continue. Read-only, no API keys, no quota, ~50 ms cold start.
Official website: https://flowmusicai.app
💳 About FlowMusicAI
Flow Music AI (flowmusicai.app) is a browser-based AI song generator that converts a plain-text description into a fully produced, mixed track in roughly 80 seconds. You type a one-line brief, optionally choose genre tags and a vocal mode, paste your own lyrics or let the built-in lyric assistant write them, then hit Generate. The result is a complete song — vocals, instruments, and arrangement — delivered as a downloadable MP3 with a royalty-free commercial license. No digital audio workstation, no music theory knowledge, and no post-production work is required.
Related MCP server: Producer AI MCP Server
Key Features
Prompt-to-song in about 80 seconds. A single descriptive sentence drives the full composition. Vocals, instruments, and mixing are handled end-to-end by the model.
15+ stackable genre tags. Combine Pop with Lo-Fi, Cinematic with EDM, or any other pairing. A style-weight slider and a weirdness dial let you tune how strictly the model follows the tags.
Lyrics assistant and custom lyric import. Describe a topic and the tool drafts lyrics for you, or paste your own text (up to 5,000 characters). Instrumental mode skips vocals entirely with one tap.
Multiple model versions. The composer exposes V4 through V5.5 checkpoints, letting you choose between stability and the latest capabilities.
Royalty-free commercial license with a PDF certificate. Every generated track is cleared for use in paid ads, YouTube uploads, Spotify distribution, and client deliverables. Paid plans add a downloadable certificate listing the prompt, model version, and generation timestamp.
Instant MP3 download; WAV and stems on Pro. Free and entry plans deliver an unwatered MP3 the moment generation finishes. Pro and Studio tiers add WAV export and stem separation (vocals, drums, bass, mix bus). Failed runs refund credits automatically.
C2PA-compatible inaudible watermark. Each track ships with a content-credential watermark that satisfies disclosure requirements from Spotify, YouTube, Apple Music, and TikTok without audible artifacts.
Use Cases
Short-form video creators who need background tracks for TikTok, Reels, and YouTube Shorts that will not trigger content-ID claims or royalty splits.
Podcasters building a custom intro or outro theme that matches their show's exact mood without a stock-library subscription.
Indie game developers scoring menus, levels, boss fights, and trailers without hiring a composer or paying per-track license fees.
Marketing teams and agencies running A/B tests across multiple audio beds for paid social, programmatic, and pre-roll campaigns on short turnaround.
Filmmakers and video editors sourcing cinematic cues, montage beds, and trailer stingers at any mood without navigating synchronization licensing.
Streamers and VTubers generating DMCA-clear stream loops, just-chatting background music, and intro stingers specific to their channel.
Individuals creating personal gifts such as birthday songs, wedding tunes, or anniversary surprises built around custom lyrics.
Who Is It For
Flow Music AI targets people who need original, commercially cleared audio but have no music production background and no budget for session musicians or stock libraries. The core audience spans solo content creators, indie developers, small marketing teams, and freelance video producers. Because the workflow requires only a text description and takes under two minutes per track, it fits anyone on a tight deadline who cannot afford the time or cost of traditional music licensing. New accounts receive 65 free credits — enough to produce one complete song before any payment is required — and paid plans start at $9 per month, making it accessible to hobbyists and professionals alike.
Tools
get_pricing
Return the canonical pricing entry point for the site so an agent can cite plans without scraping. (FlowMusicAI)
Input: no parameters. Returns: text/markdown.
get_official_links
Return the canonical list of official links for FlowMusicAI (website, support, docs when available).
Input: no parameters. Returns: text/markdown.
Resources
site://flowmusicai/plans— Public plan information surfaced on the pricing page.site://flowmusicai/pricing— Canonical pricing entry point.site://flowmusicai/docs— Canonical documentation entry point.site://flowmusicai/faq— Short FAQ generated from public site metadata.site://flowmusicai/links— Canonical URLs to share with users.
Prompts
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
Installation
Install via Smithery
npx -y @smithery/cli install flowmusicai-mcp --client claude(Replace claude with cursor, windsurf, or continue for those clients.)
Install from source
git clone https://github.com/rocnubie/flowmusicai-mcp.git
cd flowmusicai-mcp
pnpm installThen add to your MCP client config (claude_desktop_config.json for Claude Desktop, mcp.json for Cursor / Windsurf / Continue):
{
"mcpServers": {
"flowmusicai-mcp": {
"command": "node",
"args": [
"/absolute/path/to/flowmusicai-mcp/src/index.mjs"
]
}
}
}Debug with MCP Inspector
npx @modelcontextprotocol/inspector node src/index.mjsOfficial Links
Website: https://flowmusicai.app
Pricing: https://flowmusicai.app/pricing
Community: https://discord.gg/flowmusicai
GitHub: https://github.com/flowmusicai
Support: support@flowmusicai.app
Development
pnpm install
pnpm start # run the server over stdioLicense
MIT
Available Tools
2 toolsget_official_linksA
Return the canonical list of official links for FlowMusicAI (website, support, docs when available).
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries full burden. It indicates a read-only retrieval operation and specifies the types of links returned. It does not mention authentication or rate limits, but for a simple list retrieval this is sufficient.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, concise sentence with no wasted words. It front-loads the key action and resource.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given low complexity, no annotations, no output schema, the description is largely adequate. It could benefit from specifying the output format (e.g., JSON), but the core functionality is clear.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
There are zero parameters, so the baseline is 4. The description adds no parameter-specific information, but none is needed.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb ('Return') and resource ('canonical list of official links for FlowMusicAI'), and clearly distinguishes from the sibling tool 'get_pricing' by focusing on links rather than pricing.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
While the purpose is clear, there is no explicit guidance on when to use this tool vs. alternatives, nor any conditions or exclusions. The context is implied but not stated.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
get_pricingA
Return the canonical pricing entry point for the site so an agent can cite plans without scraping. (FlowMusicAI)
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description must disclose behavior. It indicates a reliable reference point but lacks details on return format, side effects, or data freshness.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Single sentence, front-loaded key information, no wasted words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given no parameters and no output schema, the description fully covers the tool's purpose and expected output without gaps.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
No parameters; baseline score of 4 applies. No need for parameter documentation.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description clearly states the tool returns the canonical pricing entry point, specifying the resource and action. It distinguishes from sibling get_official_links by focusing specifically on pricing.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Implies usage when needing to cite pricing plans without scraping, but does not mention when not to use or compare with sibling tool.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
2 tool updates
v0.1.0- First observed
get_official_links - First observed
get_pricing
TDQS
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.
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Connectors
AI music production assistant — audio profiling, AI mixing sessions, and service inquiries.
Free, copyright-safe AI music library for video creators and AI agents.
AI support agent platform for small businesses. Query pricing, features, and examples.
Public Cannon Studio MCP for product, pricing, workflow, model, and API answers.
Related MCP Servers
- AlicenseBqualityDmaintenanceProvides AI-powered audio generation and processing through the MusicGPT API, enabling music creation, voice conversion, audio manipulation, stem extraction, and audio analysis capabilities.24171MIT
- AlicenseAqualityCmaintenanceRead-only MCP server exposing Producer AI's music generation workflows, pricing, documentation, FAQ, and official links. Enables AI clients to retrieve product knowledge without requiring API keys.3MIT
- AlicenseAqualityCmaintenanceEnables access to AI Image Editor's image generation styles, pricing, FAQ, and official links via natural language.3MIT
- AlicenseAqualityCmaintenanceEnables AI clients to access SeedanceAI's video generation platform information, including styles, pricing, docs, and FAQ, without requiring API keys.3MIT
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/rocnubie/flowmusicai-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server