On October 28, Suno launched Suno MCP in beta. People can connect Suno to Claude, ChatGPT, Claude Code and other MCP clients and make songs without leaving the chat: describe a song, start from a voice memo, or remix something from their library. Every song lands in their Suno library, and it's available on every plan, including Free. (Suno)

The setup is clean. There's one endpoint, https://api.suno.com/mcp, no API key, and the user signs in with their own Suno account. (Suno) That's what a consumer MCP launch should look like.

Is your SaaS agent-ready? Get your score

It's also a sign of where things are going. MCP isn't only for developer tools anymore. A consumer creative app now treats "use us from inside your AI assistant" as a feature worth announcing.

Shipping is half the job

Suno's own FAQ answers a telling question: "Why can't I find Suno in my AI assistant?" The answer is that Suno "may not appear automatically in your AI assistant's available connections," so you add it yourself as a custom connector. (Suno help center)

That's normal for a beta. But it shows the gap every SaaS team runs into after launch. A person who already knows the URL can connect. An agent, or a person asking their assistant "can you make me a song?", has to find the server first.

Here's what we saw when we looked on October 31:

  • The official MCP Registry. A search for "suno" returned 3 servers. All three are third-party wrappers, and none is published under Suno's own namespace. (MCP Registry search)
  • The AI Catalog. suno.com/.well-known/ai-catalog.json returned a 404, so there's no Server Card for a client to find from the domain.
  • llms.txt. Suno publishes one at suno.com/llms.txt, but it didn't mention MCP.

None of this is a knock on Suno. It's a beta that's a few days old. But it's the pattern we see on most launches: the server ships, and the discovery work comes later. In the meantime, an agent looking for "Suno" in the registry finds someone else's wrapper first.

That's how ghost churn starts. The user's intent was to use your product. The agent routed it somewhere else, and you never saw the request.

The discovery checklist for a new MCP server

  • Publish to the official MCP Registry under your own domain's namespace, like com.yourcompany/mcp, so you're the verified result when someone searches your name.
  • Publish /.well-known/ai-catalog.json and a Server Card so clients can go from your domain to your server without a search. (SEP-2127)
  • Mention your MCP server in /llms.txt and link the setup guide.
  • Use a predictable address, on your own domain, that you control for the long term.
  • Apply to the assistants' own connector directories where they exist, so users don't have to paste a URL.

See where your product stands

Our free Agent Readiness Check scans your site for the signals AI agents look for and gives you a score in about a minute.

Is your SaaS agent-ready? Get your score

Is your SaaS agent-ready? Get your score

Run a free Pryno readiness check on your MCP server