Glad it’s useful!
Discourse MCP could add content negotiation as an optional path. It would not need to require this plugin, it could request Accept: text/markdown from the canonical topic/post URL and fall back to the current JSON API behavior if the site does not support Markdown.
This plugin is just one way for a Discourse site to satisfy that request today. Without either this plugin or equivalent support in Discourse core, the Accept header alone would not change the JSON API output.
So the ideal MCP integration might be: try text/markdown on the content URL first, then fall back to /t/:id.json?include_raw=true.