MCP connector reference

How the sharable.link connector connects, what it can do, and its limits. Setting it up for the first time? The step-by-step guide is shorter.

The server

  • URL: https://sharable.link/mcp, a remote MCP server over Streamable HTTP. Nothing to install.
  • Every request needs an OAuth 2.1 bearer token issued by sharable.link for that URL. Without one the server answers 401 with a WWW-Authenticate header that points to its protected-resource metadata at /.well-known/oauth-protected-resource.
  • Clients register themselves with Dynamic Client Registration and use PKCE (S256). Tokens are checked for issuer, audience (this URL only), expiry and scope on every call.

Connecting

  1. In Claude, open the sharable.link listing in the connector directory and click Add. Or go to Settings → Connectors → Add custom connector and paste the URL above, exactly, with no trailing slash.
  2. Sign in with Google or Microsoft, or with a link sent to your email. That creates a free sharable.link account the first time.
  3. Review what Claude may do on the consent screen and click Allow.
  4. Copy the prompt the next screen shows and paste it into Claude.

In Claude Code: claude mcp add --transport http sharable https://sharable.link/mcp, then run /mcp to sign in. Cursor, Cline and Windsurf take the same URL in their MCP settings.

In ChatGPT, the same server is the sharable.link plugin, with the same tools and the same account: how to add it.

Publishing through the connector always needs a signed-in account: every page it publishes belongs to a person. People who open a page don't need an account, unless the page is shared only with specific people.

Scopes

  • pages:read: list the account's pages, and send feedback.
  • pages:write: publish, update, replace and unpublish them. It covers reading too.
  • offline_access: a refresh token, so Claude stays connected without asking you to sign in again.
  • openid, profile, email: optional. An app that asks for them can see the account's ID, name and picture, and email address. The connector's tools don't need them, and the consent screen lists each one the app asks for.

A call to a tool its token's scope doesn't cover gets 403 naming the scope it needs. So does any call from a suspended account.

Tools

share_htmlPublish page

Publishes an HTML page of under 150 KB and returns its link. Optionally with a password, or shared only with named email addresses or company domains.

Scope pages:write · not read-only · not destructive · not idempotent · open world

update_pageUpdate published page

Replaces the content of a page the account owns with HTML of under 150 KB, changes who can view it, or both. The link stays the same. Without HTML, only the password or the list of people and domains changes, and the content stays as it is.

Scope pages:write · destructive · idempotent · open world

edit_pageEdit part of a page

Changes part of a page the account owns without sending the whole page: each edit replaces text exactly as it is in the published page, which has to occur once in it. The edits apply in order and all together, or not at all. It works on a page of any size, so a page of 150 KB or more is changed without the file. The link, the password and who can view it stay the same, and so does the title unless an edit changes the <title> tag or title is passed.

Scope pages:write · destructive · not idempotent · open world

unshare_pageUnpublish page

Removes a page the account owns. Its link returns 404 straight away.

Scope pages:write · destructive · idempotent · open world

upload_filePublish a file

For an HTML file of 150 KB or more, up to 25 MB. Shows an upload area in the chat, in claude.ai, Claude Desktop, Cowork and ChatGPT: the person drops the file, and it's published or replaces one of their pages; the link shows in the area and is passed back to the chat. Where the chat can't show the area, as in Claude Code in a terminal, it gives a link to the same upload area on sharable.link.

Scope pages:write · destructive · not idempotent · open world

list_my_pagesList my published pages

Lists the account's pages with their links, view counts, who can view them, and when they were last updated.

Scope pages:read · read-only · idempotent · closed world

send_feedbackSend feedback

Sends feedback about sharable.link to the person who builds it: something that didn't work, a missing feature, or something that worked. It takes the feedback, a sentiment, and optionally what the person was doing, the area and a page slug. A person reads every report, with the account it came from. The page itself and the conversation aren't attached. Reports are kept for 90 days.

Scope pages:read · not read-only · not destructive · not idempotent · open world

A tool that changes a page works only on pages the signed-in account owns. A page that isn't yours gets the same answer as one that doesn't exist, so the tools can't be used to find out which links are taken.

Limits

  • HTML sent inside a tool call (share_html, update_page) is for pages under 150 KB. A page of 150 KB or more goes through upload_file.
  • upload_file sends a file of up to 25 MB, in parts, and the browser upload takes the same size.
  • edit_page takes up to 50 edits under 150 KB in all in one call, on a page of up to 25 MB, and up to 10 calls a minute per account.
  • send_feedback takes up to 2,000 characters of feedback, and each account can send 3 reports a minute and 10 a day.
  • A page has a password or a list of people who can open it, never both.
  • A list can hold up to 100 email addresses and company domains.
  • Connector requests are rate-limited per account and per network, at around 60 a minute per account. Going over gets 429 with a Retry-After header.
  • An account can publish 30 new pages an hour and 200 a day, and keep 1,000 live pages adding up to 2 GB. In its first day the limits are 20 an hour, 50 a day, 50 live pages and 250 MB. Updating a page you've already published doesn't count. Going over, share_html and upload_file answer with an error that names the limit, and either when you can publish again or that you need to delete pages first.

Home-screen icon and app name

A page's link opens a small wrapper around the page, and the page itself is in a frame inside it. A phone that adds the page to its home screen reads the wrapper, so these tags are copied into it from the page's own <head>:

  • <link> with a rel of apple-touch-icon, apple-touch-icon-precomposed or icon, when the image is written into the page as a data: URL, with its sizes, type and media.
  • <meta> named apple-mobile-web-app-title, apple-mobile-web-app-capable, mobile-web-app-capable, apple-mobile-web-app-status-bar-style or theme-color.
  • A web app manifest written into the page as a data: link. Its names, description, language, colors, display mode, orientation and the icons written into it are kept, and the app it describes opens on the page's own link. A manifest file on another site isn't copied.

An icon's data: URL can be up to 256 KB, which is an image file of about 190 KB, and all the copied tags together up to 512 KB. A page can pass up to 12 icons and 4 theme colors, and an app name of up to 64 characters; a longer name is left out, not cut. An iPhone needs a PNG.

An icon that's only a link to an image on another site isn't copied: write the image into the page. No other tag from the page's head is copied; the link's title and description are the page's own, as before. The page's own icon also takes the place of ours in the browser tab.

A password-protected page carries the tags on its password screen; a page shared with specific people carries them only once the viewer is let in.

It works on pages that are already published and have these tags in them: the tags are read each time the link is opened.

Removing pages and access

  • Pages stay live until you remove them. Unpublish one with unshare_page or from your dashboard; the link returns 404.
  • Disconnect the connector in Claude under Settings → Connectors. That revokes Claude's access; your pages stay live.
  • Deleting your account, from the dashboard, deletes every page it published straight away.

Abuse and takedowns

  • What can't be published, such as phishing, malware, or other people's personal information, is in the terms of use.
  • Anyone can report a page, without an account, with the report form. Every report reaches our team by email.
  • A page taken down for breaking the terms serves 410 with a notice saying so, and its owner can no longer change or remove it. An account can be suspended, which takes down every page it published and stops it publishing.
  • Every page is tied to the account that published it.

Contact

Questions: email nazar@sharable.link. To add the connector now: Add to Claude.