Add Spotify artwork to MCP resource responses - #43
Merged
Merged
Conversation
austin-smith
marked this pull request as ready for review
August 7, 2026 06:50
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
include_artworksupport to the MCPget_resourcetool for tracks and albumsWhy
Spotify resource metadata exposed album details but the MCP result discarded the image data, so clients could not directly show album art. This keeps artwork opt-in and attached to the existing resource response while preserving the text-only default.
Validation
bun test— 1,055 passedbun run typecheckbun run engine:test— 28 passedcargo fmt --manifest-path native/Cargo.toml --checkcargo clippy --manifest-path native/Cargo.toml --all-targets -- -D warningsgit diff --check