> 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/endpoint-and-protocol-compatibility.md).

# Endpoint and protocol compatibility

Streamable HTTP, JSON-RPC, protocol versions, routing metadata, and stateless behavior.

## Transport

Send authenticated MCP requests to `https://mcp.podigee.com/mcp` over HTTPS. Requests use JSON-RPC 2.0 and Streamable HTTP. The server can return JSON or an event stream where the client permits it.

The JSON-RPC request body must stay within the public request-size limit. Media bytes use the separate upload protocol and never appear in MCP JSON.

## Preferred protocol

`2026-07-28` is the preferred protocol version. Send it in `MCP-Protocol-Version` and request `_meta`. Modern requests also send `Mcp-Method` and, for `tools/call`, `resources/read`, and `prompts/get`, `Mcp-Name`.

Modern requests are stateless. They do not require `initialize`, `notifications/initialized`, `ping`, or an MCP session ID. Successful results include `resultType: "complete"` and server identity.

## Legacy compatibility

`2025-11-25` remains available for compatible clients. It uses `initialize`, then `notifications/initialized`, and can use `ping`. The negotiated version is sent in `MCP-Protocol-Version` after initialization.

Clients must not silently downgrade after authentication, authorization, rate-limit, network, server, metadata, or malformed-response errors. Downgrade only when discovery proves that the server is legacy-only.

## Catalog caching

Authorization-sensitive modern catalogs report `cacheScope: "private"` and currently use `ttlMs: 0`. Refresh the tool catalog before relying on dynamic parameter-to-header annotations.

## Unknown methods

Both eras return JSON-RPC code `-32601`. Modern requests use HTTP 404 for the unknown method; legacy requests use HTTP 200.


---

# 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/endpoint-and-protocol-compatibility.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.