> 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/choose-permissions-and-scopes.md).

# Choose permissions and scopes

Choose the minimum Podigee MCP permissions required for an agent workflow.

Grant only the Model Context Protocol (MCP) permissions that the intended workflow needs.

## Permission groups

| Permission in the token settings          | Scope                 | Allows                                                                                  |
| ----------------------------------------- | --------------------- | --------------------------------------------------------------------------------------- |
| Read podcasts and episodes                | `mcp:podcasts:read`   | Read podcasts, episodes, distribution, productions, and operation status                |
| Read podcast content and generated assets | `mcp:content:read`    | Read transcripts, search podcast content, and inspect generated content assets          |
| Read podcast and episode analytics        | `mcp:analytics:read`  | Read podcast analytics, episode analytics, and available report metadata                |
| Read private-feed listeners               | `mcp:listeners:read`  | List and inspect private-feed listener access                                           |
| Create and update podcasts and episodes   | `mcp:podcasts:write`  | Create and change podcasts or episodes, publish, import, and submit supported platforms |
| Manage private-feed listeners             | `mcp:listeners:write` | Add listeners, change listener state, send resets, and change feed protection           |
| Upload and process media                  | `mcp:media:write`     | Create upload sessions, attach uploaded media, and control encoding production          |

The browser consent page lists the same scopes with the words "View your", "Create and update", "Manage your", and "Upload and process".

Write scopes do not automatically include the corresponding read scope. Select every scope that the complete workflow requires.

## Choose the smallest useful set

Use these examples as a starting point:

| Workflow                                  | Suggested scopes                                                 |
| ----------------------------------------- | ---------------------------------------------------------------- |
| Inspect podcasts and episodes             | `mcp:podcasts:read`                                              |
| Read transcripts and search what was said | `mcp:podcasts:read`, `mcp:content:read`                          |
| Review analytics                          | `mcp:podcasts:read`, `mcp:analytics:read`                        |
| Update existing episode metadata          | `mcp:podcasts:read`, `mcp:podcasts:write`                        |
| Publish a local media file                | `mcp:podcasts:read`, `mcp:podcasts:write`, `mcp:media:write`     |
| Manage private-feed listeners             | `mcp:podcasts:read`, `mcp:listeners:read`, `mcp:listeners:write` |

The exact tool catalog remains authoritative. Each tool declares its required security scopes.

## Important limits

A scope permits a category of request. It does not bypass account ownership, podcast permissions, plan allowances, preview and confirmation, write rollout controls, or operation policy.

Legacy API keys and legacy `read`, `read_write`, or `admin` labels do not grant MCP authority.

## Related tasks

* [Add write access to an existing connection](/documentation/start-here/ai-agents/connect-and-authorize/add-write-access-to-an-existing-connection.md)
* [Create and use a personal access token](/documentation/start-here/ai-agents/connect-and-authorize/create-and-use-a-personal-access-token.md)


---

# 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/choose-permissions-and-scopes.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.