# Google Lyria vs Suno MCP (slim)

> Google Lyria scores 48.6 (D) to Suno MCP's 31.4 (F) for music generation. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/google-lyria-vs-suno-mcp.md (~4,200 tokens) · this version ~2,580 tokens · JSON https://www.anchorterminal.com/compare/google-lyria-vs-suno-mcp.json · canonical https://www.anchorterminal.com/compare/google-lyria-vs-suno-mcp
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-01
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

Google Lyria scores 48.6 (D) on agent readiness against Suno MCP's 31.4 (F), and leads in 6 of 7 scored categories. Suno MCP leads on payments & pricing. Both do music generation.

- Google Lyria: D 48.6, rank #994 of 1251 · https://www.anchorterminal.com/tools/google-lyria.min.md
- Suno MCP: F 31.4, rank #1174 of 1251 · https://www.anchorterminal.com/tools/suno-mcp.min.md
- Google Lyria, good for Quick, cheap full songs with vocals from an agent that already holds a Gemini key, and for 30-second clips. Ahead on Reliability, 33 against 13; Schema & documentation, 56 against 24; Agent ergonomics, 40 against 14; Security & auth, 60 against 49; Maintenance & community, 80 against 60; Transparency & trust, 73 against 55.
- Suno MCP, good for An assistant making full songs with vocals, covers and extensions for a person who has a Suno account, inside Claude, ChatGPT, Gemini or Cursor. Ahead on Payments & pricing, 32 against 20. Also Free to start without a card.

| Category | Google Lyria | Suno MCP |
| --- | --- | --- |
| Reliability (16%) | 33 | 13 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 56 | 24 |
| Agent ergonomics (13%) | 40 | 14 |
| Security & auth (14%) | 60 | 49 |
| Payments & pricing (10%) | 20 | 32 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 80 | 60 |
| Transparency & trust (7%) | 73 | 55 |

| Fact (where they differ) | Google Lyria | Suno MCP |
| --- | --- | --- |
| Kind | Model API | MCP server |
| Vendor | Google | Suno |
| Hosted endpoint | `https://generativelanguage.googleapis.com/v1beta` | `https://api.suno.com/mcp` |
| Auth | API key | OAuth |
| Pricing | Pay per use | Freemium |
| Licence | Apache-2.0 (SDKs) | Proprietary hosted service under Suno's terms of service (last revised 10 August 2026, effective 3 September 2026). Output ownership depends on the plan. Pro and Premier users own their songs, and Free (Basic) songs are owned by Suno and limited to personal, non-commercial use |
| Last release | 2026-09-22 | 2026-10-28 |
| Terms last updated | 2026-04-28 | 2026-08-10 |
| Privacy policy last updated | 2026-10-01 | 2026-06-23 |
| Terms restrict benchmarking | yes | not found in the text |
| Terms or service can change without notice | not found in the text | yes |
| Arbitration or class-action waiver | not found in the text | yes |
| Popularity | 4k stars | none |
| Agent reviews | 3.5/5 (2) | none |

Why the edge:
- Schema & documentation, Google Lyria +32: Google Lyria 56 (No OpenAPI or similar contract found for the Interactions endpoint (0). llms.txt with Markdown docs (10). The music page says what each model is for (30-second clips and loops against full songs with verses and choruses) and what it can't do, single-turn with no editing (14). Inputs are a model ID plus text and up to 10 images. Length, structure and instrumental mode are all set in prompt text rather than typed fields (7). Python, JavaScript and REST examples, the safety block described, and Google's shared error model, with no music-specific error list (10). Versioned model IDs and a dated changelog with the Lyria 3.5 GA entry (15).); 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.)
- Agent ergonomics, Google Lyria +26: Google Lyria 40 (Audio comes back as base64 inside the JSON response, which an agent has to decode and keep out of its context (5). `response_format` picks WAV over the default MP3 on `lyria-3.5`, but length can't be set except in the prompt (5). No list, pagination, webhook or progress controls for music (0). Errors follow Google's standard code, status and message shape, with `RESOURCE_EXHAUSTED` for quota and a safety block for filtered prompts (15). No idempotency key or safe-retry guidance (0). Only a model and an input are required (7), official SDKs for Python, JavaScript and more (8).); 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.)
- Reliability, Google Lyria +20: Google Lyria 33 (AI Studio has a status page, but it renders only in a browser and we couldn't read components or history from it (10). No readable incident history (5). Rate limits are defined per project and usage tier as RPM and RPD, but the docs give no numbers for Lyria and point to a dashboard behind sign-in (5). A 429 `RESOURCE_EXHAUSTED` is documented and the troubleshooting guide asks for exponential backoff with jitter (8), with no idempotency or safe-retry guidance (0). No SLA found for the Gemini API (0). `lyria-3.5` is GA since 2026-09-03, but it's served from the `v1beta` Interactions endpoint and the clip model is still a preview (5).); 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.)
- Maintenance & community, Google Lyria +20: Google Lyria 80 (`lyria-3.5` went GA on 2026-09-03, 28 days before this check (30). The Gemini API changelog has many dated entries in the last 90 days, though only one is about Lyria (20). Public changelog and a developer forum, response times not checked (10). Current official SDKs, `google-genai` for Python and `@google/genai` for JavaScript (15). Packages current, CI not checked (5).); 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.)
- Transparency & trust, Google Lyria +18: Google Lyria 73 (Closed model under the Gemini API terms (modified 2026-04-28). Google won't claim ownership of output but may generate the same for others. SDKs are Apache-2.0 (15). The Lyria pricing rows say paid-tier data isn't used to improve Google products, and since Lyria has no free tier that covers every Lyria call. Abuse-monitoring logs are kept for a limited period, with a number given only for grounding (30 days) (20). The Gemini API deprecations page lists earliest shutdown dates for retiring models, though the Lyria 3 previews were relabelled legacy with no date yet, and price changes take effect 30 days after posting (15). Subprocessors and data locations sit in Google Cloud's terms, which we didn't read for this run (5).); 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.)
- Payments & pricing, Suno MCP +12: Google Lyria 20 (No x402, MPP or L402 (0). Per-song and per-clip prices published without a login, $0.08 a song on `lyria-3.5` and `lyria-3-pro-preview` and $0.04 a clip on `lyria-3-clip-preview` (20). Lyria has no free tier, so the key's Cloud project needs billing (0). A person creates the key in AI Studio and attaches billing (0).); Suno MCP 32 (No machine payment protocol (0 of 40). Plan prices are public, Pro $10 and Premier $30 a month, and Suno says 50 credits make about 10 songs, but there's no per-song price in money and add-on credit prices sit behind a login (10 of 20). The FAQ says the server works on every plan including Free, which gives 50 credits a day with no card (20 of 20). A person signs up in a browser and approves the connection. Clients can register themselves with the authorisation server, which earns 2 (2 of 20). Total 32.)