publishingstatic-hostingmarkdownartifactsremote-mcp
tempmd-mcp publishes agent-made HTML, Markdown, CSV, or Mermaid artifacts to one stable public URL that updates in place, via a remote or local stdio MCP server.
Quick Install
Automated & IDE SetupCopy the AI prompt to install this server into Claude Code, Cursor, or another agent — or use 1-click editor setup below.
Not yet automatically verified
We haven't yet run this listing's install command through our automated sandbox check. This isn't a red flag — we're steadily working through the catalog.
Manual Client & Custom JSON ConfigExpand JSON ▾
Client Config & Setup
Choose your client or environment
Target File:
💡 Paste the JSON block into your client's configuration file under mcpServers, then restart the application.
Overview
Use cases
Publish an agent-generated HTML or Markdown report to a stable public URL
Push an updated version of an artifact behind the same existing URL
Check whether an expired Temp can still be restored
Freeze the current version of an artifact as a fixed snapshot
Key features
One stable, canonical URL per artifact that updates in place
Supports HTML, Markdown, CSV, and Mermaid artifacts
7-day active window that resets on update; 7-day restore grace period after expiry
No account or API key required — anonymous publishing by default
Remote (10 MiB/20 files) or local stdio (50 MiB/100 files) transport
Capabilities & Tool Schemas
Inspect callable tools, capabilities, and parameters exposed to AI agents by Tempmd MCP.
Extracted Tool Capabilities
One stable, canonical URL per artifact that updates in place
Supports HTML, Markdown, CSV, and Mermaid artifacts
7-day active window that resets on update; 7-day restore grace period after expiry
No account or API key required — anonymous publishing by default
Remote (10 MiB/20 files) or local stdio (50 MiB/100 files) transport
Documentation Overview
@tempmd/mcp
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 <tempmd_key_...>.
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.
Configuration
| Env var | Default | Purpose |
|---|---|---|
TEMPMD_API_URL | https://api.temp.md | Point at a different API (e.g. local dev http://localhost:8787) |
Development
This repo mirrors the packages/mcp package from the temp.md monorepo, where development happens. Issues and feature requests are welcome here.
Semantics agents should preserve
- The canonical URL is the only link to share — never surface version-specific links.
- A failed update never breaks the live link; the last successful version keeps serving.
- Prefer
update_tempoverpublish_tempwhen the project already has a Temp for the artifact.
Related MCP Servers
Reviews
No reviews yet — be the first to share how this listing worked for you.
Frequently Asked Questions about Tempmd MCP
AllMCPs Directory Badge
Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.
Badge Style:
Live Dynamic SVG Preview
Markdown (GitHub README)
[](https://allmcps.com/mcp/huangdun-tempmd-mcp)HTML Embed
<a href="https://allmcps.com/mcp/huangdun-tempmd-mcp"><img src="https://allmcps.com/api/badge/huangdun-tempmd-mcp?style=directory" alt="Tempmd MCP on AllMCPs" /></a>