Update a shared document from Claude Code and keep one link
How to use the ArtifactSend MCP in Claude Code to send an artifact once and push new versions to the same link, with example prompts.
The short answer
Add the ArtifactSend MCP server to Claude Code, send the artifact once, then ask Claude to update it. The tool update_artifact pushes a new version to the same link, and readers always see the latest version.
You keep building in your IDE. Your readers keep one link.
Why one link matters
Each new link costs you something. Readers open the old one. Analytics split across links. You send 'please use this version' emails. One link per document removes all of that.
Add the MCP server
- Use the server address https://artifactsend.com/mcp.
- In Claude Code, add it as a remote MCP server. In Claude Desktop, add it as a connector.
- Sign in to ArtifactSend when asked.
- Ask Claude to list the ArtifactSend tools to check the connection.
The tools
- send_artifact: share a file as a new private link.
- update_artifact: push a new version to an existing link.
- get_artifact: read the current version of an artifact.
- list_links: list your links.
- link_report: get the reading report for one link.
- reader_activity: see what one reader did.
- recent_activity: see recent opens across your links.
- update_link: change the door, allow list or expiry of a link.
- schedule_digest: set up a regular email summary.
Example prompts
- 'Send dist/report.html to ArtifactSend with an email code door. Allow only @acme.com.'
- 'I changed the pricing table. Update the ArtifactSend link for report.html.'
- 'Who opened the Q3 memo link today, and which sections did they read?'
- 'Set the board memo link to expire next Friday.'
- 'Show me what jane@fund.com did on the deck link.'
- 'Email me a summary of all link activity every Monday.'
A build loop that works
This loop suits specs, prototypes, reports and HTML decks. Readers see changes on their next open. You see whether each change helped.
- Build the page in your repo with Claude Code.
- Send it once with send_artifact and share the link.
- Check link_report to see where readers stop or rage click.
- Fix that part of the page.
- Run update_artifact. The link stays the same.
- Repeat after the next readers.
Cost and limits
The free plan includes 500 MCP calls a month. Each call to a tool counts as one call. After 500, calls cost $1 per 1,000. A typical day of sends, updates and reports uses a few dozen calls.
The MCP shares HTML, Markdown and Claude artifact files. PDF, Word and Excel uploads are coming.
Example session
You build a launch plan page in your repo. You ask Claude: 'Send plan.html to ArtifactSend with Google sign-in, allow only @acme.com.' Claude calls send_artifact and returns the link. You post the link in your team channel.
Two days later you ask: 'Who read the launch plan, and where did they stop?' Claude calls link_report. It tells you that five people read it and three stopped at the budget table.
You split the budget table into two short tables. You ask: 'Update the launch plan link.' Claude calls update_artifact. The team sees the new version at the same link. Next week you ask again and compare the read depth.
Use it as a team
Each team member can add the MCP server with their own sign-in. Members are free, and there are no seats to buy. Links live in your shared space, so one person can send an artifact and another can update it. The report keeps all readers under one link, whoever pushed the last version.
Good practice
- Keep one file per link in your repo, so Claude knows which link to update.
- Ask Claude to confirm the link before an update.
- Ask for a link_report after each update, so you see if the change helped.
- Use update_link, not a new link, to change who can read.