The five tools cover the whole life of a document — publish, update, delete, list — and re-sharing a file path lands on the existing link rather than scattering new ones, so the URL you already sent stays correct. Editing rights travel with a local .plsreadme file, which means the machine that published a document is the machine that can change it.
A publishing server for markdown. It takes a local .md file or raw text, uploads it to plsreadme.com, and hands back a permanent URL that renders in any browser.
- Share a local markdown file by path — re-sharing the same file updates the existing link instead of creating a second one
- Share text directly; plain text is auto-structured into markdown before upload
- Update a published document by document ID or by the original file path
- Delete a published document permanently
- List everything you have shared, with document IDs, titles, URLs and source files
A plsreadme account for owned documents. Two ways in: the hosted endpoint https://plsreadme.com/mcp over HTTP, where the first authenticated call opens browser login; or local stdio with npx -y plsreadme-mcp. Clients that cannot complete browser login send a personal key instead — create it at /my-links and pass PLSREADME_API_KEY for stdio or an Authorization: Bearer header for HTTP. Local stdio expects PLSREADME_API_KEY by default; PLSREADME_ALLOW_ANONYMOUS=1 restores the older anonymous mode. Edits are keyed to a local .plsreadme record file, which stores the admin token per document.
One command plus a key — npx -y plsreadme-mcp, then supply credentials