PodMule

PodMule plugin

Connect your agent to your own PodMule podcast workspace — shows, episodes, transcripts, the knowledge base built from your back catalogue, clips, guest CRM and interview bookings.

The plugin bundles two things: a reference to PodMule's remote MCP server, and five skills that tell your agent when to use which part of it. Connecting without the skills gives you three tools and no idea how to drive them.

You need a PodMule workspace. This plugin talks to your data; it does nothing on its own. You sign in with your normal PodMule account the first time your agent connects — there is no API key to copy. If you don't have an account yet, start at podmule.com.

Connector URL: https://app.podmule.com/mcp · Full setup guide: app.podmule.com/mcp-setup

Install

Everywhere except Claude Code, the whole install is the repo name — Squared-Lemons-Ltd/podmule-plugin — pasted into a Plugins settings screen.

Claude Code

/plugin marketplace add Squared-Lemons-Ltd/podmule-plugin/plugin install podmule@podmule

Then /mcp and sign in. A browser window opens for PodMule's consent screen; if you belong to more than one workspace you pick which one the connection uses.

Non-interactive sessions (claude -p, the Agent SDK) cannot complete the OAuth flow and will report the tools as unavailable. Authorise once from an interactive session first.

Claude Desktop, ChatGPT and Codex

All three take the repo name directly. Open the Plugins section, choose Add custom, and enter:

Squared-Lemons-Ltd/podmule-plugin

Then install PodMule and sign in. One package, read by all of them.

The ChatGPT chat surface is a separate thing and is not reachable this way — it needs a connector ID minted by your own developer-mode registration, which no distributable package can carry.

One click, other surfaces

[Add to Cursor] [Add to VS Code] [Add to VS Code Insiders] [Add to LM Studio] [Add to Replit] [Add to Goose]

These add the MCP connection only — the skills come with the plugin package, so Claude Code and ChatGPT desktop get more out of it.

Anything else

Any MCP client that speaks Streamable HTTP with OAuth can point at the URL directly:

{  "mcpServers": {    "podmule": {      "type": "http",      "url": "https://app.podmule.com/mcp"    }  }}

"type" is not optional. Claude Code reads a url entry without it as a stdio server, skips it, and errors.

What the skills do

find-in-back-catalogue is read-only and the best first thing to try. The clip and write-up skills change your workspace, so they ask before doing so.

Repo layout

.claude-plugin/marketplace.json    the catalog, read by both Claude and ChatGPT desktopplugins/podmule/  .claude-plugin/plugin.json       Claude manifest  .codex-plugin/plugin.json        Codex/ChatGPT manifest  .mcp.json                        the connector declaration, shared by both  skills/                          five skills, shared by both  assets/                          brand mark, taken from the PodMule marketing siteserver.json                        the official MCP registry entryscripts/check-manifests.mjs        structural checks on the manifestsscripts/check-capability-drift.mjs fails when a skill names a capability that no longer exists

Both manifests point at one skills directory and one .mcp.json, so the two ecosystems can never drift apart in content — only in the presentation fields each one reads.

Checks

node scripts/check-manifests.mjsnode scripts/check-capability-drift.mjs

The drift check reads PodMule's public capability list and fails if a skill mentions something the server no longer registers. It needs no credentials, and runs in CI on every push and pull request. Renaming a capability in the product is exactly the kind of change that otherwise breaks installed guidance silently.

Licence

MIT — see LICENSE.