What can you do with this server?

rootvine-mcp is a neutral commerce resolution layer for AI agents, enabling them to find where to stream, buy, or collect music and other media across major platforms. * resolve_music: Find streaming, digital purchase, and physical media options (vinyl, CD, collector editions) for a song or album. Returns ranked results from platforms like Spotify, Apple Music, iTunes, Amazon, Bandcamp, Discogs, YouTube Music, Tidal, and Deezer — with prices and direct links. * resolve_game: Look up where to buy a video game across stores like Steam, PlayStation, Xbox, Nintendo, and Epic Games. (Coming soon — currently returns a placeholder response.) * find_product: Submit a natural language query and let the server auto-detect the product category (music, game, or auto) and route it to the correct resolver. * Neutral ranking: Results are ranked deterministically by trust tier → price → availability → freshness → merchant ID — explicitly excluding ads, sponsored placements, or affiliate commission rates. Planned future support: books, films & TV, podcasts, and live events.

Which integrations are available for this server?

Enables music link resolution and price discovery for tracks and albums available on Amazon. Enables music link resolution and streaming availability lookups for tracks and albums on Apple Music. Enables discovery of direct links and pricing for music and albums on Bandcamp. Enables music link resolution and price discovery for purchasing tracks and albums via the iTunes Store. Enables music link resolution and streaming availability lookups for tracks, artists, and albums on Spotify. Enables music link resolution and streaming availability lookups for tracks and albums on Tidal. Enables discovery of music-related video links and availability on the YouTube platform. Enables music link resolution and streaming availability lookups for tracks and albums on YouTube Music.

de en es ja ko ru zh

rootvine-mcp

by RagingOrangutan

Overview Schema Related Servers Score Discussions

TypeScript

Remote

rootvine-mcp

A neutral commerce resolution layer for AI agents. Connects Claude, ChatGPT, and other AI agents to trusted product and media data via the Model Context Protocol — covering every path from streaming to collector editions.

What it does

When a user asks an AI agent "Where can I listen to Windowlicker by Aphex Twin?", RootVine resolves the query across all major streaming, purchase, and physical platforms and returns ranked results with direct links.

The same infrastructure answers the full purchase ladder: stream it, buy it digitally, or find the vinyl. Music is live today. Games, books, films, podcasts, and live events are rolling out as their verticals ship.

No ads. No sponsored placements. No pay-to-rank. Results are ranked by a neutral, deterministic algorithm: trust tier → price → availability → freshness → merchant ID. Commission rates, affiliate networks, and sponsored flags are architecturally excluded from the ranking function.

Related MCP server: sonovault-mcp

Quick Start

Claude Desktop

Add to your Claude Desktop config (~/.claude/claude_desktop_config.json):

{
  "mcpServers": {
    "rootvine": {
      "command": "npx",
      "args": ["-y", "rootvine-mcp"]
    }
  }
}

Restart Claude Desktop. You can now ask:

"Where can I stream Galway Girl by Ed Sheeran?"
"Where can I listen to Windowlicker by Aphex Twin?"
"Find links for the new Kendrick Lamar album"

Other MCP Clients

Any MCP-compatible client can use rootvine-mcp via stdio transport:

npx rootvine-mcp

Tools

`discover_music`

Browse curated music collections — charts, genre walls, moods, editorial playlists, artist spotlights, and historic charts back to 1946.

Input: { chamber?: "by-genre" | "for-this-moment" | "charts" | "by-era" | "spotlights", wall?: string, year?: number, limit?: number }

Modes (picked by which arg is set):

Foyer (no args) — overview of all chambers and featured walls
Chamber (chamber arg) — list walls within a chamber (e.g. all genre corridors)
Wall (wall arg) — drill into a specific wall's tracks, albums, or artists
Archive (year arg) — frozen chart snapshots from any year since 1946

Returns: Curated collections with honest attribution (e.g. "Curated by Deezer's editorial team", "Based on Last.fm scrobbles"). Each entry links to a BeatsVine page whose streaming and purchase links can be retrieved via resolve_music.

Answering "what was number one when I was born":

discover_music { year: 1994 }          → bv-year-end-hot-100-1994 (100 entries)
discover_music { wall: "bv-year-end-hot-100-1994" }  → position 1 = Ace of Base, "The Sign"

Archives cover Billboard Hot 100, Global Top 100 and UK Singles year-end charts, plus weekly snapshots.

`resolve_artist`

Get an artist's profile and full discography.

Input: { slug: "stromae" } — the artist/stromae form is also accepted

Returns: Genres, artist metadata, and every release BeatsVine holds, each with a slug ready for resolve_music:

resolve_artist { slug: "stromae" }
  → 19 releases, e.g. album/stromae-racine-carre

resolve_music { slug: "album/stromae-racine-carre" }
  → stream, purchase and physical-media links

Physical formats — vinyl, CD, Discogs listings — are album-level products, so this is the route to collector editions.

Two response fields worth handling:

discography_source: "not_yet_indexed" means BeatsVine hasn't catalogued this artist yet. An empty list then means unknown, not no releases — the formatter says so explicitly rather than implying an empty discography.
sparse_fallback_applied means singles were included because the album list was thin. That's BeatsVine's presentation choice, surfaced so it isn't mistaken for the artist's own framing.

`resolve_music`

Find where to stream, buy, or collect a song or album.

Input: { slug: "ed-sheeran-galway-girl" }

Returns: Ranked results covering:

Streaming — Spotify, Apple Music, Tidal, YouTube Music, Deezer
Digital purchase — iTunes Store, Amazon Music, Bandcamp
Physical media — vinyl, CD (via Amazon), Discogs collector listings

Every result includes prices (where available), direct links, and affiliate-tagged click-through URLs for tracking.

`resolve_game` (coming soon)

Game price resolution across Steam, PlayStation, Xbox, Nintendo, Epic, GOG, Humble, and Fanatical. This tool is registered but not yet active — it will return a "coming soon" response until the games vertical launches.

`find_product`

Smart router — automatically detects category and routes to the correct resolver.

Input: { query: "Aphex Twin Windowlicker", category: "auto" }

Returns: Music results today (streaming, digital purchase, vinyl, CD, collector editions). Games, books, films, podcasts, and live event tickets will route automatically as each vertical launches.

Response Format

All results follow the RootVine v1 specification:

{
  "rootvine": {
    "version": "1.0",
    "resolver": "beatsvine",
    "category": "music"
  },
  "status": "success",
  "query": {
    "type": "music",
    "artist": "Aphex Twin",
    "title": "Windowlicker"
  },
  "results": [
    {
      "rank": 1,
      "merchant": "Spotify",
      "trust_tier": "authoritative",
      "price": null,
      "url": "https://open.spotify.com/track/...",
      "click_url": "https://beatsvine.com/r/abc123",
      "type": "stream",
      "ranking_reason": {
        "code": "FREE_STREAM_T1",
        "summary": "Free stream from authoritative source"
      }
    }
  ]
}

Roadmap

✅ Music resolution — live (stream, digital purchase, vinyl, CD, collector editions across Spotify, Apple Music, iTunes, Amazon, Bandcamp, Discogs, YouTube Music, Tidal, Deezer, and more)
✅ Music discovery — live (browse charts, genre walls, mood collections, editorial playlists, artist spotlights)
✅ Chart archives — live (frozen year-end and weekly chart snapshots back to 1946 — Billboard Hot 100, Global Top 100, UK Singles)
✅ Artist discography — live (artist profiles and full release lists, each resolvable to stream/buy/collect links)
🔜 Live events — concert, gig, and festival tickets
🔜 Games — digital keys, physical copies, and collector editions (Steam, PlayStation, Xbox, Nintendo, Epic, GOG)
🔜 Books — ebook, audiobook, paperback, hardback, and special editions (Amazon, Bookshop.org, Apple Books, Kobo, Audible)
🔜 Films & TV — streaming, rental, digital purchase, DVD, Blu-ray, and 4K steelbook
🔜 Podcasts — listen links across Apple Podcasts, Spotify, Pocket Casts, and more

Neutrality

RootVine follows a strict neutrality policy:

Rankings are determined by trust tier → price → availability → freshness → merchant ID
Commission rates, affiliate networks, and sponsored flags are architecturally excluded from the ranking function
The ranking logic runs server-side — this package is a thin client

License

MIT — © Raging Orangutan Holdings

Available Tools

5 tools

discover_musicA

Browse curated music collections — charts, genre walls, moods, editorial playlists, artist spotlights, and historic charts back to 1946. Use when a user wants to EXPLORE music rather than look up a specific song or album. Examples: 'what's trending this week', 'find electronic music charts', 'show me focus playlists', 'what was number one in 1994', 'what was in the charts the year I was born'. Returns walls (collections) with their slugs, which can then be passed back as the wall argument to expand into individual tracks, albums or artists. Each entry includes a BeatsVine page URL whose streaming and purchase links can be fetched via resolve_music. Ranked by editorial pinning and refresh freshness, never by commission.

ParametersJSON Schema

Name	Required	Description
`wall`	No	Wall slug to drill into. If set, returns the wall's track/album/artist entries. Takes priority over `chamber`. Example: 'lastfm-top-electronic-tracks', 'deezer-90s-hits'. Slugs are returned in the foyer and chamber responses.
`year`	No	Browse archived chart snapshots from this year. Use for questions about the past — 'what was number one in 1994', 'what was in the charts when I was born'. Archives run from 1946 to the present. Returns snapshot slugs; pass one back as `wall` to get the ranked entries, where position 1 is the number one. Takes priority over `chamber`.
`limit`	No	Max items to return. Default 10, max 30. Applies to walls (foyer/chamber mode), entries (wall mode) or snapshots (year mode).
`chamber`	No	Chamber to browse. Omit for a top-level overview of all chambers and featured walls. 'by-genre' = genre corridors (house, hip-hop, jazz, etc.). 'for-this-moment' = mood and activity walls (chill, focus, workout). 'charts' = live streaming charts. 'by-era' = decades and golden eras. 'spotlights' = editor-led artist features.

TDQS

A4.9/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full disclosure burden and does so well: it says the tool returns walls with slugs, that entries can be expanded, that streaming/purchase links require resolve_music, that year mode returns snapshots, and that results are ranked by editorial pinning and refresh freshness, not commission. These behavioral details go beyond any structured field.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is about six purposeful sentences with the core action and scope front-loaded, then examples, return semantics, and a ranking note. No filler; each sentence adds operational or behavioral information an agent needs.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a browse/discovery tool with four optional parameters and no output schema, the description covers how results are shaped (walls, entries, snapshots), how to drill in, how to resolve external links via a sibling, and ranking intent. There is no missing operational context an agent needs to invoke it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds value by explaining the wall-slug flow, that snapshot slugs should be passed back as wall, and that position 1 is the number one. It also frames year as the past-archive mode and chamber as the browse mode in user terms, supplementing but not repeating the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific action ('Browse curated music collections') with concrete resource types (charts, genre walls, moods, editorial playlists, artist spotlights, historic charts). It explicitly distinguishes exploration from looking up a specific song or album and names the sibling 'resolve_music' for fetching links, so an agent can separate it from siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit use-case rule ('Use when a user wants to EXPLORE music rather than look up a specific song or album'), illustrative example queries, and a follow-up path (pass returned wall slugs back as the wall argument; use resolve_music for page links). This is clear when-to-use and alternative guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

find_productA

Smart router — finds the best place to stream, buy, or collect any supported product. Automatically detects the product category and routes to the right resolver. Music is live (stream, digital purchase, vinyl, CD, collector editions). Games, books, films, podcasts, and live event tickets are rolling out. Use this when the query is ambiguous or when music could be streamed, purchased digitally, or found on physical media.

ParametersJSON Schema

Name	Required	Description	Default
`query`	Yes	A natural language product query. Examples: 'Aphex Twin Windowlicker', 'Elden Ring DLC', 'where can I stream Bad Guy by Billie Eilish'
`category`	No	Product category. Use 'auto' (default) to let RootVine detect the category automatically.

TDQS

A4.6/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description must fully disclose behavior. It explains auto-detection of product category, routing to resolvers, and states which categories are live and which are rolling out. It lacks explicit details on authentication or rate limits, but for a non-destructive routing tool, this is reasonably transparent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise and well-structured, starting with the core purpose ('Smart router'), then detailing supported categories and usage guidance. Every sentence adds value without redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (routing, multiple categories) and lack of output schema, the description adequately explains behavior, status, and when to use. It could mention fallback behavior for unsupported categories, but overall it is complete enough for an agent to use correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 100% coverage with descriptions for both parameters. The description adds context by explaining the 'query' parameter with natural language examples and the 'category' enum with the 'auto' default. This exceeds the baseline of 3 by providing meaningful usage context.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description explicitly states it is a 'Smart router' that finds the best place to stream, buy, or collect products. It specifies the product categories (music, games, etc.) and clearly distinguishes from sibling tools like discover_music, resolve_game, and resolve_music.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit guidance: 'Use this when the query is ambiguous or when music could be streamed, purchased digitally, or found on physical media.' It also explains the category parameter's auto-detect behavior, helping the agent decide when to use this tool over alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

resolve_artistA

Get an artist's profile and full discography. Use when a user asks what else an artist has made, wants their albums, or is exploring a body of work rather than one song — 'what albums has Stromae released', 'show me Radiohead's discography', 'what else has this artist done'. Returns the artist's genres and every release BeatsVine holds, each with a slug that resolve_music turns into stream, purchase and physical-media links. Note that physical formats — vinyl, CD, Discogs listings — live at the ALBUM level, so this is the route to collector editions.

ParametersJSON Schema

Name	Required	Description	Default
`slug`	Yes	The BeatsVine artist slug, lowercase and hyphenated: 'stromae', 'radiohead', 'ed-sheeran'. Slugs keep letters of any script, so non-Latin names are valid. An 'artist/name' form is also accepted, since that is what BeatsVine's search returns for artist hits.

TDQS

A4.5/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full transparency burden. It clearly frames the operation as a read ('Get') and describes what the response contains: genres, every release, and slugs. It also adds a useful behavioral nuance: physical formats live at the album level, so this is the route to collector editions. It doesn't cover every possible edge case, but it discloses the key behavioral traits an agent needs.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is compact yet rich: three sentences, no filler, and the core purpose is front-loaded. Every sentence earns its place—purpose, usage examples, return-value summary, and the album-level physical format nuance all contribute unique value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter tool with no output schema, the description is remarkably complete: it states what the tool returns, how the output relates to resolve_music, and why physical-format seekers should use this route. An agent has enough context to select and invoke the tool correctly without opening sibling schemas.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already fully documents the slug parameter, including accepted forms. The description mentions slugs but adds no new parameter semantics beyond what the schema provides. This meets the baseline of 3 but does not exceed it.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource: 'Get an artist's profile and full discography.' It also clearly separates this from song-level tools by saying it covers a 'body of work rather than one song,' making the tool's role obvious even before considering siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives explicit when-to-use guidance with concrete examples: 'what albums has Stromae released', 'show me Radiohead's discography'. It names resolve_music as the alternative for turning slugs into links and implies song-level requests should go elsewhere, giving both positive and negative use cases.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

resolve_gameA

Find where to buy a video game at the best price across trusted stores (Steam, PlayStation, Xbox, Nintendo, Epic, GOG, Humble, Fanatical). Returns ranked results with prices, editions, and DLC info. Note: the games vertical is launching soon — this tool currently returns a 'coming soon' message. Prefer resolve_music or find_product for music queries.

ParametersJSON Schema

Name	Required	Description	Default
`slug`	Yes	The game slug. Format: game-title (lowercase, hyphenated). Example: 'elden-ring'

TDQS

A4.4/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of disclosure. It transparently notes the tool is currently non-functional, returning a 'coming soon' message, which is a key behavioral trait. However, it does not explicitly mention read-only nature or other side effects.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise and well-structured: a single sentence for purpose, a second for details, and a crucial note about current status. Every sentence adds value without repetition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema, the description explains the return format (ranked results with prices, editions, DLC info) and the current limitation. It covers the stores list. It is mostly complete but lacks mention of error handling or data freshness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema coverage is 100% for the single required parameter. The description adds no additional meaning beyond the schema, repeating the slug format and example from the schema. Thus, the baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: finding where to buy a video game at the best price across specific trusted stores. It distinguishes itself from siblings by targeting games versus music.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description not only explains when to use the tool (for game purchases) but also advises when not to use it (for music queries) and provides alternatives (`resolve_music` or `find_product`), fulfilling the guidelines dimension well.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

resolve_musicA

Find where to stream, buy, or collect a song or album. Returns ranked results covering streaming (Spotify, Apple Music, Tidal, YouTube Music), digital purchase (iTunes, Amazon MP3, Bandcamp), and physical media (vinyl, CD via Amazon, Discogs). Use when a user asks about music — whether they want to listen, own digitally, or find a collector edition. Ranked by trust × price × availability, never by commission.

ParametersJSON Schema

Name	Required	Description	Default
`slug`	Yes	The BeatsVine page slug for the track or album. Format: artist-name-song-title, lowercase and hyphenated. Slugs keep letters of any script, so non-Latin titles are valid: 'ed-sheeran-galway-girl', 'ヨルシカ-火星人'. Latin accents are folded to their base letter ('Rosalía Despechá' → 'rosalia-despecha'), and punctuation is dropped. Pass the slug undecoded — do not percent-encode it yourself.

TDQS

A4.3/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure. It states that the tool 'returns ranked results' and explains the ranking criteria: 'trust × price × availability, never by commission.' It does not cover errors, rate limits, or authentication, but for a read-only lookup tool the disclosed ranking behavior is substantive.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is three sentences with no filler: purpose, result coverage, usage trigger, and ranking behavior are all stated efficiently. It is front-loaded with the core action and each subsequent sentence adds distinct value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has one required parameter, and the schema thoroughly documents its format and edge cases. The description covers scope, ranking behavior, and when to use it, with no output schema requiring explanation of return values. Nothing essential for correct invocation is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already fully documents the single 'slug' parameter, including format, non-Latin scripts, accent folding, and percent-encoding guidance. The description adds no parameter-specific detail, so it stays at the baseline for a fully documented schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource: 'Find where to stream, buy, or collect a song or album.' It clearly distinguishes this tool from siblings like resolve_artist, resolve_game, find_product, and discover_music by defining the music-lookup scope and the categories of results (streaming, purchase, physical media).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides an explicit trigger: 'Use when a user asks about music — whether they want to listen, own digitally, or find a collector edition.' It does not explicitly name sibling alternatives or state when not to use the tool, but the usage context is clear enough for an agent to select it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

3 tool updatesv1.3.1Aug 31, 2026

Changeddiscover_music2 fields changed

changedInput schema / properties / limit / description

Previous value: -"Max items to return. Default 10, max 30. Applies to walls (foyer/chamber mode) or entries (wall mode)."New value: +"Max items to return. Default 10, max 30. Applies to walls (foyer/chamber mode), entries (wall mode) or snapshots (year mode)."

addedInput schema / properties / year

Added value: +{
+  "description": "Browse archived chart snapshots from this year. Use for questions about the past — 'what was number one in 1994', 'what was in the charts when I was born'. Archives run from 1946 to the present. Returns snapshot slugs; pass one back as `wall` to get the ranked entries, where position 1 is the number one. Takes priority over `chamber`.",
+  "maximum": 2100,
+  "minimum": 1946,
+  "type": "integer"
+}

Addedresolve_artist

Changedresolve_music1 field changed

changedInput schema / properties / slug / description

Previous value: -"The BeatsVine page slug for the track or album. Format: artist-name-song-title (lowercase, hyphenated). Example: 'ed-sheeran-galway-girl'"New value: +"The BeatsVine page slug for the track or album. Format: artist-name-song-title, lowercase and hyphenated. Slugs keep letters of any script, so non-Latin titles are valid: 'ed-sheeran-galway-girl', 'ヨルシカ-火星人'. Latin accents are folded to their base letter ('Rosalía Despechá' → 'rosalia-despecha'), and punctuation is dropped. Pass the slug undecoded — do not percent-encode it yourself."

4 tool updatesMay 12, 2026
- Addeddiscover_music
- Changedfind_product1 field changed
  - removedInput schema / additionalProperties
```
Removed value: -false
```
- Changedresolve_game1 field changed
  - removedInput schema / additionalProperties
```
Removed value: -false
```
- Changedresolve_music1 field changed
  - removedInput schema / additionalProperties
```
Removed value: -false
```
3 tool updatesv1.0.1Feb 23, 2026
- First observedfind_product
- First observedresolve_game
- First observedresolve_music

Install Server

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

A4.3/5.0

Disambiguation4/5

The three music tools (resolve_music, resolve_artist, discover_music) are clearly separated by task: specific track/album links vs artist discography vs curated exploration. find_product overlaps somewhat with resolve_music for ambiguous music queries, but its routing purpose is distinct. resolve_game is distinct but currently a placeholder, which slightly muddies selection.

Naming Consistency5/5

All tools use a consistent lowercase snake_case verb_noun pattern (resolve_music, resolve_game, find_product, resolve_artist, discover_music). The verbs vary (resolve/find/discover) but map intuitively to their actions and never mix conventions.

Tool Count4/5

Five tools is a reasonable, manageable set for a music-discovery and link-resolution server. However, resolve_game does not yet earn its place because it only returns a coming-soon message, leaving effectively four live tools.

Completeness3/5

The music surface is fairly well covered: specific tracks/albums, artist discography, and curated discovery all have dedicated tools. The advertised product router (find_product) is incomplete and resolve_game is non-functional, so the broader multi-category promise is not yet fulfilled. There is also no obvious general search tool, though discover_music may partially cover exploration.

Maintenance

ActivityMaintained

ResponsivenessNo issues

Resources

Need Help?

Reddit Discussion

Related Servers

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Dynamoi A
io.github.getDynamoi
Create music promotion campaigns, Smart Links, analytics, and music distribution applications.
Marketing Entertainment & Media Social Media
1723
Youfiliate Smart Links A
io.github.andrewmpierce
Create geo-targeted affiliate smart links, pull analytics, and rewrite YouTube descriptions.
Marketing Social Media
182
Achriom AOAuth
com.achriom.mcp
The media memory layer for AI agents and their humans. Your AI client gets 29 tools to search your collection, add items, update ratings, preview music, and find patterns across everything you've read, watched, and listened to.
Knowledge & Memory Entertainment & Media Search
2
unulu A
ai.unulu
AI agent website builder. Create and publish link-in-bio sites via MCP or REST API.
App Automation Marketing Web Scraping
422

Related MCP Servers

rights-mcp
Entertainment & Media Payments & Billing Search
yksanjo
A
license
A
quality
D
maintenance
Enables AI agents to search, license, and pay for rights-clean music per use, returning a verifiable license certificate.
Updated 3 months ago (2026-06-13 23:59 UTC)
5
MIT
sonovault-mcpofficial
Entertainment & Media Search
rekordcloud
A
license
A
quality
A
maintenance
Provides access to the SonoVault music metadata API, enabling search and retrieval of information about 90M+ tracks, artists, labels, and releases, including ISRC, ISWC, and cross-platform IDs.
Updated 2 days ago (2026-09-04 09:53 UTC)
15
52
MIT
Dynamoi MCPofficial
Marketing Entertainment & Media Social Media
getDynamoi
A
license
Not graded
quality
B
maintenance
Lets AI agents help artists and labels prepare releases for promotion by creating Smart Links, checking campaign readiness, and managing platform connections.
Updated 6 days ago (2026-08-31 03:06 UTC)
408
3
MIT
music-mcp-agent
thelma-tertrais
F
license
Not graded
quality
C
maintenance
Enables music search, metadata retrieval, local audio analysis (tempo, key, energy), recommendations, song recognition, and classical work resolution via Spotify, Last.fm, AudD, MusicBrainz, and Songkick APIs.
Updated 2 months ago (2026-07-17 23:27 UTC)
-

Latest Blog Posts

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/RagingOrangutan/rootvine-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server

rootvine-mcp

What it does

Quick Start

Claude Desktop

Other MCP Clients

Tools

discover_music

resolve_artist

resolve_music

resolve_game (coming soon)

find_product

Response Format

Roadmap

Neutrality

License

Available Tools

Tool Schema Changelog

Maintenance

Resources

Looking for Admin?

Related MCP Connectors

Related MCP Servers

sonovault-mcpofficial

Dynamoi MCPofficial

Latest Blog Posts

MCP directory API

`discover_music`

`resolve_artist`

`resolve_music`

`resolve_game` (coming soon)

`find_product`