An agent that writes a report is only half useful if the report stays in a chat. shareHub exposes an MCP server so the agent can turn what it wrote into a link you can send, with the access rules you choose, without you copying anything.
Connect once
The endpoint is https://sharehub.link/api/mcp. In Claude, open Settings, Connectors, Add custom connector, and paste it. A shareHub sign-in window opens; approve the connection and you are done: no key to copy and no token to store. In Claude Code:
claude mcp add --transport http sharehub https://sharehub.link/api/mcp
# then, inside Claude Code: /mcp -> sharehub -> AuthenticateOnly an organization owner or administrator can approve a connection, because it lets the agent act as your organization's publisher. The consent screen shows the real redirect address; do not approve one you do not recognize. Access renews on its own for 60 days, and you can disconnect from the dashboard's Connect page or from the client's connector settings. If your client has no OAuth support, an API key from the same Connect page works too.
Let the agent pick the path by size
| Content | Tool | Why |
|---|---|---|
| Notes, plans, reports | publish_markdown | Smallest and fastest. The agent sends Markdown as written; no HTML to generate. |
| A small HTML page (under about 50 KB) | publish_share | Inline HTML. |
| Anything larger, embedded images, Word, Excel, PDF | request_upload, then publish_by_ref | The file goes from disk to the server and never passes through the model's output. |
Why large files take a different road
A tool argument is text the model has to write out token by token. In our own measurement a 94 KB branded HTML document took about 71,000 tokens and more than 15 minutes that way, and a single wrong character is enough to corrupt an embedded image. The upload flow avoids all of it in three steps: the agent asks for a one-time upload ticket, a shell curl sends the file straight to shareHub, and the agent publishes it by reference. The upload needs no API key; it rides on the existing connection plus a ticket that expires in 15 minutes.
For Word, Excel and PDF files the same three steps apply: the converter runs on the server. PDFs are limited to 20 pages and every document to 5 MB.
You stay in control
- The agent sets the access mode when it publishes. Without one, the share is created email-code protected, and a share with no recipients is refused.
- Every share gets an end date (90 days unless the agent asks for another, 365 at most).
- Afterwards the agent can read the viewed status (
get_share_stats), update the content at the same link, and revoke it (revoke_share). - When an agent reads someone else's published document with
fetch_share, the result is marked as third-party content: data to read, never instructions to follow.
The full tool list, the REST alternative and the authentication details are in the developer documentation.
Frequently asked questions
Does it work with tools other than Claude?
Any client that supports a remote MCP server can connect to https://sharehub.link/api/mcp. The dashboard has examples for Claude Desktop, Claude Code and Cursor; other clients may offer different connection options.
Who can approve the connection?
An organization owner or administrator, because the connection acts as the organization's publisher.
How are large documents sent?
With the upload flow: the agent requests a one-time upload ticket, a shell command sends the file directly to shareHub, and the agent publishes it by reference, so the file never passes through the model's output.
Turn your document into a live link and decide who can open it.
Create account
Share a Word or Excel file as a link, no download
Turn a .docx or .xlsx into a page your reader opens in the browser. What carries over, what does not, and how to update it without sending a new file.
2 min read
Update a shared document without changing the link
How a live link keeps one address while its content changes, what a new version does to the viewed signal, and which files you can start from.
2 min read