mcp-deezer
This server has a remotely hosted endpoint. Open its connector listing for connection details, authentication requirements, and setup instructions:
@pipeworx/deezer
Deezer public catalog MCP — search tracks/artists/albums + lookups (keyless, no OAuth needed for public catalog).
Part of Pipeworx — an MCP gateway connecting AI agents to 1863+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.
Tools
search(type?, query, limit?)— search tracks/albums/artists/playliststrack(id)— full track metadataalbum(id)— album metadata + tracklistartist(id)— artist infoartist_top(id, limit?)— most popular tracks for an artistchart(genre_id?)— current chart (worldwide or by genre)
Related MCP server: Deezer 1 MCP Server
Data source
https://api.deezer.com (public read-only endpoints).
Quick Start
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"deezer": {
"url": "https://gateway.pipeworx.io/deezer/mcp"
}
}
}What this endpoint actually serves
tools/list at https://gateway.pipeworx.io/deezer/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 1863+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
No MCP client? Call it over HTTP
curl -X POST https://gateway.pipeworx.io/v1/tools/deezer_search \
-H 'Content-Type: application/json' \
-d '{"query":"Daft Punk Get Lucky"}'No account needed for the first calls. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/deezer_search. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.
Run it from npm
@pipeworx/mcp-deezer is a local stdio bridge to the Pipeworx gateway: your MCP client
starts it with npx, and it forwards every call to the same
https://gateway.pipeworx.io/deezer/mcp endpoint shown above. It needs network access;
there is no offline mode.
{
"mcpServers": {
"deezer": {
"command": "npx",
"args": ["-y", "@pipeworx/mcp-deezer"]
}
}
}Without a key it calls anonymously, capped at 50 calls a day. A free account
raises that to 200 a day: get a key at https://pipeworx.io/signup and add
"env": { "PIPEWORX_API_KEY": "<your key>" } to the server entry.
The key is sent as a Bearer token, the same way a hosted connection sends it,
so calls are metered and billed exactly as they are there.
It lists only this pack's tools by default. Set PIPEWORX_META_TOOLS=1 to
also list ask_pipeworx and the other gateway-wide tools.
Behind an HTTPS proxy: Node's built-in fetch does not read HTTPS_PROXY by
default. Newer Node releases honour it when NODE_USE_ENV_PROXY=1 is set; check
your Node version's documentation.
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 Deezer data" })The gateway picks the right tool and fills the arguments automatically.
More
License
MIT
Related MCP Connectors
Find Bizzy radio stations, read station cards and public author information. Read-only; no playback.
Public, read-only: search Splice docs and list models, live prices and templates. No sign-in.
Search, analyze, and discover commercially released music using sonic intelligence.
Spotify: Spotify Data API for Millions of songs & podcasts, artists, albums, playlists and more.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables interaction with the dev.to platform through its public API. Allows users to retrieve articles, user profiles, tags, comments, and perform article searches without requiring authentication.46MIT
- AlicenseCqualityDmaintenanceEnables access to the Deezer 1 API through MCP protocol. Requires API key authentication and supports integration with Cursor and Claude Desktop for interacting with Deezer services.1MIT
- AlicenseAqualityCmaintenanceEnables querying FIFA competitions, fixtures, results, and live match data through the FIFA Public API without authentication.1228 npmMIT
- FlicenseAqualityDmaintenanceEnables searching and retrieving scholarly metadata from Crossref's public REST API, including works, journals, funders, and members, without requiring an API key.101-