# Working with other capabilities Most of what makes Markdown worth having in the suite comes from what sits next to it. This page is the summary; each connection has its own page with the detail. Where a connection does not exist, it is listed as such rather than left out, so you can stop looking. --- ## Every connection | **Connects to** | **What you get** | | -------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | Capable Sites (published static sites) | Both macros export as real rendered HTML using markdown-it (html: false, linkify: true, typographer: true), sanitised, with external images downloaded and rewritten to local paths, wrapped in .c-macro--markdown. The document macro's Title and the reference macro's stored template title both become a | | Kroki diagram gateway | Every fenced diagram language is rendered server-side into a static SVG by Kroki, not by mermaid.js in the browser. Rendering requires a Capable client token. The self-hosted (customer-run) renderer code path exists but is currently switched off by a hard kill switch, so every markdown diagram goes. | | Capable URL proxy and egress | URL-sourced markdown is fetched through the Capable proxy unless the domain is on the tenant's approved egress list, in which case the browser fetches it directly. The app's own declared egress covers only Capable hosts (static.app, client.api.app, server.api.app, ws.api.app, plus Sentry), which is. | | Confluence custom content types | Markdown documents are stored as two Confluence custom content types whose visible names differ per app: 'Capable Custom Content (Markdown)' / 'Capable Shared Storage (Markdown)' standalone, and '(Suite)' in the Suite. Both declare preventDuplicateTitle, indexing and unlicensedAccess. | | Content indexing and CQL aliases | A markdown content indexing records referenced template ids under markdown.refs in the capable\_refs content property, exposed to CQL as \_capable\_refs\_markdown\_refs. Writes are re-indexed by created/updated custom-content triggers filtered to Capable content whose title starts with 'markdow | | Rovo agent | The standalone app ships its own Rovo agent named 'Capable Markdown' with eight verbs (capable-describe, -search, -get, -fetch, -create, -update, -insert, -upload-begin) and four conversation starters. It can write markdown documents onto pages from Rovo chat. In the Suite the equivalent is one comb | | 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 M | | Navigation entry points | Standalone: a 'Capable Markdown' space page, global page and global settings page (all three named 'Capable Markdown'), all carrying unlicensedAccess. Suite: one shared 'Capable' space page, global page and settings page, plus a second byline entry titled just 'Capable' (keyboard shortcut ',') along | | Macro migrators | They are run from the Migration settings tab. | --- ## The pages [Capable Sites (published static sites)Both macros export as real rendered HTML using markdown-it (html: false, linkify: true, ty](https://help.gocapable.com/markdown/capable-sites-published-static-sites.html) [Kroki diagram gatewayEvery fenced diagram language is rendered server-side into a static SVG by Kroki, not by m](https://help.gocapable.com/markdown/kroki-diagram-gateway.html) [Capable URL proxy and egressURL-sourced markdown is fetched through the Capable proxy unless the domain is on the tena](https://help.gocapable.com/markdown/capable-url-proxy-and-egress.html) [Confluence custom content typesMarkdown documents are stored as two Confluence custom content types whose visible names d](https://help.gocapable.com/markdown/confluence-custom-content-types.html) [Content indexing and CQL aliasesA markdown content indexing records referenced template ids under markdown.refs in the cap](https://help.gocapable.com/markdown/content-indexing-and-cql-aliases.html) [Rovo agentThe standalone app ships its own Rovo agent named 'Capable Markdown' with eight verbs (cap](https://help.gocapable.com/markdown/rovo-agent.html) [MCP surfaceMarkdown joins the Capable MCP resource surface for the app's own agent, but no markdown v](https://help.gocapable.com/markdown/mcp-surface.html) [Navigation entry pointsStandalone: a 'Capable Markdown' space page, global page and global settings page (all thr](https://help.gocapable.com/markdown/navigation-entry-points.html) [Macro migratorsThey are run from the Migration settings tab.](https://help.gocapable.com/markdown/macro-migrators.html) --- ## A few things worth knowing * A connection needs both halves installed. In a standalone app most of these do not exist. * Anything that depends on search only reflects pages that have been indexed. * Published sites render Capable macros properly, which is where several of these pay off. --- ## Related [IntegrationsThe section.](https://help.gocapable.com/markdown/integrations.html) [Capable for ConfluenceThe whole suite.](https://staging.dev.capable-sites.com/wiki/pages/1412890864) --- _Better with company._