MusicGPT API vs Suno MCP

MusicGPT API 78

A public OpenAPI 3.1 file with 27 operations (25). llms.txt and a Markdown copy of every page (10). Each operation has a one-line purpose and the guides add notes such as voice_id forcing the v6 model, with little on when not to use an endpoint (11). Schemas are inline with no shared components, 12 of 23 request bodies name required fields, and gender on /v2/MusicAI is a free string although the guide lists three values. Stems travel as a JSON string inside a form field (9). Every operation has an example, and the error page lists 11 codes, while the file documents only 402, 422 and 500 (11). /v1 and /v2 paths and a changelog dated by month (12).

Suno MCP 24

Suno doesn't publish the server's tool list, and the tool definitions can be read only after signing in, which this run didn't do, so no contract is public (0 of 25). suno.com/llms.txt is Markdown written for agents but describes the app as of 29 May 2026 and says nothing about the MCP server (5 of 10). suno.com/mcp and the help article list what the server does (songs, covers, extensions, mashups, Speech, uploads, Voices, playlists, credits) without per-tool purpose or when not to call (5 of 20). Typed inputs weren't readable (0 of 15). Three example prompts on suno.com/mcp, and only the 401 with its resource metadata is documented as an error (4 of 15). Dated release notes with an entry for the launch, but no server version or MCP changelog (10 of 15). Total 24.

MusicGPT API 54

Creates return a small JSON task with an eta and a credit_estimate, but music requests always make two versions and Music AI V2 sends up to seven webhooks a request (15). limit and page on the two voice lists, polling by task_id or conversion_id, and no call that lists past conversions (10). One error body with error_code and message and 11 documented codes (16). No idempotency key is documented and 409 CONFLICT is described only in general terms (3). /v2/MusicAI has no required field and defaults to v6. SDKs are published for Node and Python, and the npm package dates from 16 June 2025 (10).

Suno MCP 14

Tool count and definition size couldn't be read without signing in, so context cost scores as not found (0 of 25). The library:search scope shows library search exists, with no paging or size controls documented (5 of 20). Only the 401 is documented (4 of 20). Idempotency and readOnlyHint or destructiveHint annotations couldn't be read (0 of 20). Setup needs no API key and Suno's examples are plain requests, but required parameters are unknown, and an MCP server needs no SDK (5 of 15). Total 14.

MusicGPT API 33

The newest changelog entry is labelled September 2026 with no day, so recency is scored within 90 days (20). Two entries fall in the last 90 days, August and September 2026 (0). A public changelog and an API support address with a stated 24 hour response, with no public issue tracker (8). Official SDKs exist on npm and PyPI, but npm musicgpt 1.0.1 dates from 16 June 2025 and names no repository (5). No public repository or CI to judge (0).

Suno MCP 60

The server launched on 28 October 2026, four days before this check (30). The release notes have 13 dated entries since 3 August 2026, one of them about the MCP server (20). Public release notes, a help centre with an MCP category, a support email and a Discord server, with response times not checked (10 of 25). Not in the official MCP registry under a Suno namespace. The two Suno entries there are third-party wrappers (0 of 15). No package to judge (0 of 10). Total 60.

MusicGPT API 37

Graded as a hosted API. No status page is linked from the docs, the home page or the API page (0). No readable incident history (5). Limits are published per plan, 1, 3 or 10 parallel requests per feature group and 20, 200 or 500 GET /v1/byId calls a minute (15). The error page names 429 TOO_MANY_REQUESTS and asks for exponential backoff, with no Retry-After header and no idempotency key documented (7). No SLA found. The API page claims 99 per cent server uptime with no terms behind it (0). POST /v2/MusicAI is not labelled beta (10).

Suno MCP 13

Read with the hosted lines, because the surface an agent uses is the remote server at api.suno.com/mcp. No official status page was found, and status.suno.com doesn't resolve (0 of 20). No readable incident history (5 of 30). No rate limit is published for the server. The plan table gives generation concurrency, 4 at once in a shared queue on Free and 10 in a priority queue on Pro and Premier, with daily or monthly credits, which we count in part (8 of 15). No 429, Retry-After or backoff guidance (0 of 15). No SLA (0 of 10). The server is labelled beta, and the page asks for early access (0 of 10). Total 13.

MusicGPT API 35

Named API keys created in the API dashboard and sent as the raw Authorization header value. No scopes, expiry or rotation are documented (20). No read-only or restricted key (0). Output is generated audio, lyrics and transcripts of the caller's own files, so no third-party content (10). Each conversion can be fetched by ID with its conversion_cost, and no audit log was found (5). /.well-known/security.txt answers 404, and no disclosure policy, bug bounty or certification was found on the pages read. No webhook signature is documented (0).

Suno MCP 49

OAuth on Suno's own authorisation server, with authorisation code and PKCE S256, refresh tokens, a revocation endpoint, open client registration, client ID metadata documents and bearer tokens in the header only. The resource lists eight scopes and keeps spending credits in its own credits:spend scope (30 of 30). The scopes separate reading, searching, writing the library and spending, but no read-only connection, spending cap or confirmation step is documented, and the consent screen wasn't seen (6 of 20). Results come from the user's own library and Suno's generation, with lyrics and titles that may come from shared or remixed songs, and no injection guidance (8 of 15). Every song lands in the library and the credit balance can be checked, with no per-call log (5 of 15). No security.txt on suno.com or api.suno.com, and no disclosure policy, bug bounty or certification found (0 of 20). Total 49.

MusicGPT API 49

Closed service under one 14-section Terms of Service dated 1 January 2025 that covers the whole platform, with no API-specific terms. Paid plans carry commercial rights to output (12). The privacy policy is ten short sections. It says prompts and uploads may be used to train models after anonymisation and gives no retention periods. The changelog says MP3 files are kept 90 days and WAV files 7 days. No DPA found (10). The changelog gives dated notices, such as WAV files leaving webhooks on 9 February 2026 and new prices from 1 August, with no written policy and no removal date for Music AI V1 (10). No sub-processor list or data locations found (0).

Suno MCP 55

A closed service whose terms (effective 3 September 2026) are clear on output. Pro and Premier users are assigned Suno's rights in their output, Free users may use theirs only for personal, non-commercial purposes, and the help centre says Suno owns Free-plan songs (15 of 30). The privacy notice (23 June 2026) says submissions, chat information and other content are used to train Suno's models, gives no retention periods, and says nothing specific about what an assistant sends through the MCP server (10 of 30). The terms allow any part of the service to change or stop without notice, and the v6 post says older models will be retired without dates (5 of 20). Data is stored in the United States, and service providers are described by category with no named list (8 of 20). Total 38.