A
licenseA
qualityF
maintenanceMCP server for the Transistor.fm API: manage podcast episodes, analytics, transcripts, and webhooks from your AI agent.
23
49 npm
1
MIT
Podcast Ingestion Core MCP Server
by norton77930
Related Servers
Alternatives to Podcast Ingestion Core MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceMCP server for the Podcast Index API — search podcasts, track appearances, monitor trending shows, check feed health1835 npm1MIT
- FlicenseNot gradedqualityCmaintenanceEnables MCP clients to call simple tools (add, echo), access a memo resource, and run a summarization prompt over stdio or streamable HTTP.-
- AlicenseAqualityDmaintenanceAn MCP server that integrates with the Podhome API to manage multiple podcast shows. It enables users to create and schedule episodes, generate clips, and manage webhooks through natural language commands.10MIT
- AlicenseNot gradedqualityBmaintenanceExposes SmartCLI's built-in agent tools (file operations, code search, shell commands, web search, memory, and snapshots) as MCP endpoints, allowing external clients to leverage them over stdio or HTTP.1MIT
- FlicenseNot gradedqualityDmaintenanceA dual-transport MCP server that exposes your API as tools to LLM clients, supporting both stdio transport for local clients like Claude Desktop and HTTP/SSE transport for remote clients like OpenAI's Responses API.-
TDQS
C2.7/5.0
Scored across 25 tools
Disambiguation2/5
The base episode/transcript/search tools are distinct, but the workflow surface is crowded: run_research_workflow and the four run_*_workflow variants, plus two query_verified_research_report_* tools, have highly similar names and only subtle distinctions. An agent would likely struggle to select the correct workflow tool without very careful reading.
Naming Consistency4/5
Tool names overwhelmingly follow a snake_case verb_noun pattern and form a recognizable family. Minor inconsistencies like summarize_episode_extractive vs semantic_summarize_episode, and some very long workflow names with awkward modifier placement, keep it from being perfectly consistent.
Tool Count3/5
25 tools sits at the high end of the heavy-but-acceptable range. The core ingestion operations are well represented, but the many workflow/report variants make the count feel bloated for a server named 'Podcast Ingestion Core'.
Completeness4/5
The tool set covers the core ingestion lifecycle well: list/get, download, transcribe, summarize, extract mentions, search, validate, cache rebuild, and extended X/YouTube ingestion and report workflows. Notable minor gaps are the lack of a direct transcript retrieval tool and no delete/update artifact operations, but agents can work around these.
Maintenance
ActivityMaintained
ResponsivenessNo issues