ShareCube

Create and share AI artifacts

ShareCube turns what your AI writes into a real document you can share and get feedback on. Ask your AI to draft a plan, a report, or a page, and it publishes to ShareCube as HTML or Markdown with its own URL.

What you can ask

Save this conversation as a doc in ShareCube
Example path →→ ·

MCP connector

Server URL: https://app.sharecube.io/mcp
Login: OAuth
Protocol: MCP 2026-07-28
Instructions: ShareCube stores editable HTML/Markdown artifacts in org projects, with selection-anchored comments. Typical flow: → (or / ) → . For a report, proposal, event page or other common document, check first and fill one with ; prefer the org's own templates when one fits. An artifact about a real place, a well-known person, an event or a product can be better with real photos, even unasked, when they suit its tone. Only use an image URL you have confirmed loads as an image, from a source that allows hotlinking; a broken <img> is worse than no image. People print HTML artifacts and save them as PDF, and the artifact's own print CSS decides how that looks: give anything document-like an @media print block (unlock 100vh/fixed/overflow-hidden layouts, hide controls, break-inside: avoid on cards and table rows). ShareCube keeps colours and sets the page margins, so leave out @page unless the format is fixed. To change part of an existing document, prefer (old_str/new_str, replaced server-side) over sending the whole body through ; it is much cheaper on a large document and old_str must match exactly and uniquely. After or , always share console_url with the user so they can continue editing, commenting, and managing visibility/permissions in the web console. share_url is the public share page (/share/:id, or /s/{slug} when the artifact has a short link); access still depends on artifact visibility settings (change those in the console, not via MCP). New comment threads: with body; optionally anchor {quote, start, end, occurrenceIndex} for a text selection (occurrenceIndex is the 0-based match of quote when it appears more than once). Replies: set parent_thread_id to the thread id and omit anchor. To mention a person in a comment, insert [@Display Name](mention://user/{user_id}) using their stable user id (not their display name). Unresolved @text is plain text and does not notify. Creating/updating artifacts requires Editor or Owner on the project; commenting requires Commenter+. Author fields: artifacts include created_by (user id) and created_by_name; comments include author_sub and author_name. Always prefer the display name when talking to the user.

Tools

Reads data9

Changes data7

Deletes or can't be undone3

Skills

1 in the ChatGPT listing

MCP connector

Server URL

https://app.sharecube.io/mcp

OAuth

Protocol

MCP 2026-07-28

Instructions

ShareCube stores editable HTML/Markdown artifacts in org projects, with selection-anchored comments. Typical flow: → (or / ) → . For a report, proposal, event page or other common document, check first and fill one with ; prefer the org's own templates when one fits. An artifact about a real place, a well-known person, an event or a product can be better with real photos, even unasked, when they suit its tone. Only use an image URL you have confirmed loads as an image, from a source that allows hotlinking; a broken <img> is worse than no image. People print HTML artifacts and save them as PDF, and the artifact's own print CSS decides how that looks: give anything document-like an @media print block (unlock 100vh/fixed/overflow-hidden layouts, hide controls, break-inside: avoid on cards and table rows). ShareCube keeps colours and sets the page margins, so leave out @page unless the format is fixed. To change part of an existing document, prefer (old_str/new_str, replaced server-side) over sending the whole body through ; it is much cheaper on a large document and old_str must match exactly and uniquely. After or , always share console_url with the user so they can continue editing, commenting, and managing visibility/permissions in the web console. share_url is the public share page (/share/:id, or /s/{slug} when the artifact has a short link); access still depends on artifact visibility settings (change those in the console, not via MCP). New comment threads: with body; optionally anchor {quote, start, end, occurrenceIndex} for a text selection (occurrenceIndex is the 0-based match of quote when it appears more than once). Replies: set parent_thread_id to the thread id and omit anchor. To mention a person in a comment, insert [@Display Name](mention://user/{user_id}) using their stable user id (not their display name). Unresolved @text is plain text and does not notify. Creating/updating artifacts requires Editor or Owner on the project; commenting requires Commenter+. Author fields: artifacts include created_by (user id) and created_by_name; comments include author_sub and author_name. Always prefer the display name when talking to the user.

Tools