ChatGPT Plugin

ShareCube

Create and share AI artifacts

Brand: Unknown

Category: Pending
Primary Subcategory: Pending

Integration details

Description

ShareCube turns what ChatGPT writes into a real document you can share and get feedback on. Ask ChatGPT to draft a plan, a report, or a page, and it publishes to ShareCube as HTML or Markdown with its own URL. You choose who sees it: keep it private, share it inside your organisation, or open it to anyone with the link. Reviewers highlight a sentence and comment on it, the way they would in a document. ChatGPT can read those comments back and revise. Every version is kept, so you can see what changed and restore an earlier one. It's useful when the people reviewing your work don't use ChatGPT themselves, when review comments would otherwise be scattered across a thread, and when you want the things an agent wrote to still be findable next month. Free to start. The same documents are reachable from Claude, Cursor and other MCP clients, so you aren't locked to one assistant.

Integration type: Plugin
Verification status: Not applicable
Platform: ChatGPT
Category: Pending
Primary Subcategory: Pending
Secondary Subcategories: None listed
Brand: Unknown
Access: Account optional
First tracked: 2026-10-15
Tool count: 15
Geography: US

Agent DiscoverabilityChatGPT Plugin Discovery Score

ChatGPT organic discovery is live

Your score is coming

ChatGPT now suggests Plugins on its own when they match a user's request.Your Plugin Discovery Score measures how often yours appears, and it will show here as soon as it’s ready.

ChatGPT recommends Airtable when a user asks it to update a CRM. — ChatGPT surfaces Airtable because it matches the user's request.

Primary Subcategory

Competitive lineup

No Primary Subcategory assigned yetOnce ShareCube has a Primary Subcategory, the Plugins and Connectors it competes with will appear here with their scores.

Tools

15 tools agents can invoke

Add a comment. New thread: omit parent_thread_id; optionally pass anchor {quote, start, end} for a selection (quote must match content.slice(start, end)). Reply: set parent_thread_id to the thread id and omit anchor. Requires Commenter+ on the project. Response includes author_sub + author_name. To mention someone, insert [@Display Name](mention://user/{user_id}) using their stable user id.
create_comment
Create an HTML or Markdown artifact in a project (Editor/Owner) — the default, simplest way to create one: one call, content included. Use this unless the document is large (say, above a few hundred KB) AND you can also issue a raw outbound HTTP request yourself outside of tool calls — only then is request_artifact_upload worth the extra step. On success, response includes created_by + created_by_name and console_url — return console_url to the user so they can open the artifact in the ShareCube web app to edit further and manage visibility/permissions. share_url is the public link path (access still depends on visibility set in the console).
create_artifact
Create a new project in the caller's org. The caller becomes Owner. Use the returned projectId as project_id for create_artifact. There is no name-uniqueness constraint — check list_projects first if you want to avoid a duplicate.
create_project
Permanently delete an artifact (Editor/Owner).
delete_artifact
Delete a comment. Omit reply_id to delete the whole thread; set reply_id to delete one reply.
delete_comment
Edit a comment or reply body. Omit reply_id to edit the thread root; set reply_id to edit a reply.
update_comment
Load artifact metadata and full content. Response includes created_by + created_by_name, console_url (web app editor, comments, sharing/permissions), and share_url (public share page). Always give the user console_url when they need to continue editing or manage access. The response also includes current_version_id — keep it and pass it as base_version_id if you later call update_artifact or request_artifact_upload (update mode). After an out-of-band PUT from request_artifact_upload, poll this tool: you succeeded only if current_version_id is a new id AND the content is your revision. content_upload_error=conflict means a concurrent save won — re-read, rebase, retry. If current_version_id is still the base after about a minute, the PUT never finalized — re-read and retry. Do not treat "the version id changed" alone as proof your PUT won.
get_artifact
Get one comment thread (root + replies) by artifact_id and thread_id.
get_comment
List artifacts. Pass project_id to scope to one project; omit it to list all accessible artifacts in the org. Each item includes created_by + created_by_name, and console_url / share_url when configured.
list_artifacts
List comment threads and replies on an artifact. Each item includes author_sub + author_name. Optionally filter by status (open, resolved, orphaned).
list_comments
List projects the API key owner can access. Use projectId from the result as project_id when creating or listing artifacts. Requires membership; Editor/Owner needed to create artifacts.
list_projects
Out-of-band HTTP PUT for large HTML/Markdown bodies — skip this unless you can issue a raw outbound HTTP PUT yourself, separately from MCP tool calls. This tool does not send the bytes; it only mints {artifactId, upload_url, console_url}. Then PUT the raw file to upload_url (no Authorization header, no Content-Type). Two modes: CREATE — project_id + display_name + type (do not pass id). The new artifact is invisible until the PUT lands, and the pending upload expires after 1 hour. UPDATE — id + base_version_id from get_artifact (do not pass project_id or type; optional display_name). Use this to revise an existing artifact; do NOT call this in create mode a second time — that mints a new id and strands comments/share URL. After the PUT, poll get_artifact: success is a new current_version_id whose content is your revision (usually a few seconds). If content_upload_error is conflict, or current_version_id moved to someone else's save, rebase and retry. If it is still the base after about a minute, retry. For small edits or title-only changes, use update_artifact instead.
request_artifact_upload
Resolve (resolved=true) or reopen (resolved=false) a comment thread.
resolve_comment
Full-text search across artifacts the caller can access. Returns matching artifact metadata (including console_url when available).
search_artifact
Update artifact content and/or display_name (Editor/Owner). Default for small inline edits and title-only changes. For a large document body (say, above a few hundred KB) that you can PUT over raw HTTP, use request_artifact_upload with id + base_version_id instead — do not create a second artifact. Creates a new content version when content is provided. When you update content, ALWAYS pass base_version_id set to the current_version_id you got from get_artifact (or from your own previous update_artifact response). The update is then rejected with a conflict error if someone else saved in between, instead of silently overwriting their work — people edit these documents in the web app while agents write to them. On a conflict error, re-read with get_artifact, re-apply your edit to the latest content, and retry.
update_artifact

FAQs

ShareCube ChatGPT Plugin FAQ

How the directory, categories and Discoverability Score work.

Read the methodology

How do I improve ShareCube's ChatGPT Plugin discoverability?

The levers are the listing surface agents actually read: names, descriptions, keywords, tool metadata, and registry health. Which lever matters depends on where discovery breaks, which is what continuous measurement shows.

Where is this profile measured?

This profile uses the geography attached to the latest public registry snapshot: US. Locale tags are intentionally omitted.