Publishing over MCP, without installing anything

Most MCP servers ask you to install a package first. This one doesn't — it's a remote server, so an agent talks to it over plain HTTP with an API key.

Add it

claude mcp add --transport http sharemydocs https://sharemydocs.dev/api/mcp \
  --header "Authorization: Bearer smd_live_your_key"

That's the whole setup. No npx, no package to keep updated, no version drift between your machine and someone else's.

What the agent gets

tool	what it does
`publish`	markdown or sandboxed HTML in, live URL out
`update`	edit in place, keeping the URL and view count
`delete`	remove a page
`list`	everything you've published

Why remote

A stdio server is a process on your laptop: it has to be installed, it can go stale, and it can't be shared. A remote endpoint is just a URL — the same one for every client, updated server-side, and reachable from anywhere the agent runs.

The page you're reading was published through exactly this flow.