> For the complete documentation index, see [llms.txt](https://docs.podigee.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.podigee.com/documentation/start-here/ai-agents/connect-and-authorize/connect-podigee-to-codex.md).

# Connect Podigee to Codex

Connect Codex to the Podigee MCP server with browser sign-in or a personal access token.

Connect the Codex command-line interface (CLI) to the Podigee Model Context Protocol (MCP) server. Codex runs on your computer. It starts the Podigee authorization in your browser and receives the result on a local address.

## Before you start

* Have an active Podigee account with AI agents access enabled.
* Install Codex 0.154.0 or later for browser sign-in. An earlier version stops with the message `Dynamic client registration not supported`, because it cannot use the sign-in method that Podigee supports. Version 0.133.0 fails this way. Any version can use the token method below.
* Use a computer that can open a browser. Use the token method below for a server without a browser.
* Install the `pdg` CLI when Codex must upload a local audio or video file.

## Connect with browser sign-in

1. Add the Podigee MCP server:

   ```sh
   codex mcp add podigee --url https://mcp.podigee.com/mcp
   ```

   Codex detects the Podigee sign-in and starts it at once. It opens your browser and also prints the authorization address.
2. Sign in to Podigee in the browser.
3. Select the Podigee account for this connection.
4. Review the client name, the selected account, and the requested permissions.
5. Approve the connection only when all details are correct.
6. Confirm the stored configuration:

   ```sh
   codex mcp get podigee
   ```

Run `codex mcp login podigee` to start the sign-in again later, for example after you add the server without a browser, or after you revoke the access in Podigee.

Codex asks for every Podigee permission when it signs in, which includes the write permissions. The `--scopes` option is available on `codex mcp login`, not on `codex mcp add`, so sign in again to hold a narrower authorization:

```sh
codex mcp login podigee --scopes mcp:podcasts:read,mcp:analytics:read
```

Then remove the wider authorization in **My account > API > Connector access**.

Podigee supports these permission values: `mcp:podcasts:read`, `mcp:analytics:read`, `mcp:listeners:read`, `mcp:content:read`, `mcp:podcasts:write`, `mcp:listeners:write`, and `mcp:media:write`.

Keep the default callback address. Codex receives the authorization code on the local address `127.0.0.1`, and Podigee accepts that address on any port. Podigee does not accept `localhost` and does not accept a callback on a remote host. Remove a custom callback host before you sign in.

## Connect with a personal access token

Use a token when the machine has no browser, or when the workflow is unattended.

1. Create an MCP token. See [Create and use a personal access token](/documentation/start-here/ai-agents/connect-and-authorize/create-and-use-a-personal-access-token.md).
2. Put the token in an environment variable that your shell reads from protected storage:

   ```sh
   export PODIGEE_TOKEN=pdg_pat_your_token
   ```
3. Add the server with the variable name:

   ```sh
   codex mcp add podigee --url https://mcp.podigee.com/mcp --bearer-token-env-var PODIGEE_TOKEN
   ```

Codex reads the variable when it starts the server. The name of the variable is stored in `~/.codex/config.toml`, and the secret is not:

```toml
[mcp_servers.podigee]
url = "https://mcp.podigee.com/mcp"
bearer_token_env_var = "PODIGEE_TOKEN"
```

## Verify the connection

Ask Codex:

> Which Podigee account are you connected to? List my podcasts. Do not make changes.

You can also run `codex mcp list` to see the configured servers, or `/mcp` in the Codex terminal interface to see the active servers of the current session.

## Expected result

Codex identifies one Podigee account and lists only the podcasts that this authorization can access. No Podigee data changes.

## If the connection fails

* `Dynamic client registration not supported`: update Codex to 0.154.0 or later, then run `codex mcp login podigee`. Podigee identifies a client through its published metadata document and does not register a client on request. Codex 0.154.0 and later can also select that method directly with `codex mcp login podigee --oauth-client-registration cimd`.
* The same message on a current Codex version: a custom callback host prevents the supported sign-in method. Remove the custom callback host, then sign in again. A fixed callback port is supported and needs no change.
* Codex reports an authentication error after a working connection: run `codex mcp login podigee` again. With a token, check the token expiry, the selected account, and the subscription state.
* Codex does not show the server: run `codex mcp get podigee` and confirm the URL `https://mcp.podigee.com/mcp`.

Do not paste a token into a chat message. Remove an exposed token in **My account > API** and create a replacement.

## Next step

[Choose permissions and scopes](/documentation/start-here/ai-agents/connect-and-authorize/choose-permissions-and-scopes.md) before you enable write work, or run [Connect and run your first read-only check](/documentation/start-here/ai-agents/start-here/connect-and-run-your-first-read-only-check.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.podigee.com/documentation/start-here/ai-agents/connect-and-authorize/connect-podigee-to-codex.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.