> 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 to Claude from the Connectors directory and authorize it with browser sign-in. Add Podigee to Claude from the Connectors directory, then approve the connection in your browser. The connector then works in Claude on the web, in the desktop app, in the mobile app, and in Claude Code. ## Before you start * Have a Podigee account on a current plan. Connecting AI assistants is part of each current plan, starting with Launch. * Have a Claude account. Directory connectors are available on each Claude plan. * Claude cannot read a local audio or video file through a connector. Upload the file in Podigee on the **New episode** page, or use Claude Code, which runs on your computer. ## Check the listing The Podigee listing is at [claude.ai/directory/podigee](https://claude.ai/directory/podigee). Before you connect, make sure that the listing shows these details: * **Made by**: Podigee GmbH * **Connector URL**: `https://mcp.podigee.com/mcp` The listing has the label **Community**. Anthropic uses this label for a connector that a third party builds and that passed automated reviews by Anthropic. Podigee builds and operates this connector. The label does not change what the connector can do. Anthropic explains the labels in [Connector verification](https://claude.com/docs/connectors/verification). ## Add Podigee from the directory 1. Open the [Podigee listing](https://claude.ai/directory/podigee). You can also go to **Customize > Connectors**, select **Discover**, and enter `Podigee` in **Search connectors**. In the desktop app, select **Customize** in the sidebar, then **Connectors**. 2. Select **Connect to Claude**. 3. Sign in to Podigee. On claude.ai, the sign-in page opens in the same tab. In the desktop app, it opens in your browser. 4. Select the Podigee account for this connection, if Podigee asks. 5. Review the app name, the selected account, and the requested permissions. 6. Select **Connect** only when all details are correct. Claude shows Podigee under **Your connectors** with the status **Connected**. ## Add Podigee on a Team or Enterprise plan An Owner adds Podigee for the organization one time: 1. Open the [Podigee listing](https://claude.ai/directory/podigee). 2. Select **Connect for your team**. To try Podigee only for yourself first, select the arrow next to **Connect for your team**, then select **Connect just for me**. 3. Select **Connect to Claude** to connect your own Podigee account. Each member then opens the listing, selects **Connect to Claude**, and signs in with their own Podigee account. A member sees **Request** instead of a connect button when an Owner has not added Podigee yet. Anthropic explains requests in [Connectors directory](https://claude.com/docs/connectors/directory). ## Use the connector in a conversation Select **+** in the message box, select **Connectors**, and switch on Podigee for that conversation. When Claude asks for approval before it uses a Podigee tool, select **Allow once** or **Always allow**. To change these choices later, go to **Customize > Connectors**, select Podigee, and set each tool under **Tool permissions** to **Always allow**, **Needs approval**, or **Blocked**. Podigee also asks for your confirmation before a consequential change. See [Confirm a consequential change](/documentation/start-here/ai-agents/make-changes-safely/confirm-a-consequential-change.md). ## 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. ## Use Podigee in Claude Code Claude Code shows the connectors from claude.ai when you sign in to Claude Code with your Claude account. 1. Add Podigee in Claude with the steps above. 2. Start Claude Code and run `/mcp`. 3. Find Podigee in the list of connectors from claude.ai. If you sign in to Claude Code with an API key, or Claude Code does not show the connector, add the server in the terminal: 1. Run this command: ```sh claude mcp add --transport http podigee https://mcp.podigee.com/mcp ``` 2. Start Claude Code and run `/mcp`. 3. Select **podigee**, then start the authentication. 4. Sign in to Podigee in the browser window that opens. 5. Review the app name, the selected account, and the requested permissions. 6. Select **Connect** only when all details are correct. Podigee shows a connection that you add in the terminal as Claude Code, an app on your computer, because the sign-in returns to an address on your own machine. For an unattended script that cannot open a browser, use an MCP personal access token instead. See [Create and use a personal access token](/documentation/start-here/ai-agents/connect-and-authorize/create-and-use-a-personal-access-token.md). ## Add Podigee by address Use this method only when your Claude workspace does not show the directory. Claude calls this a custom connector. Claude states the plan rules in [Get started with custom connectors using remote MCP](https://support.claude.com/en/articles/11175166). 1. Go to **Customize > Connectors**. 2. Select **+**, then select **Add custom connector**. 3. Enter this MCP server URL: ``` https://mcp.podigee.com/mcp ``` 4. Leave the advanced OAuth fields empty. Podigee does not need a client ID or a client secret from you. 5. Select **Add**, then select **Connect**. 6. Sign in to Podigee and approve the connection only when all details are correct. Do not add a connector with the Podigee name and a different MCP address. ## If the connection fails * The browser window closes before you approve: select **Connect** again and complete the authorization. * Claude returns the wrong Podigee account: go to **Customize > Connectors**, select Podigee, select **Disconnect**, then connect again and select the correct account. Each account needs its own authorization. * The connector shows **Reconnect**: select **Reconnect** and sign in to Podigee again. * You see **Request** instead of a connect button: ask an Owner of your Claude organization to add Podigee. * Podigee shows that AI assistants are part of the current plans: your account is on an earlier plan. Select **See plans** to change the plan, then start the connection again. Keep the connection read-only until Claude returns the intended Podigee account. ## Remove the connection In Claude, go to **Customize > Connectors** and select Podigee. Select **Disconnect** to sign Claude out of Podigee, or open the three-dot menu and select **Remove**. On a Team or Enterprise plan, an Owner removes Podigee for the organization in **Organization settings > Connectors**. You can also revoke the access in Podigee. See [Review and revoke connected clients](/documentation/start-here/ai-agents/connect-and-authorize/review-and-revoke-connected-clients.md). ## 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` 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 what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.