Connect Cursor

Cursor can work with poddub while you work in a project. Cursor connects to poddub with a key: it does not sign in to poddub the way Claude Code and claude.ai do. Only an owner makes keys, and a key is its owner's own, so the agent acts as that owner. Keys says what a key is and who makes it. Where poddub works lists every client and how it connects.

Add the serverCopy Anchor Link

Put the server in .cursor/mcp.json in your project, or in ~/.cursor/mcp.json in your home folder to have it in every project:

{
  "mcpServers": {
    "poddub": {
      "url": "https://poddub.com/api/mcp",
      "headers": {
        "Authorization": "Bearer ${env:PODDUB_API_KEY}"
      }
    }
  }
}

Set PODDUB_API_KEY to your key in your shell profile or your system's environment before you open Cursor. Cursor fills in ${env:PODDUB_API_KEY} itself, so the key stays out of the file and the file can be shared with a project.

Cursor asks before it uses a tool, unless you allow it to run tools on its own.

Long callsCopy Anchor Link

Having poddub write a script or a line again happens inside one call and can take a couple of minutes. How long Cursor waits for one call has not been checked. If such a call gives up, the script is unchanged unless poddub finished: read it again with get_script before trying again.

What it can doCopy Anchor Link

The same as any agent: read, paste and correct sources, start an episode and shape its script, retry and publish within your key's role, and never do more than its person can, approve on its own, manage people, touch money, delete anything or put an episode on the public show. See Agents and Tools.