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

# Scopes and permissions

The seven public Podigee MCP scopes and how they combine with resource permissions.

## Public scopes

| Scope                 | Access                                                                                  |
| --------------------- | --------------------------------------------------------------------------------------- |
| `mcp:podcasts:read`   | Podcast, episode, production, operation, and distribution reads as mapped by each tool. |
| `mcp:content:read`    | Transcript search and generated content asset reads.                                    |
| `mcp:analytics:read`  | Podcast and episode analytics plus available report metadata.                           |
| `mcp:listeners:read`  | Protected-feed listener reads.                                                          |
| `mcp:podcasts:write`  | Podcast, episode, import, publishing, production, and distribution changes as mapped.   |
| `mcp:listeners:write` | Feed-protection and listener changes.                                                   |
| `mcp:media:write`     | Upload control and media attachment or publishing actions as mapped.                    |

Each tool page lists its exact required scopes. A tool with multiple scopes requires all of them. Identity discovery can require no explicit scope but still requires an active MCP credential.

## Permission intersection

A scope is necessary but not sufficient. The current user must also have resource-level permission for the podcast, episode, analytics, distribution, or listener action. The selected tenant must own or contain the target. Plan and allowance gates also remain authoritative.

## Minimum-scope examples

* List podcasts: `mcp:podcasts:read`.
* Read transcripts and assets: `mcp:content:read` plus the mapped podcast visibility.
* Read analytics: `mcp:analytics:read` plus podcast analytics permission.
* Upload media: `mcp:media:write`.
* Publish uploaded media: `mcp:media:write` and `mcp:podcasts:write`.

## Missing scope

The server returns an insufficient-scope error that names the required scopes. Reauthorize the client with the minimum missing scope. Do not mint or share a broader token as a shortcut.


---

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