MCP surface

Markdown joins the Capable MCP resource surface for the app's own agent, but no markdown verb is published to third-party agents in either product: the standalone app deliberately omits rovo:mcp, and the Suite's rovo:mcp lists only the two approval verbs. Markdown assets never get a thumbnail. The MCP descriptor always reports previewStatus 'unavailable' and never returns a previewUrl.


#Settings that affect this

Setting

Where

What it does

There is no Markdown-specific settings t

-

It contributes only a byline, query actions, an asset browser, a Search panel, a custom content renderer, migrators and the two macros. Every switch above is a shared Capable settings surface.



Better with company.