> 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-chatgpt.md).

# Connect Podigee to ChatGPT

Check Podigee app availability in ChatGPT and use a verified alternative when needed.

The first-party Podigee app is not yet available in the public ChatGPT app directory. Do not connect an app that uses the Podigee name until Podigee announces and links the verified listing.

## Before you start

* Have an active Podigee account.
* Decide whether your workflow can use another compatible MCP client or the `pdg` CLI.
* Use `pdg` when an agent must upload a local file.

## Use a current connection path

1. Use another remote Model Context Protocol (MCP) client that supports Streamable HTTP and OAuth.
2. Set its MCP endpoint to `https://mcp.podigee.com/mcp`.
3. Complete Podigee authorization and select one account.
4. Run a read-only account check before you grant write access.

Use the `pdg` CLI instead when the workflow starts with a local audio or video file.

## Verify the connection

Ask the connected client:

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

## Expected result

The client identifies the selected Podigee account and lists only the podcasts available through that authorization. No Podigee data changes.

## When the first-party app launches

This page will show the tested ChatGPT steps only after the verified directory listing is public. The listing announcement will identify its publisher, support link, privacy information, and connection flow.

Do not use an unverified listing, a similar name, or an MCP address supplied by an unknown party.

## If the current connection fails

Confirm that the alternative client supports remote Streamable HTTP and OAuth. Start a new authorization request after an expired browser flow. Keep the workflow read-only until the client returns the intended Podigee account.

## Next step

[Connect another compatible MCP client](/documentation/start-here/ai-agents/connect-and-authorize/connect-another-compatible-mcp-client.md), or [install the pdg CLI](/documentation/start-here/ai-agents/connect-and-authorize/install-the-pdg-cli.md) when an approved distribution is available.


---

# 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-chatgpt.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.