pods4.me

Agent guide

Manage pods4.me from a conversation

Connect once, then ask your AI to find podcasts, tune your preferences, maintain the queue, or give you a safe subscription handoff.

What the connection can do

  • Search, add, remove, and configure podcast sources.
  • Read and update your episode preferences, weekly limit, and feed name.
  • find_podcast_episodes finds dated choices; recommend_episodes returns alternatives with stable episode IDs.
  • get_episode_transcript accepts a search-result hex ID or canonical key, or a queue UUID, and reads transcripts in bounded chunks with continuation offsets. Queue removal accepts the same IDs.
  • Create a single-use subscription page valid for 45 minutes where you can retrieve your private feed URL yourself.

Help a new listener sign up

  1. Confirm the email address, then ask exactly: “May I use this email and open the link?”
  2. Only after the listener says yes, open the pods4.me signup page, enter that email, and request the magic link.
  3. Open the magic link and finish signup. The private feed is created automatically.
  4. Do not ask for preferences, a feed name, or a weekly limit during signup. Those settings are optional and can be changed later.

Security

The MCP endpoint is https://pods4.me/mcp. Connect with OAuth 2.1 with PKCE: the connection gets its own named agent credential and cannot replace or revoke a credential another agent uses. A personal Bearer token remains a fallback only for clients without OAuth and belongs in protected client settings, never in chat. Every request is tied to the signed-in user, checked for the pods4.me audience, and rate limited.

Claude app

Use a personal Claude account: work or Team accounts may block custom connectors. This is custom-connector setup, not a public directory listing.

Start in Claude

  1. Open Customize → Connectors → Add custom connector.
  2. Name it pods4me, enter https://pods4.me/mcp, and leave the OAuth fields blank.
  3. Connect, then sign in or create an account with pods4.me. Open the email magic link in the same browser.
  4. Approve the connection, then ask Claude: “Show my podcast sources and queue.”

Start on the web

  1. Sign up or sign in at pods4.me. Open the email magic link in the same browser.
  2. Return to Claude and add the custom connector using the name and URL above.
  3. Approve the connection, then ask Claude: “Show my podcast sources and queue.”

Claude handles OAuth; do not create, copy, or paste a token into chat.

OpenAI Dot and R2

Dot on mobile and desktop uses the same OAuth connect path: eligible Connect or Allow, hosted pods4.me sign-in and consent, then return to the same conversation. This is not a public app-directory listing.

Connect in Dot

  1. Open pods4.me from Dot's tools or apps and choose Connect when you are eligible.
  2. Sign in to pods4.me and approve access on the hosted consent screen.
  3. Return to the same conversation and ask: “Show my podcast sources and queue.”

Start on the web

  1. Sign up or sign in at pods4.me. Open the email magic link in the same browser.
  2. Return to Dot and connect pods4.me from tools or apps.
  3. Approve the connection, then ask: “Show my podcast sources and queue.”

Dot completes OAuth in chat; do not create, copy, or paste a token into chat. A personal Bearer token is only a clearly labelled fallback for Dot's protected credential field when OAuth is unavailable — name it separately (for example, Dot/R2) so other agents keep their own connections.

ChatGPT

Today pods4.me is a private cloud plugin, not a public ChatGPT directory listing. Access is limited to plugin creators and eligible testers; ordinary users who already have the plugin connect from chat and never enter MCP endpoints, manifests, or client configuration.

Plugin owner setup (one time)

  1. In ChatGPT on the web, open Plugins → Add → Add custom MCP server.
  2. Enter https://pods4.me/mcp, choose Streamable HTTP and OAuth, then create the plugin.
  3. Manage the connection under ChatGPT plugin settings for your private cloud plugin.

Do not treat the older desktop-only manifest-package plugin as the cloud path.

Ordinary user path

  1. When ChatGPT offers Connect or Allow for pods4.me, accept it.
  2. Sign in to pods4.me and approve access on the hosted consent screen.
  3. Return to the same conversation and ask: “Show my podcast sources and queue.”

ChatGPT handles OAuth for ordinary users; do not paste a token into chat. A Bearer token belongs only in a client's protected credential field when OAuth is unavailable. A fresh Connect chip on a brand-new pods4.me account was not re-verified for every workspace — sign up at pods4.me first if you need a new account.

Connect your AI client

Connect with OAuth: add https://pods4.me/mcp, sign in to pods4.me, and approve. OAuth creates or reuses a named connection for that client without replacing another agent's connection.

Grok Bot

  1. Open Grok Bot integrations and add a custom remote MCP server named pods4me.
  2. Choose Streamable HTTP and enter https://pods4.me/mcp.
  3. Choose OAuth, sign in to pods4.me, and approve the connection.

Codex

  1. Open MCP settings and add a custom MCP named pods4me.
  2. Choose Streamable HTTP, not STDIO. Set URL to https://pods4.me/mcp.
  3. Leave Bearer token env var empty. This field expects an environment-variable name, not your token.
  4. Under Headers, set Key to Authorization and Value to Bearer YOUR_TOKEN. Replace only YOUR_TOKEN, keeping the space after Bearer. Do not add quotes.
  5. Leave Headers from environment variables empty, then save. If the tools do not appear, restart Codex.
OpenAI Dot

On mobile or desktop, connect with OAuth from the same conversation:

  1. Open pods4.me from Dot's tools or apps and choose Connect when you are eligible.
  2. Sign in to pods4.me and approve access on the hosted consent screen.
  3. Return to the same conversation and ask: “Show my podcast sources and queue.”

Bearer fallback (only when OAuth is unavailable)

Add a custom remote MCP named pods4me at https://pods4.me/mcp. Put a separately named token such as Dot/R2 only in Dot's protected Bearer credential field — never in chat.

ChatGPT

Plugin owner setup (one time)

  1. In ChatGPT on the web, open Plugins → Add → Add custom MCP server.
  2. Enter https://pods4.me/mcp, choose Streamable HTTP and OAuth, then create the plugin.
  3. Manage the connection under ChatGPT plugin settings for your private cloud plugin. Do not use the older desktop-only manifest-package plugin as the cloud path.

Ordinary user path

  1. When ChatGPT offers Connect or Allow for pods4.me, accept it. End users do not enter MCP URLs, manifests, or client configuration.
  2. Sign in to pods4.me and approve access, then return to the same conversation.
  3. Ask: “Show my podcast sources and queue.”

Private cloud plugin eligibility applies; this is not a public directory listing.

Claude Code

Add pods4me with OAuth:

claude mcp add --transport http pods4me https://pods4.me/mcp

Start in Claude Code: use /mcp and authenticate. Sign in or create an account, open the email magic link in the same browser, and approve the connection.

Start on the web: sign up or sign in at pods4.me first, open the email magic link in the same browser, then run the command and authenticate through /mcp.

Bearer fallback (only when OAuth is unavailable)

Put the token only in Claude Code's protected configuration; never paste it into chat:

claude mcp add --transport http --scope user pods4me https://pods4.me/mcp --header "Authorization: Bearer YOUR_TOKEN"

For the Claude app instead, use Customize → Connectors → Add custom connector with the same URL and leave OAuth fields blank.

Cursor (Bearer fallback)
  1. Open Cursor's MCP settings and add a custom remote MCP named pods4me.
  2. Choose Streamable HTTP and set the server URL to https://pods4.me/mcp.
  3. Add a header named Authorization with the value Bearer YOUR_TOKEN. Keep the space after Bearer.
  4. Mark the header value as masked or secret when that option is available, then save and enable the connection.

If a client does not support OAuth, a personal Bearer token may be used only in that client's protected credential settings. This is a compatibility fallback, not the Grok setup path.

Create a separate, clearly named token such as Dot/R2 for a token-based OpenAI connection. Do not revoke or reuse the token for Grok, Mac, or another existing connection.

Keep your token private: these methods save it in local or client configuration, and the terminal command may also remain in shell history. Never share that configuration or paste your token into an AI chat. Revoke the token from your signed-in pods4.me settings if it is exposed.

Once connected, try: “Show my podcast sources and queue.” This checks the connection without changing your feed.

Queue and transcript response sizes

list_queue returns compact rows by default: stable ID, title, podcast, dates, and duration when known. An agent can request full rows when it needs descriptions and episode links. get_episode_transcript returns at most 12,000 Unicode characters by default and provides next_offset when more text is available. Agents should pass that value back as offset to continue.

Private RSS stays out of chat

The agent can return a temporary subscription page, but it cannot read or return your permanent private RSS credential. The agent must present that link, ask you to open it while signed in, and ask you to add the private feed to your podcast player. It must not open the subscription link or private feed URL itself. It should give extra steps only when it knows which podcast player you use.

Support and policies

Privacy: /privacy. Terms: /terms. Support: help@pods4.me.

AI agent guide | pods4.me