Fyyd vs Next Devtools MCP
A side-by-side look at the Fyyd and Next Devtools MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Fyyd for podcasts work as a local process; choose Next Devtools MCP for developer tools as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Fyyd when
- You need dedicated capabilities in the Podcasts domain.
- You prefer a local stdio subprocess transport.
- You want tools like
search_podcasts, search_episodes, get_podcast.
Choose Next Devtools MCP when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
nextjs_index, nextjs_call, nextjs_docs.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Podcasts | Developer Tools |
| Quality signal | 56/100 · Good | 86/100 · Excellent |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Verified |
| GitHub stars | 0 | 832 |
| Directory activity | 1 views 0 installs 0 upvotes | 9 views 0 installs 1 upvotes |
| Tools | 7 | 4 |
| Full listing | View Fyyd | View Next Devtools MCP |
Tools & capabilities
Fyyd tools 7
search_podcastsfyyd, the open podcast directory — search podcast shows by title term, optionally restricted to a language code, up to 30 per page. Returns each show's fyyd podcast id, title, author, description, RSS feed URL, artwork and episode count. Answers which podcast shows exist under a name and where the RSS feed is.search_episodesfyyd, the open podcast directory — search individual podcast episodes, matching the term against episode titles and show-note descriptions, optionally filtered by language. Returns each episode's fyyd id, title, description, publication date, duration, audio enclosure URL and its parent podcast id. Answers which podcast episode covered a subject and where to listen to it.get_podcastPodcast metadata + recent episodes.get_podcast_by_urlResolve an RSS feed URL to its fyyd id.latest_episodesLatest episodes for a podcast.top_podcastsReturn the most popular podcasts on fyyd, optionally filtered by category slug and language code, with up to 30 results per call.categoriesCategory tree.
Next Devtools MCP tools 4
nextjs_indexDiscover running Next.js dev servers and list each one's runtime MCP tools.nextjs_callCall a runtime tool on a discovered server (errors, routes, logs, Server Actions).nextjs_docsGateway.** Point the agent at version-accurate docs in `node_modules/next/dist/docs/`.browser_evalGateway.** Point the agent at the [`agent-browser`](https://github.com/vercel-labs/agent-browser) CLI for browser automation.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Fyyd
{
"mcpServers": {
"fyyd": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-fyyd"
]
}
}
}
Next Devtools MCP
{
"mcpServers": {
"vercel-next-devtools-mcp": {
"command": "npx",
"args": [
"-y",
"next-devtools-mcp@latest"
]
}
}
}
Frequently asked questions
Fyyd is categorized under Podcasts and uses a local stdio subprocess. Next Devtools MCP belongs to Developer Tools and uses a local stdio subprocess. Pick Fyyd for podcasts work and Next Devtools MCP for developer tools.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Fyyd has no declared pricing — check the project's own site. Next Devtools MCP is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add fyyd and vercel-next-devtools-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Fyyd has a quality signal of 56/100 (Good) with 1 views, 0 installs and 0 GitHub stars. Next Devtools MCP has 86/100 (Excellent) with 9 views, 0 installs and 832 GitHub stars.