Megaphone MCP. Manage ad campaigns and podcast content flow.

Look, forget those clunky dashboards and half-baked API calls. This Megaphone MCP Server hooks your AI client up right to your podcast publishing and ad management workflow. You're gonna manage everything—from the network structure all the way down to specific ad spots—just by chatting with your agent.

Network Overview

When you wanna map out your whole operation, start by calling list_networks. That'll give you a clean list of every podcast network attached under your account. If you need deep metadata on just one of those networks, you use get_network_details to pull all the specifics for that single entity.

Tracking Content Inventory

Once you know which networks you're working with, you gotta find the content inside. You can list every individual podcast belonging to a network using list_podcasts. For any specific show you pick out, you run get_podcast to grab all its detailed setup info. To see what episodes are actually available for that show, use list_episodes, which enumerates everything in the library.

If you're hunting down something specific—maybe a keyword or a date range—you don't have to list 'em one by one; just hit up search_episodes and it crawls your entire catalog. Need the full data on one particular episode? You call get_episode, and that gives you all the deep details for that single piece of content.

Managing Ad Placement and Campaigns

Running ads is half the job, right? To manage ad revenue, first, check out what campaigns are active or were run by calling list_campaigns. You can then figure out exactly where an ad needs to go on a specific episode using list_ad_locations; this shows all the available spots and locations for that one piece of content.

When you need to track down existing placements, you use list_orders to retrieve records and details on every ad order placed in the network.

Putting It All Together

This setup means your agent doesn't just pull data; it lets you build a full workflow. You can tell it to list all networks, then find all podcasts within Network A, get the episode count for Show B, and immediately check which ad spots are open on Episode 145. It processes that whole chain of commands conversationally.

You're basically telling your agent: 'Check these ads, pull this data, cross-reference those episodes.' You don't have to juggle a dozen tabs; you just talk to your client and it handles the backend calls using all ten tools: list_networks, get_network_details, list_podcasts, get_podcast, list_episodes, search_episodes, get_episode, list_campaigns, list_ad_locations, list_orders. You'll get the whole picture of your publishing and ad revenue in one go.