FacundoLucci/plsreadme

Paste markdown. Get a beautiful, shareable link. Done.
Website ·
MCP Package ·
Request a Feature
---
The Problem
You wrote a README, a PRD, meeting notes, or an API doc in markdown. Now you need to share it with someone who doesn't have a markdown renderer, doesn't use GitHub, or just needs a clean link they can open in a browser.
**plsreadme** turns any markdown into a permanent, beautifully rendered web page in one step. No accounts. No sign-ups. No friction.
✨ Features
- **Instant sharing** — Paste markdown or upload a file, get a plsrd.me link
- **Beautiful rendering** — Clean typography, dark mode, mobile-responsive
- **Inline comments** — Readers can click any paragraph and leave feedback
- **Review mode (current vs timeline)** — Multi-version docs default to **Current draft** feedback with one-click access to full **Timeline** history
- **AI auto-formatting** — Throw raw text at it; it comes out as clean markdown
- **MCP server** — Share docs directly from Claude, Cursor, VS Code, or any MCP client
- **OpenClaw skill** — Available on ClawHub for AI agent workflows
- **Short links** — Every doc gets a compact plsrd.me/v/xxx URL
- **Raw access** — Download the original .md file from any shared link
- **Version timeline + safe restore** — /v/:id/versions + /v/:id/history + archive-first restore API for fast rollback
- **Clerk auth foundation** — GitHub/Google sign-in wiring + Clerk-hosted email fallback + backend auth verification utilities
- **Ownership model (Phase 2)** — docs can be linked to a Clerk user (owner_user_id) while preserving anonymous flows
- **My Links dashboard (Phase 3)** — authenticated /my-links page with search/sort/pagination and quick copy/open actions
- **Legacy link claiming (Phase 4)** — signed-in users can claim older anonymous links by proving the original admin_token
- **Zero config website demo** — No account or API key needed to try it in the browser
🚀 Quick Start
Web
Go to plsreadme.com, paste your markdown, click share.
Auth Paths And Rollout State
Recommendation order:
1. **Try in browser first** — fastest demo path, no MCP setup required.
2. **Use hosted remote MCP with browser login** when client support is verified.
3. **Use API key / local MCP fallback** when interactive login is unavailable.
Current rollout state:
| Journey | Status today | Ownership rule | Source tag |
| --- | --- | --- | --- |
| Anonymous website demo | Available now via browser-verified demo flow | owner_user_id = NULL until user later saves/claims the doc | web_demo |
| Signed-in website create | Available now | doc is created with the signed-in Clerk user as owner | web_signed_in |
| Hosted remote MCP with browser login | Available now in supported clients | creates owned docs for the signed-in user after browser login | mcp_remote_login |
| Hosted remote MCP with API key | Available now as the compatibility fallback | creates owned docs for the API key owner | mcp_remote_api_key |
| Local npm MCP with API key | Available now and recommended for local stdio setups | creates owned docs for the API key owner | mcp_local_api_key |
| Local npm MCP anonymous fallback | Still available only with explicit opt-in | remains anonymous unless later claimed/saved | mcp_local_anonymous |
Hosted remote MCP rollout notes:
- https://plsreadme.com/mcp
- https://plsreadme.com/sse
Those hosted remote MCP routes are live behind OAuth-protected browser login in code, including /authorize, /oauth/token, and /oauth/register.
Operational notes:
- D1 doc_create_events is the canonical create-attribution table across web, hosted MCP, and local MCP flows.
- docs.raw_view_count tracks every render hit, while docs.view_count is reserved for likely-human reads.
- See docs/runbooks/auth-surface-monitoring.md for the production query set and response steps.
- access tokens last about 1 hour
- refresh tokens last about 30 days
- reconnecting the same client replaces the older grant
- signing out of the website does not revoke an existing editor grant by itself