Tastedive

io.github.pipeworx-ioPublished by GitHub account pipeworx-iov0.1.1Updated Oct 24, 2026

TasteDive MCP — cross-media recommendations (free with key)

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingMedia & Design

Overview

AI-generated overview

A remote Pipeworx gateway endpoint that gives an assistant TasteDive cross-media recommendations for music, movies, shows, books, authors, games and podcasts.

What you can do
Get recommendations for music, movies, shows, books, authors, games and podcasts based on a title or name, with optional type, result limit and extra info settings. Ask questions in plain English through the gateway's ask_pipeworx meta-tool, which routes to the right tool. Use shared gateway meta-tools such as tool discovery, search and remember/recall alongside the recommendation tool.
When to use it
Useful when you want an assistant to suggest similar artists, films, series, books, games or podcasts from a starting title, and you are willing to connect through the Pipeworx gateway rather than a dedicated TasteDive integration.
Requirements
A remote MCP connection to the Pipeworx gateway endpoint; no local package or runtime. A TasteDive API key is needed, either supplied by the gateway platform key or passed as a query parameter after registering on TasteDive. Network access to the gateway.
Before you install
The endpoint lists roughly 30 shared gateway meta-tools in addition to the recommendation tool, which consumes context; the README says pack endpoints cannot be mounted without them. A personal TasteDive API key passed in the URL query string may be exposed in logs or client configuration. Requests and questions are routed through the third-party Pipeworx gateway.

Installation

In SourceWeft

  1. Open Tastedive in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.pipeworx-io%2Ftastedive/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "tastedive": {
      "type": "http",
      "url": "https://gateway.pipeworx.io/tastedive/mcp"
    }
  }
}

README

@pipeworx/tastedive

TasteDive MCP — cross-media "like X" recommendations.

Part of Pipeworx — an MCP gateway connecting AI agents to 1476+ live data sources.

Tools

  • get_recommendations(query, type?, limit?, include_info?) — music / movies / shows / books / authors / games / podcasts.

Auth

Data source

https://tastedive.com/api/similar — ?k= query param.

Quick Start

Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):

json
{  "mcpServers": {    "tastedive": {      "url": "https://gateway.pipeworx.io/tastedive/mcp"    }  }}

What this endpoint actually serves

tools/list at https://gateway.pipeworx.io/tastedive/mcp returns the tools in the table above plus the shared Pipeworx meta-tools — ask_pipeworx, discover_tools, search_within, remember/recall and the rest of the gateway-wide set. So the tool count you see is larger than this table: a single-pack endpoint currently lists roughly 30 shared tools alongside the pack's own. The connection's initialize response states its exact scope, and is the authoritative answer for a given day.

This is deliberate, not multiplexing by accident. The meta-tools are what let a scoped connection answer a question this pack does not cover — via ask_pipeworx, which routes across the whole catalog — without you adding a second MCP server. There is currently no way to mount a pack endpoint without them; if the extra schemas cost you more context than the routing is worth, connect to the full gateway once rather than to several pack endpoints.

Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:

json
{  "mcpServers": {    "pipeworx": {      "url": "https://gateway.pipeworx.io/mcp"    }  }}

Both URLs reach the same gateway and the same 1476+ data sources. The only difference is which pack's tools are listed directly; ask_pipeworx reaches all of them from either one.

Using with ask_pipeworx

Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:

ask_pipeworx({ question: "your question about Tastedive data" })

The gateway picks the right tool and fills the arguments automatically.

More

License

MIT

Source: README.md at commit 7c0d6e9

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v0.1.1LatestSep 16, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts