Add MCP server schema dialect and SDK v2 compatibility section

[pwizla]

This PR adds a "Compatibility and schema changes" section to the MCP server page covering the SDK v2 upgrade shipped in strapi/strapi#27505. The new section explains that tool schemas are now serialized as JSON Schema 2020-12 (instead of draft-07), lists the formatting differences that strict clients will observe (prefixItems for tuples, $defs for recursive schemas), and notes that clients previously affected by the silent tool-drop bug described in strapi/strapi#27395 no longer need a workaround. It also documents that handler context and capability result types are now Strapi-owned, keeping them stable across future SDK updates.

Documents #27505

Direct preview link 👉 here

[strapi-cla]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
documentation	Ready	Preview	Sep 9, 2026 1:52am UTC

[pwizla]

Hey @nclsndr the docs self-healing caught your changes and created this PR. Do you think we need this level of detail in the official Strapi MCP docs?
I also saw a long description and migration guide in the corresponding strapi/strapi PR; if this is considering a breaking change for the MCP, shouldn't we document this on docs.strapi.io too? 🤔