> 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/start-here/choose-how-to-use-podigee-for-ai-agents.md).

# Choose how to use Podigee for AI agents

Choose the Podigee AI connection that matches your client, media, and automation needs.

Choose a compatible Model Context Protocol (MCP) client or an approved `pdg` command-line interface (CLI) build. Claude and Codex connect today with browser sign-in. Public first-party ChatGPT and Claude directory listings are a separate release.

## Choose a connection

| Your work                           | Recommended connection                               | Why                                                                                                                       |
| ----------------------------------- | ---------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------- |
| Use Podigee in ChatGPT              | Wait for the verified Podigee app listing            | Podigee has not announced a public listing. Use another compatible client now.                                            |
| Use Podigee in Claude               | Custom connector in Claude                           | Claude connects to the Podigee MCP server and you approve the account in the browser.                                     |
| Work in a terminal with Codex       | Codex 0.154.0 or later with browser sign-in          | Codex runs on your computer and receives the Podigee authorization on a local address. An earlier version cannot sign in. |
| Publish a local audio or video file | `pdg` CLI                                            | The CLI can read the local file and upload its bytes directly to Podigee.                                                 |
| Use another AI application          | Compatible remote MCP client                         | The client can discover the Podigee MCP server and request access through OAuth.                                          |
| Run an unattended script            | `pdg` CLI or MCP client with a personal access token | A token avoids an interactive browser login. Store it as a secret.                                                        |

You can use more than one connection. Each authorization applies to one selected Podigee account or organization.

## Plan for first-party connectors

A directory listing is separate from a custom connector. You can add the Podigee MCP address as a custom connector today. A first-party listing removes that manual step and shows a verified publisher.

Podigee has not announced a public ChatGPT or Claude listing. Do not connect a directory listing that uses the Podigee name until Podigee announces and links the verified listing.

## Use the pdg CLI for local media

Use `pdg` when the workflow must read a file from your computer. The CLI transfers media directly to Podigee, then uses the same protected Podigee workflows as other clients.

The CLI is also useful for repeatable terminal workflows, structured JSON output, and long-running publication operations.

## Use another MCP client for portability

Podigee exposes a remote MCP server at `https://mcp.podigee.com/mcp`. A compatible client can discover the authorization flow, ask you to approve access, and use the Podigee capabilities that match the granted scopes.

Client support differs. Confirm that the client supports remote Streamable HTTP servers and OAuth before you connect it.

## Local media boundary

Chat messages and MCP tool calls do not carry large media files. A hosted connector cannot read a file from your computer unless the application provides a separate local execution environment.

Use `pdg` for the upload. You can then continue the episode workflow from another authorized client. Podigee does not fetch episode media from a remote URL through MCP.

## Next step

[Connect and run your first read-only check](/documentation/start-here/ai-agents/start-here/connect-and-run-your-first-read-only-check.md) before you grant write access or prepare a publication.


---

# 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/start-here/choose-how-to-use-podigee-for-ai-agents.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.