> 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-resources/media-upload-recipe.md).

# podigee://docs/media-upload

Reference for the \`podigee://docs/media-upload\` MCP resource.

Read `podigee://docs/media-upload` to retrieve this resource.

## Contract

| Property        | Value                                                   |
| --------------- | ------------------------------------------------------- |
| URI             | `podigee://docs/media-upload`                           |
| Required scope  | `mcp:media:write`                                       |
| Parameters      | None.                                                   |
| Returned format | Markdown text inside the MCP resource `contents` array. |

## Example request

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "resources/read",
  "params": {
    "uri": "podigee://docs/media-upload"
  }
}
```

For a URI template, replace each placeholder before the request. Encode query values when needed.

## Result

The `pdg upload` and direct HTTPS upload sequence, including the boundary between MCP control calls and file-byte transfer.

### Parsed content schema

After a client parses the resource `text` field as described above, the result matches this schema. For the Markdown upload recipe, the parsed value is the Markdown string itself.

```json
{
  "type": "string",
  "contentMediaType": "text/markdown"
}
```

The MCP response uses a `contents` array. Read the `text` field in the first matching content item, then parse it as JSON when the resource format is JSON. A resource response is a current snapshot. It does not subscribe the client to later changes.

## Compatibility note

The current discovery metadata advertises `application/json` for this resource. The returned content item uses `text/markdown`. Clients must use the `mimeType` on the returned content item. A release review must align the discovery metadata before this page is published.

## Errors and recovery

The server rejects an invalid URI, a missing required query parameter, a resource outside the connected account, or a request without `mcp:media:write`. Correct the URI or authorization before retrying. Pagination parameters must remain within the public limits.

## Related guides and reference

* [Media upload protocol](/documentation/start-here/ai-agents/mcp-reference/media-upload-protocol.md)
* [Upload local media with the pdg cli](/documentation/start-here/ai-agents/transfer-media-encode-and-publish/upload-local-media-with-the-pdg-cli.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/mcp-resources/media-upload-recipe.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.