A pasteable skeleton generated from the repository name. Check the project README for the exact package and arguments.
Star count
0 ★ · huangdun/tempmd-mcp · read from the repository page · (checked 2026-10-16 20:00:20)
Source
collected from the punkpeye/awesome-mcp-servers list · type: MCP server
Harvest history
first seen 2026-10-09 · last seen 2026-10-16 · seen 32× · listed by 7 sources
Score
score 703 · 7 sources · mcp
FAQ (answers come from our records)
How do I install it?
We did not find an install command for this repository (our install coverage is only about 4%). Check its README or releases page.
Who is it for?
We filed it under these tags: MCP 服务. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository huangdun/tempmd-mcp;first catalogued 2026-10-09;last seen 2026-10-16。There is no official certification or quality rating here — we record sources and dates only.
MCP server for temp.md — give agent-made artifacts one stable public link that updates in place. Publish an HTML, Markdown, CSV, or Mermaid artifact and get a canonical URL like amber-hill-9eb6.temp.md. Push new versions behind the same URL — no re-sharing, ever. Temps expire intentionally when the work goes cold (7-day active window, resets on every update) and can be restored within 7 days of expiry. Install **Remote — no install** Remote MCP accepts inline UTF-8 or base64 files. Anonymous publishing needs no credential. To publish directly into an account and use account tools, configure the connection with Authorization: Bearer . **Local stdio — best for filesystem access and larger directories** **Cursor / Windsurf / any MCP client** — add to your MCP config: tempmd-mcp remains available as a compatibility package with the same implementation and version. No account or API key required — temp.md is anonymous-create-first. Claim a Temp later to keep it. The remote transport is limited to 10 MiB and 20 inline files per bundle. The stdio package uses local paths and supports the full 50 MiB / 100-file bundle. Tools | Tool | Local stdio | Remote | What it does | |------|:-----------:|:------:|--------------| | publish_temp | ✓ | ✓ | Publish a new artifact and get a stable public URL | | update_temp | ✓ | ✓ | Push a new version behind the same URL | | get_temp_status | ✓ | ✓ | Check lifecycle and restore eligibility | | restore_temp | ✓ | ✓ | Bring a recently expired Temp back at the same URL | | snapshot_temp | ✓ | ✓ | Freeze the current version as a fixed reference | | set_comments | ✓ | ✓ | Toggle pinned visitor comments | | list_temps | ✓ | ✓ | List local project records or account-owned Temps | | recover_update_token | — | ✓ | Rotate and recover a lost scoped update token | publish_temp and update_temp accept spa_mode: true for client-routed single-page apps. Leave it off for static sites so missing assets return 404. Uploads are capped at 10 MB per file, 50 MB per bundle, and 100 files; publish and update limits are 60/hour/IP and 120/hour/Temp/IP respectively. How credentials work publish_temp saves a record (Temp ID, URL, update token, expiry) to a .tempmd file in the project root. Every other tool reads that file automatically, so an agent can update the same Temp across sessions without you managing tokens. Tokens can also be passed explicitly via update_token. Add .tempmd to .gitignore if the update token shouldn't be shared with everyone who can read the repo.