> 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-claude.md). # Connect Podigee to Claude Add Podigee as a custom connector in Claude and authorize it with browser sign-in. Add the Podigee Model Context Protocol (MCP) server to Claude as a custom connector, then approve the connection in your browser. The first-party Podigee connector is not yet available in the public Anthropic Connectors Directory. Add the connector with the Podigee address in these steps. Do not connect a directory listing that uses the Podigee name until Podigee announces and links the verified listing. ## Before you start * Have an active Podigee account with AI agents access enabled. * Use a Claude plan that permits custom connectors. Claude states the current plan rules in [Get started with custom connectors using remote MCP](https://support.claude.com/en/articles/11175166). * Install the `pdg` CLI when the workflow must upload a local audio or video file. Claude cannot send a local media file through a connector. ## Add the connector on a Pro or Max plan 1. Open Claude. 2. Go to **Customize > Connectors**. 3. Select **+**, then select **Add custom connector**. 4. Enter this MCP server URL: ``` https://mcp.podigee.com/mcp ``` 5. Leave the advanced OAuth fields empty. Podigee does not need a client ID or a client secret from you. 6. Select **Add**. 7. Select **Connect** to start the authorization. 8. Sign in to Podigee in the browser window that opens. 9. Select the Podigee account for this connection. 10. Review the client name, the selected account, and the requested permissions. 11. Approve the connection only when all details are correct. ## Add the connector on a Team or Enterprise plan An Owner or Primary Owner adds the connector for the organization: 1. Go to **Organization settings > Connectors**. 2. Select **Add**. 3. Point to **Custom**, then select **Web**. 4. Enter the URL `https://mcp.podigee.com/mcp`. 5. Select **Add**. Each member then goes to **Customize > Connectors**, finds the Podigee connector, and selects **Connect** to authorize their own Podigee account. ## Use the connector in a conversation Select **+** in the chat, select **Connectors**, and switch on the Podigee connector for that conversation. ## Verify the connection Ask Claude: > Which Podigee account are you connected to? List my podcasts. Do not make changes. ## Expected result Claude identifies one Podigee account and lists only the podcasts that this authorization can access. No Podigee data changes. ## Connect Claude Code Claude Code runs in your terminal and cannot complete Podigee browser sign-in. It registers itself with the authorization server on request, and Podigee does not register a client that way. Claude Code reports `Incompatible auth server: does not support dynamic client registration`. A pre-configured client ID does not help, because Claude Code returns to an address on `localhost` and Podigee accepts only `127.0.0.1`. Connect Claude Code with an MCP personal access token instead: ```sh claude mcp add --transport http podigee https://mcp.podigee.com/mcp \ --header "Authorization: Bearer pdg_pat_your_token" ``` Claude Code stores the header in its own configuration. Protect that file, and replace the token if the file becomes readable by another person. See [Create and use a personal access token](/documentation/start-here/ai-agents/connect-and-authorize/create-and-use-a-personal-access-token.md). ## If the connection fails * The browser window closes before you approve: select **Connect** again and complete the authorization. * Claude returns the wrong Podigee account: remove the connector, add it again, and select the correct account. Each account needs its own authorization. * Claude reports an authentication error after a working connection: select **Connect** again to start a new authorization. Keep the connection read-only until Claude returns the intended Podigee account. ## 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 [connect Podigee to Codex](/documentation/start-here/ai-agents/connect-and-authorize/connect-podigee-to-codex.md) for terminal work. --- # 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-claude.md?ask=&goal= ``` `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.