MCP Server

Podwise runs a hosted MCP (Model Context Protocol)  server, so you can use Podwise in Claude, ChatGPT, Cursor, and other MCP clients without installing anything. Search episodes, read summaries and transcripts, ask questions, create Clips, and send notes to your apps, all from a chat.

Server URL:

https://mcp.podwise.ai/mcp

The server uses the Streamable HTTP transport. Clients sign in with your Podwise account through OAuth, so you only need to paste the URL and approve access.

Connect your AI app

claude mcp add --transport http podwise https://mcp.podwise.ai/mcp

{
  "mcpServers": {
    "podwise": {
      "url": "https://mcp.podwise.ai/mcp"
    }
  }
}

{
  "servers": {
    "podwise": {
      "type": "http",
      "url": "https://mcp.podwise.ai/mcp"
    }
  }
}

codex mcp add podwise --url https://mcp.podwise.ai/mcp
codex mcp login podwise

Use an API access token

Developer tools, scripts, and agents that run without a browser can skip OAuth and send an API access token in the Authorization header. Create a token in Settings > Developer . The same token works with the Open API.

Authorization: Bearer YOUR_API_TOKEN

claude mcp add --transport http podwise https://mcp.podwise.ai/mcp \
  --header "Authorization: Bearer YOUR_API_TOKEN"

{
  "mcpServers": {
    "podwise": {
      "url": "https://mcp.podwise.ai/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_TOKEN"
      }
    }
  }
}

export PODWISE_API_TOKEN=YOUR_API_TOKEN
codex mcp add podwise --url https://mcp.podwise.ai/mcp --bearer-token-env-var PODWISE_API_TOKEN

Treat the token like a password. Anyone with it can act on your Podwise account; disable or delete it in Settings > Developer if it leaks.

Manage connected apps

Every AI app you authorize through OAuth appears in Settings > Connections > Connected Apps , with the date it was connected and when it was last active. Click Disconnect to revoke its access immediately. You can connect it again from the app at any time.

Apps connected with an API access token do not appear there; manage those tokens in Settings > Developer.

Tools

Episodes and podcasts are identified by their numeric seq, the number in Podwise URLs such as https://app.podwise.ai/dashboard/episodes/<seq>.

Discovery

Episodes

Library and Ask

Clips

Audio uploads

Notion, Readwise, and Readwise Reader must already be connected in Podwise Settings > Connections  before send_episode or send_clips can use them.

Enterprise tools

Accounts with an active Enterprise entitlement also see these tools, which wrap the Enterprise API. Usage is billed to your Enterprise organization. If your Enterprise access changes, reconnect the app to refresh its tool list.

Uploading local audio

A remote MCP server cannot read files on your computer, so audio files are uploaded outside the chat:

1. The AI app calls start_audio_upload, which returns an upload URL and a browser upload link. Both expire after one hour.
2. Agents that can run shell commands, such as Claude Code, upload the file directly. In chat apps like Claude and ChatGPT, open the browser link and choose the file yourself.
3. The AI app calls complete_audio_upload to create the episode and start AI processing.

Hosted and local MCP servers

The Podwise CLI also includes a local MCP server started with podwise mcp. Both give AI apps access to Podwise with the same plan requirements; they differ in where they run and how they sign in.