Suno MCP (official, remote, beta)

65/100
Last tested 2026-10-29 (Fresh: tested within 30 days) Needs credentialsNo tool call tested yet OAuth

Advisories: not yet checked

Security review: not tested

Score = points from 5 automated checks. Not a quality or security rating. Methodology

  • Install20/20
  • Handshake5/30
  • Maintenance25/25
  • Docs15/15
  • License0/10

Vendor-hosted
Official Suno MCP, beta (release note 2026-10-28 says 'Sign up for early access'; access may be limited by Suno). Our anonymous probe got a proper OAuth 401; we did not sign in. Listed under the vendor-hosted rule (Our review, Oct 24, 2026).
Sources: https://suno.com/mcp · https://suno.com/release-notes/suno-mcp-beta

Transport: Needs credentials to confirm transport · probed 2026-10-29 without credentials

Score 65/100 · Tools — · Token cost — · Compare · Last tested 2026-10-29 · Server version not reported · Remote endpoint https://api.suno.com/mcp (streamable-http)

Summary: Suno MCP (official, remote, beta) requires credentials or a backing service before it will list tools.

Evidence summary

Handshake
auth-gated
Tools listed
—
Context cost
Not measured ranking
Login
Needs OAuth sign-in
Tested
2026-10-29

Test results

TestResultPointsEvidence
installpass20Endpoint https://api.suno.com/mcp reachable over streamable-http (HTTP 401) in 0.1s; no install step for remote servers.
handshakeauth-gated5Needs credentials: vendor-hosted, OAuth sign-in required. HTTP 401 with OAuth challenge (WWW-Authenticate resource_metadata https://api.suno.com/.well-known/oauth-protected-resource/mcp; metadata lists authorization server https://studio-api-prod.suno.com/api/v2/external/oauth). We do not sign in; not counted as working until a credentialed test exists.
maintenancepass25Vendor-hosted rule: scored from vendor release note 2026-10-28 (https://suno.com/release-notes/suno-mcp-beta), 1 day before test. Registry: Not in the official MCP registry for this endpoint (registry search 'suno' on 2026-10-29 found only third-party com.sunoboard/sunoboard and io.github.AceDataCloud/mcp-suno, different endpoints).
docspass15official MCP docs page; states the endpoint URL; client setup instructions. Vendor-hosted rule: scored from the vendor's official MCP docs (https://suno.com/mcp).
licensefail0Vendor-hosted service with no public repo: no license to cite, so 0 (rule: no points without a cited source).

Local-model readiness

Not yet tested (no tools/list response without credentials).

What we tested and what we didn't

Tested on 2026-10-29

  • We attempted an MCP initialize to the vendor's hosted endpoint with no credentials and got HTTP 401, so we never reached the tool list (Method details: initialize POST answered 401; tools/list not sent)
  • Auth response: HTTP 401, WWW-Authenticate resource_metadata https://api.suno.com/.well-known/oauth-protected-resource/mcp, OAuth metadata lists authorization server https://studio-api-prod.suno.com/api/v2/external/oauth. Login is an OAuth sign-in; we did not sign in
  • Vendor docs: official MCP docs page; states the endpoint URL; client setup instructions (15/15)
  • Maintenance: dated vendor source, vendor release note 2026-10-28 (25/25)
  • License: a hosted service has no license to cite (0/10)

Not tested

  • Security: not audited (hosted service; no code to review, no permission or data-flow analysis)
  • Behaviour after signing in, or with a real account
  • Source code, repository activity or an open-source license (none published for the hosted service)
  • Performance, rate limits or load
  • Real tasks (no functional task runs yet)

Methodology: how we test (vendor-hosted rule). A high score means it responds and its vendor documents and dates it, not that it is safe to give it access to your data.

Known security issues

Not yet checked.

Monthly roundup: MCP security issues, October 2026.

Tool list changes

No tool list: this server did not list tools without credentials in our test, so tool changes are not tracked.

Raw test record (JSON)
{
  "name": "suno-remote",
  "version": null,
  "registry": "remote",
  "status": "auth-gated",
  "tested": "2026-10-29",
  "tools_count": null,
  "tools_schema_tokens_est": null,
  "deprecated": false,
  "archived": null,
  "tests": {
    "install": [
      "pass",
      20,
      "Endpoint https://api.suno.com/mcp reachable over streamable-http (HTTP 401) in 0.1s; no install step for remote servers."
    ],
    "handshake": [
      "auth-gated",
      5,
      "Needs credentials: vendor-hosted, OAuth sign-in required. HTTP 401 with OAuth challenge (WWW-Authenticate resource_metadata https://api.suno.com/.well-known/oauth-protected-resource/mcp; metadata lists authorization server https://studio-api-prod.suno.com/api/v2/external/oauth). We do not sign in; not counted as working until a credentialed test exists."
    ],
    "maintenance": [
      "pass",
      25,
      "Vendor-hosted rule: scored from vendor release note 2026-10-28 (https://suno.com/release-notes/suno-mcp-beta), 1 day before test. Registry: Not in the official MCP registry for this endpoint (registry search 'suno' on 2026-10-29 found only third-party com.sunoboard/sunoboard and io.github.AceDataCloud/mcp-suno, different endpoints)."
    ],
    "docs": [
      "pass",
      15,
      "official MCP docs page; states the endpoint URL; client setup instructions. Vendor-hosted rule: scored from the vendor's official MCP docs (https://suno.com/mcp)."
    ],
    "license": [
      "fail",
      0,
      "Vendor-hosted service with no public repo: no license to cite, so 0 (rule: no points without a cited source)."
    ]
  }
}

Install

https://api.suno.com/mcp

Tools listed

Not available (handshake did not complete without credentials).

Quick config

{
  "mcpServers": {
    "suno-mcp-official-remote-beta": {
      "type": "http",
      "url": "https://api.suno.com/mcp"
    }
  }
}

Add to config Opens the config generator with this server selected.

Setup

Without credentials it said (verbatim): Needs credentials: vendor-hosted, OAuth sign-in required. HTTP 401 with OAuth challenge (WWW-Authenticate resource_metadata https://api.suno.com/.well-known/oauth-protected-resource/mcp; metadata lists authorization server https://studio-api-prod.suno.com/api/v2/external/oauth). We do not sign in; not counted as working until a credentialed test exists.

  1. Install. No install step: it is a remote server at https://api.suno.com/mcp.
  2. Configure. Add the mcpServers entry below to your MCP client config.
  3. Verify. Restart the client and check that tools/list returns tools. In our test it did not list tools without credentials.
{
  "mcpServers": {
    "suno-mcp-official-remote-beta": {
      "type": "http",
      "url": "https://api.suno.com/mcp"
    }
  }
}

Not tested with credentials We have not tested this with real credentials.

Test history

No dated events yet.

Follow this server (RSS) · Monthly changelog

Related: MCP servers that need an OAuth sign-in · How to secure AI API keys

FAQ

Is Suno MCP (official, remote, beta) deprecated?

No. suno-remote was not deprecated or archived when we last tested it on 2026-10-29.

What replaces Suno MCP (official, remote, beta)?

Nothing; Suno MCP (official, remote, beta) is not deprecated as of 2026-10-29.

Does Suno MCP (official, remote, beta) need an API key?

Not an API key: it needs an OAuth sign-in. Without signing in, the endpoint returned HTTP 401 with an OAuth challenge and did not list tools.

Embed the badge

TestedMCP: 65/100, tested 2026-10-29

Every tested server gets a free embeddable badge. It shows the current score and test date and expires after 90 days. Testing is free; payment never changes a score.

Claim this listing · Report an issue