tempmd-mcp
The tempmd-mcp server lets you publish HTML, Markdown, CSV, or Mermaid artifacts to stable public URLs on temp.md and manage their full lifecycle — no account required.
Publish a new artifact (
publish_temp): Upload a file and receive a stable, shareable URL (e.g.amber-hill-9eb6.temp.md); credentials are auto-saved to a local.tempmdfile. Extra files (scripts, styles, images) can be bundled with the main artifact.Update an existing artifact (
update_temp): Push a new version behind the same URL without re-sharing; resets the 7-day active window.Check artifact status (
get_temp_status): Inspect a Temp's lifecycle state (active, cooling, or expired), its expiry time, and restore eligibility.Restore an expired artifact (
restore_temp): Reactivate a recently expired Temp at its original URL within 7 days of expiry.Freeze a snapshot (
snapshot_temp): Lock the current version as a fixed-reference snapshot with its own URL for sign-offs or approvals, while the canonical link continues serving the latest version.Toggle comments (
set_comments): Enable or disable visitor comments on a published Temp's page.List project Temps (
list_temps): View all Temp records (IDs, URLs, tokens, expiry) stored in the local.tempmdfile without a network call.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@tempmd-mcppublish this HTML page to temp.md"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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
claude mcp add --transport http tempmd https://api.temp.md/mcpRemote 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
claude mcp add tempmd -- npx -y tempmd-mcpCursor / Windsurf / any MCP client — add to your MCP config:
{
"mcpServers": {
"tempmd": {
"command": "npx",
"args": ["-y", "tempmd-mcp"]
}
}
}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.
Related MCP server: stacktree-mcp
Tools
Tool | Local stdio | Remote | What it does |
| ✓ | ✓ | Publish a new artifact and get a stable public URL |
| ✓ | ✓ | Push a new version behind the same URL |
| ✓ | ✓ | Check lifecycle and restore eligibility |
| ✓ | ✓ | Bring a recently expired Temp back at the same URL |
| ✓ | ✓ | Freeze the current version as a fixed reference |
| ✓ | ✓ | Toggle pinned visitor comments |
| ✓ | ✓ | List local project records or account-owned Temps |
| — | ✓ | 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 |
|
| Point at a different API (e.g. local dev |
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.
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- AlicenseAqualityDmaintenanceEnables users to upload files and generate tracked, shareable links directly from AI agents like Claude Desktop or Cursor. It supports publishing various file formats including text, PDFs, and images, while providing tools for artifact management and analytics.Last updated862MIT
- Alicense-qualityCmaintenanceEnables publishing and managing HTML artifacts on stacktr.ee directly from MCP clients like Claude Desktop.Last updated69MIT
- Alicense-qualityBmaintenanceEnables publishing and updating Claude artifacts or HTML to private, access-controlled links directly from Claude.Last updated1AGPL 3.0
- Flicense-qualityCmaintenanceEnables publishing, updating, and sharing HTML artifacts with strict security isolation (origin separation, CSP, API keys) via MCP tools.Last updated1
Related MCP Connectors
Publish HTML, files, or a URL to a permanent public URL, then update it — from any MCP agent.
Publish HTML, Markdown, PDF, or images as instant shareable links with expiry and passwords.
Publish AI-generated HTML & Markdown to a hosted, shareable URL via MCP.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/huangdun/tempmd-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server