Fyyd

What the Fyyd MCP server does

The Fyyd MCP server exposes Fyyd’s public podcast data to MCP-compatible clients. Fyyd indexes approximately 3 million podcasts worldwide, making the server suitable for podcast discovery, metadata lookup, and episode searches.

Searches can target podcast titles or episode titles and descriptions. Other operations retrieve a show from its Fyyd identifier, resolve a podcast’s RSS feed URL to a Fyyd identifier, return episodes in chronological order, identify currently popular podcasts, and expose Fyyd’s category tree.

The underlying data source is Fyyd’s public REST API at https://api.fyyd.de/0.2/.

Tools and capabilities

The pack provides these tools:

• search_podcasts(term, lang?, count?, page?) searches shows by title.
• search_episodes(term, lang?, count?, page?) searches episode titles and descriptions.
• get_podcast(podcast_id) returns show metadata and recent episodes.
• get_podcast_by_url(feed_url) maps an RSS feed URL to a Fyyd ID.
• latest_episodes(podcast_id, count?, page?) returns a chronological episode list.
• top_podcasts(category?, lang?, count?) retrieves currently popular shows, optionally filtered by category or language.
• categories() returns Fyyd’s category hierarchy.

These tools cover both discovery and follow-up lookups. For example, an agent can find a show by title, resolve its identifier, then request metadata or episode listings.

Setup and configuration

A local installation uses the npm package and communicates through standard input and output:

{
  "mcpServers": {
    "fyyd": {
      "command": "npx",
      "args": ["-y", "@pipeworx/mcp-fyyd"]
    }
  }
}

Running npx -y @pipeworx/mcp-fyyd directly can verify that the process starts. The local process answers MCP initialize, tools/list, and tools/call requests and exposes only the Fyyd pack’s tools.

The Fyyd MCP server is also available through the Pipeworx gateway at https://gateway.pipeworx.io/fyyd/mcp. A full gateway connection uses https://gateway.pipeworx.io/mcp. The gateway endpoint can also be called without an MCP client through HTTP; for example, POST https://gateway.pipeworx.io/v1/tools/fyyd_search_podcasts accepts a JSON body containing a search term.

Limitations and notes

The gateway pack endpoint lists the Fyyd tools together with shared Pipeworx meta-tools. Its exact tool scope can change, so the initialize response is authoritative. Shared tools include routing and discovery functions such as ask_pipeworx, which can reach other Pipeworx sources. The standalone package does not include those gateway meta-tools or cross-catalog routing.

Both gateway URLs use the same Pipeworx infrastructure and data-source catalog; they differ in which pack tools are listed directly. No environment variables are documented for the local package.