mcpField
T
Tastedive

Tastedive

Remote
pipeworx.ioGames & Entertainment0Updated 6w ago
RepositoryVisit website

About Tastedive

Tastedive is an MCP server for finding related music, films, shows, books, authors, games, and podcasts. It suits clients seeking cross-media recommendations and combines its pack-specific tool with Pipeworx gateway meta-tools.

Key features

  1. 01Cross-media recommendations
  2. 02Search by media type
  3. 03Optional result details
  4. 04Query and limit controls

Use cases

  1. 01Find music similar to an artist
  2. 02Explore books related to a title
  3. 03Discover shows or games from a favorite

MCP support

Exposes `get_recommendations` to MCP clients through a Pipeworx gateway endpoint. The endpoint also includes shared gateway meta-tools such as `ask_pipeworx`.

Configuration

Remote servers need no local install. Pick your client, then copy the config or install in one click.

Endpointhttps://gateway.pipeworx.io/tastedive/mcp
Copy install command
Claude CodeTerminal
Cursor.cursor/mcp.json
VS Code.vscode/mcp.json
Claude Desktopclaude_desktop_config.json
Windsurf~/.codeium/windsurf/mcp_config.json

Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.

Tools

Details

From the project 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.):

{
  "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:

{
  "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

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.