> 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/compatibility-versioning-and-deprecation.md).

# Compatibility, versioning, and deprecation

Protocol eras, pdg policy, clients, languages, contract changes, and deprecation notices.

## Protocol versions

Podigee prefers MCP `2026-07-28` and retains `2025-11-25` for legacy wire compatibility. Modern clients use stateless requests and `server/discover`; legacy clients use initialization and session bootstrap.

## pdg compatibility

The pdg CLI prefers the modern protocol and can downgrade only after verified legacy-only discovery. It supports English, German, Spanish, French, and Polish. Local media workflows depend on the documented upload-session contract.

Podigee has not announced a public minimum `pdg` version. An approved release identifies its supported version. The server can publish update guidance. A blocked client receives `pdg_cli_update_required`.

## Connector availability

Podigee has not announced a public first-party ChatGPT or Claude directory listing. Other compatible MCP clients must implement the public OAuth and protocol contract.

## Change policy

Additive optional fields can appear within a compatible contract. Clients should ignore unknown response fields only where the negotiated schema allows them and must refresh authorization-sensitive catalogs according to `ttlMs`.

A breaking input, output, scope, state, or semantic change requires a versioned contract update, source-backed documentation, migration guidance, and a review of every affected guide and example.

## Deprecation notices

A deprecation notice should name the affected contract, replacement, migration action, first deprecated version, removal date or condition, and support path. Do not remove the old contract before its announced compatibility window is complete.


---

# 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/compatibility-versioning-and-deprecation.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.