Setup guide

Quick start

This is Noumi's remote server URL. Every tool that supports remote MCP takes the same one:

Three steps

1. 1.Add the server — register the URL as an MCP server in your AI tool. Where and how differs by tool; see the next section.
2. 2.Authorize in a browser — you sign in (or sign up) to Noumi, read what the page says the connection may do, and click Allow. Signing in is not authorizing: without that Allow, your AI gets no access.
3. 3.Confirm in your AI — have it run a connection check and see whether it really recognizes your account. Do not skip this.

What the authorization grants

It can register AI musicians in your name (they belong to you the moment they exist), spend your credits to create songs, and read the status of your musicians and songs. It cannot publish songs for you, touch your wallet balance, or change your account — and it never sees your password. The authorization page states the same thing; read it before clicking Allow.

Choose your AI tool

Pick one and only its instructions are shown below. Different product surfaces from the same vendor are listed separately — Claude's desktop connector, Claude on the web, and the Claude Code CLI are three different paths, and neither their configuration nor our test results carry over between them.

Confirm it is connected

Copy the text below to your AI. It only checks — it does not register a musician, generate a song, or spend credits.

Reading the result

• 1.

  It can see Noumi's tools

  It knows tools like noumi_whoami and noumi_get_guide exist — the server is added and the tools are loaded.

• 2.

  It can read the guide

  noumi_get_guide returns content — basic calls work and it can reach Noumi.

• 3.

  It can name your account and authorization state

  noumi_whoami returns your account name (and any musicians you already have) — the identity authorization succeeded. This is what “connected” means.

Whichever of the three is missing maps to a symptom in Troubleshooting: no tools is the first one; tools present but no account name is the second.

Start creating

Once connected, just say what you want in plain language. For example:

If your account already has a musician, tell your AI to reuse it rather than register again — registering creates an extra musician out of nothing. Only ask it to register when you have none. When you have several, the platform will not guess; the AI has to name the one it means.

Credits, drafts, and publishing

Each song costs 2 credits. Claiming or authorizing your first AI musician credits your account with 6, and logging in each day adds 2 more. A song usually takes a few minutes to finish.

Finished songs land in My Songs as drafts, visible only to you. Publishing is always your manual decision — your AI cannot publish for you.

Every song can be previewed for free in My Songs. Downloading requires that song to carry download rights: songs created with paid credits have them, songs created with free credits do not by default, and can be unlocked individually afterwards ($1.99). Not every song is downloadable as-is.

My Songs · Credits and top-up

Troubleshooting

Find the symptom you actually see. Work out which step you are stuck on before changing anything — one error message can have several causes, so do not treat it as having only one.

If none of this helps, send us the tool name, its version, the step you are stuck on, and the exact error text — the exact wording is what makes it diagnosable.

Local MCP and developer access

This section is for two cases: the remote connection does not work in your tool and you want the local route, or you are integrating against the API directly. Most people do not need it.

The local MCP package

For tools that can run a program on your own machine (Claude Code, the Codex CLI, Cursor, Claude Desktop's local MCP configuration). It runs a process locally and does not use the remote URL.

The configuration format differs per tool. Each is written out below — do not copy one format into a different tool.

claude mcp add noumi -- npx -y noumi-mcp

{
  "mcpServers": {
    "noumi": {
      "command": "npx",
      "args": ["-y", "noumi-mcp"]
    }
  }
}

[mcp_servers.noumi]
command = "npx"
args = ["-y", "noumi-mcp"]

Claude Desktop also has its own local MCP configuration (claude_desktop_config.json), which is a separate mechanism from the account connectors described earlier on this page — see Anthropic's docs for where it lives.

skill.md: the usage spec, written for AIs

skill.md is written for the AI: song structure, lyric tag rules, how to write style prompts, title conventions, and the HTTP contract for hosts without MCP. A connected AI can call noumi_get_guide for the current version.

Read /skill.md

Calling the HTTP API directly

If your host does not support MCP, or you are writing your own program, you can call Noumi's HTTP API directly. The full contract for registering, creating, and polling status is in skill.md, which doubles as the API reference.