> 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-another-compatible-mcp-client.md).

# Connect another compatible MCP client

Connect a compatible remote MCP client to Podigee through the protected public endpoint.

Connect an AI application that supports remote Model Context Protocol (MCP) servers and OAuth.

## Before you start

* Confirm that the client supports remote Streamable HTTP MCP servers.
* Confirm that the client supports OAuth authorization for protected MCP resources.
* Have an active Podigee account.
* Use the production Podigee MCP endpoint only for production account data.

## Add the Podigee server

1. Open the client's MCP server or connection settings.
2. Add a remote HTTP server.
3. Enter this endpoint:

   ```
   https://mcp.podigee.com/mcp
   ```
4. Start the connection.
5. Allow the client to open the Podigee authorization page.
6. Sign in to Podigee.
7. Review the client name, selected account, return host, and requested permissions.
8. Approve the connection only when all details are correct.

Do not enter the authorization-server URL as the MCP endpoint. A compatible client discovers the authorization server from the protected-resource metadata.

## Verify the connection

Ask the client to identify the connected account and list accessible podcasts without making a change. A client can call `get_me` and `list_podcasts` for this check.

## Expected result

The client completes OAuth, connects to `https://mcp.podigee.com/mcp`, and returns the selected Podigee tenant and accessible podcasts.

## If the client cannot connect

Check that the client supports Streamable HTTP, protected-resource metadata, authorization-code OAuth with S256 Proof Key for Code Exchange (PKCE), and bearer authentication.

Do not work around an OAuth failure by pasting a token into a chat message. Use a protected client secret field or the personal-access-token path when the client supports one.

## Next step

[Choose permissions and scopes](/documentation/start-here/ai-agents/connect-and-authorize/choose-permissions-and-scopes.md) before you enable write 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-another-compatible-mcp-client.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.