SongUp AI has published a read-only Model Context Protocol (MCP) server that lets compatible assistants search its song library, prepare a custom-song link and find browser-based audio utilities. The endpoint uses Streamable HTTP, requires no account or API key, and supports connections from tools including Claude Code, Cursor, VS Code, Zapier, Make and n8n, according to SongUp’s MCP documentation.
The boundary worth noting is what happens after a tool call. A search returns existing songs with direct audio links. A custom-song request returns a link to a pre-filled creation page. An audio-tool request returns links to relevant utilities. None of these calls generates a song, takes payment or changes user data.
That makes this a discovery and handoff integration. I’d evaluate it on how neatly those links fit into a workflow, with song generation treated as a separate step. The details below analyze SongUp’s published instructions; they are not results from hands-on testing.
The Endpoint and Connection Settings
SongUp publishes these connection details on its setup page:
| Setting | Value |
|---|---|
| Server URL | https://www.songupai.com/mcp/agents |
| Transport | Streamable HTTP |
| Authentication | None |
| Account or API key | Not required for the MCP endpoint |
| Tool permissions | Read-only |
MCP gives compatible clients a standard way to discover and call a server’s tools. Here, the client connects directly to SongUp’s hosted HTTP endpoint. The documented configurations do not require running a separate SongUp server locally.
The endpoint is shared across the listed integrations, but each application uses its own configuration format. VS Code’s configuration uses servers, while Cursor and Windsurf use mcpServers.
Claude Code
SongUp provides this terminal command:
claude mcp add --transport http songup-ai https://www.songupai.com/mcp/agents
The command registers a server named songup-ai with Claude Code using HTTP transport. It configures the connection; it does not search for music or create a song.
Cursor
Add the following to ~/.cursor/mcp.json, or use .cursor/mcp.json inside a project:
{
"mcpServers": {
"songup-ai": {
"url": "https://www.songupai.com/mcp/agents"
}
}
}
The first location is the user-level configuration path supplied by SongUp. The second lets you keep the connection definition with a particular project.
VS Code With GitHub Copilot
SongUp’s VS Code example belongs in .vscode/mcp.json:
{
"servers": {
"songup-ai": {
"type": "http",
"url": "https://www.songupai.com/mcp/agents"
}
}
}
Keep the type field and the servers wrapper shown here. Copying Cursor’s configuration unchanged would miss the format SongUp documents for VS Code.
Windsurf
For Windsurf, SongUp specifies ~/.codeium/windsurf/mcp_config.json:
{
"mcpServers": {
"songup-ai": {
"serverUrl": "https://www.songupai.com/mcp/agents"
}
}
}
Notice the serverUrl property. All four clients connect to the same endpoint, but the configuration keys are not interchangeable.
What the Three Tools Actually Return
The server exposes three tools, each with a narrow purpose. SongUp’s tool descriptions make the distinction between discovery and execution explicit.
| Tool | Inputs described by SongUp | Returned result |
|---|---|---|
find_songs | Song language, optional genre, mood or occasion words, and a requested count of up to 10 | Existing library songs, each with a direct audio link |
start_custom_song | A song idea of up to 500 characters, plus an optional language | A link that opens the song maker with the idea filled in |
find_audio_tool | A description of the desired audio task | Up to three browser-tool links, such as a stem separator, vocal remover, mashup maker or audio editor |
The name start_custom_song can sound like an instruction to begin generation, but the documented result is a prepared link. The song itself is made on SongUp’s website with a SongUp account.
Likewise, find_audio_tool selects utilities. Asking it for vocal removal returns a route to a browser tool; the MCP call does not itself separate vocals from an uploaded track.
The search limit also shapes the workflow. A call to find_songs can return at most 10 songs. That suits a short recommendation list, but the documented behavior should not be treated as a bulk catalog export.
Connecting Zapier, Make and n8n
SongUp lists an MCP connection path for all three automation platforms:
- Zapier: Add a step using the MCP Client app, create a connection with the server URL, choose Streamable HTTP and no authentication, then select a SongUp tool as the action.
- Make: Add the MCP Client module, create a connection using the server URL and no authentication, select a tool, and map its inputs.
- n8n: Attach an MCP Client Tool to an AI Agent node. Set the endpoint to the SongUp URL, choose HTTP Streamable, and set authentication to None.
These instructions come from SongUp’s integration page. The useful setup check is that the endpoint, transport and authentication settings all match. A server URL alone is only part of the configuration.
Once connected, the automation still needs to decide what to do with the returned links. Finding a song and posting it to Slack are separate actions. SongUp supplies the discovery result; the surrounding workflow handles delivery.
Two Workflows That Fit the Read-Only Design
SongUp suggests posting a song in a customer’s language to Slack each week. A workflow could take the language from a customer record, call find_songs with an occasion or mood, and pass a selected audio link to a Slack step.
The result would be a recommendation from SongUp’s existing library. It would not be a newly generated song based on the customer’s information. That distinction should stay visible in the message sent to the recipient.
A second example is a birthday-song handoff. An automation could assemble a short idea from an occasion, a name and an approved message, then send that text to start_custom_song. The returned link would open the song maker with the idea already filled in.
The 500-character input limit makes a compact brief useful. A workflow should check the length before making the call, particularly when combining several database fields.
My view is that this second use case fits the release especially well: automation handles the reminder and drafting, while the recipient continues on the creation site. The documented boundary is clear, and the workflow can stop successfully after delivering the prepared link.
For fully automated song creation in code, Zapier, Make or n8n, SongUp directs users to its separate API. The MCP setup page does not provide the API’s authentication, pricing or generation-job details, so those requirements need checking before planning an end-to-end generation pipeline.
Frequently Asked Questions
3 questions
1Do I Need a SongUp Account or API Key?
Neither is required to connect to the MCP server. Creating a custom song through the linked SongUp website requires a SongUp account.
