Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
作者提供的说明(英文原文)
Publish artifacts to one stable public temp.md link that updates in place. No account needed.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
TEMPMD_API_URL, Authorization标为机密的值是你账户的钥匙。千万不要分享给别人,也不要粘贴到聊天里。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
这个地址需要在请求的 header 中放入密钥,而添加连接器的菜单无法设置。请改用 Claude Code、Cursor 或 VS Code。
打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json
{
"mcpServers": {
"tempmd": {
"command": "npx",
"args": [
"-y",
"@tempmd/mcp"
],
"env": {
"TEMPMD_API_URL": "your-value"
}
}
}
}在终端中运行这条命令
claude mcp add --transport http tempmd https://api.temp.md/mcp --header 'Authorization: your-value'claude mcp add tempmd --env TEMPMD_API_URL=your-value -- npx -y @tempmd/mcp运行前请先填写空着的值。
粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"tempmd": {
"url": "https://api.temp.md/mcp",
"headers": {
"Authorization": "your-value"
}
}
}
}粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"tempmd": {
"command": "npx",
"args": [
"-y",
"@tempmd/mcp"
],
"env": {
"TEMPMD_API_URL": "your-value"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"tempmd": {
"type": "http",
"url": "https://api.temp.md/mcp",
"headers": {
"Authorization": "your-value"
}
}
}
}粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"tempmd": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@tempmd/mcp"
],
"env": {
"TEMPMD_API_URL": "your-value"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
这个地址需要在请求的 header 中放入密钥,而添加连接器的菜单无法设置。请改用 Claude Code、Cursor 或 VS Code。
你的选择通过 Cookie 保存在这台设备上,无需账户。
TEMPMD_API_URL envAuthorization 机密 HTTP header这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
我们还没有读取这个服务器的工具列表;我们会轮流检查各个端点。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月6日
注册名称已通过 GitHub 账户 tempmd 验证,该账户拥有此仓库
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
尚未检查;我们会轮流检查各个端点
尚未检查;我们会轮流检查各个端点
尚未检查;我们会在检查端点时读取工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
你需要填写:Authorization
两种方式都可以:安装在你的电脑上,或者连接云端版本。
GitHub 仓库最后更新于–,最新版本(0.4.3)于2个月前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,所以接受远程 MCP 服务器的应用也可以使用,例如开启开发者模式的 ChatGPT。
同一分类中有:Spec Driven Development, Remote Desktop Commander, Whisper
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
One routable IPv6 per AI agent, verifiable from the DNS root. Keyless tools need no signup.
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
@tempmd/mcpMCP 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.
Remote — no install
claude mcp add --transport http tempmd https://api.temp.md/mcp
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
claude mcp add tempmd -- npx -y @tempmd/mcp
Cursor / Windsurf / any MCP client — add to your MCP config:
{
"mcpServers": { "tempmd": { "command": "npx", "args": ["-y", "@tempmd/mcp"] } } }
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.
| 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.
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.
| Env var | Default | Purpose |
|---|---|---|
TEMPMD_API_URL | https://api.temp.md | Point at a different API (e.g. local dev http://localhost:8787) |
This repo mirrors the packages/mcp package from the temp.md monorepo, where development happens. Issues and feature requests are welcome here.
update_temp over publish_temp when the project already has a Temp for the artifact.