Loudly Music API vs Suno MCP

Loudly Music API 3

No dated release, changelog entry or API change found (0). No dated entries in the last 90 days (0). No public changelog. Support is help@loudly.com (3). No official SDK (0). No package 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.

Loudly Music API 75

Public OpenAPI 3.0 spec covering 19 paths across account, catalogue, generation, Manta, remix, mastering and stems (25). The site has an llms.txt, but it only links to the Music API page, with no agent-facing API docs (5). Every operation carries a description, though few say when not to use one (14). Enums for energy, key root and quality, model version (VEGA_1, VEGA_2) and stem model, a 30 to 420 second range for duration, and genres fetched from an endpoint rather than enumerated in the spec (13). Error schemas with example payloads for 400, 402, 403, 404 and 500 (13). Version 1.0.0 in the spec, no public changelog (5).

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.

Loudly Music API 51

Responses are JSON with track URLs (15) and duration is a parameter, but we found no output format choice in the spec (5). List endpoints take page and limit and return page metadata (10). Error payloads name the cause, including 402 for credits and 403 when the Manta flag is off, with no 429 documented (15). No idempotency key or retry guidance, and test=true helps wiring but not retries (0). Genre, BPM and instrument values must match the genres endpoint, and requests are multipart form data (6). No official SDK (0).

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.

Loudly Music API 35

A plain key from the self-serve developer portal in an API-KEY header, with no scopes, rotation or expiry documented (20). No least-privilege or read-only mode (0). Returns generated audio and catalogue metadata from Loudly's own library, no untrusted content (10). A credits endpoint shows the balance, with no per-call log found (5). No security.txt, disclosure policy, bug bounty or certification found (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.