Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
作者提供的说明(英文原文)
Send real, printed letters by post across Europe. Requires a free account; quote before sending.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
适用于网页版、桌面版和手机版 Claude:
https://sendletter.eu/api/mcp在终端中运行这条命令
claude mcp add --transport http sendletter https://sendletter.eu/api/mcp粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"sendletter": {
"url": "https://sendletter.eu/api/mcp"
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"sendletter": {
"type": "http",
"url": "https://sendletter.eu/api/mcp"
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
ChatGPT 只能连接互联网上的服务器:
https://sendletter.eu/api/mcp菜单名称可能因套餐和版本不同而略有差异。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
我们还没有读取这个服务器的工具列表;我们会轮流检查各个端点。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日
注册名称已通过域名 sendletter.eu 验证(注册中心会核实域名所有权)
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
尚未检查;我们会轮流检查各个端点
尚未检查;我们会轮流检查各个端点
尚未检查;我们会在检查端点时读取工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。
GitHub 仓库最后更新于–,最新版本(1.0.0)于3个月前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,所以接受远程 MCP 服务器的应用也可以使用,例如开启开发者模式的 ChatGPT。
同一分类中有:Spec Driven Development, Remote Desktop Commander, Systemdox
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ 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.
Your architecture in your agents' context: checks, specs, ADRs and docs over MCP, at write time.
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
Send a real letter — printed, folded, franked and handed to the post — from Node.
npm install sendletter
import { SendLetter } from 'sendletter'
const sendletter = new SendLetter(process.env.SENDLETTER_API_KEY!)
const input = { idempotencyKey: 'invoice-2026-0042-reminder-1', sender: { company: 'Twilper', name: 'Gert Snijder', street: 'Merelstraat', number: '64', postalCode: '8916 AX', city: 'Leeuwarden', country: 'NL', }, recipient: { name: 'Jan de Vries', street: 'Keizersgracht', number: '123', postalCode: '1015 CJ', city: 'Amsterdam', country: 'NL', }, text: 'Beste heer De Vries,\n\nBijgaand de herinnering voor factuur 2026-0042.', }
const prepared = await sendletter.prepare(input) console.log(prepared.id, prepared.pages, prepared.totalCents) const pdf = await sendletter.download(prepared.id)
Show the PDF and exact total to the user. After approval, use the same input and key:
const letter = await sendletter.send({ ...input, expectedTotalCents: prepared.totalCents })
console.log(letter.id, letter.status, letter.totalCents)
Get a key at sendletter.eu. Keys starting sk_test_ post nothing, charge nothing, and still run the whole status chain, so you can build against the real thing.
Give the content exactly one way: text, document (rich text), file (base64) or fileUrl. Two is refused rather than guessed at, because the wrong document in a postbox cannot be recalled.
// An invoice you already have as a PDF.
await sendletter.send({ sender, recipient, file: { name: 'invoice.pdf', contentBase64: pdf.toString('base64') }, product: 'registered', // 'standard' | 'priority' | 'registered' colour: true, idempotencyKey: invoice-${invoice.id}, })
Send an `idempotencyKey` on anything that can be retried. A repeat with the same key returns the original letter instead of a second envelope. That single field is what makes a retry after a network timeout safe, and a timeout says nothing about whether the letter was accepted.
await sendletter.get(id) // one letter
await sendletter.list({ status: 'posted' }) // one page await sendletter.cancel(id, 'order withdrawn') // while it is still cancellable await sendletter.download(id) // the PDF as printed await sendletter.download(id, { proof: true }) // proof of posting
for await (const letter of sendletter.all({ mode: 'live' })) { // walks every page; you never hold the cursor }
Every paid live letter receives its invoice number at payment time. Test letters never consume the statutory series. A full refund keeps that invoice and adds a separately numbered negative credit note.
const page = await sendletter.listInvoices()
await writeFile('invoice.pdf', await sendletter.downloadInvoice(page.data[0].id))
if (page.data[0].creditNote) { await writeFile( 'credit-note.pdf', await sendletter.downloadCreditNote(page.data[0].creditNote.id), ) }
const check = await sendletter.validateAddress(recipient)
if (!check.valid) console.log(check.problems) // answers, does not throw
const quote = await sendletter.quote({ destination: 'DE', pages: 3 })
validateAddress returns a bad address rather than throwing: a wrong postcode is the successful outcome of asking. supported: false is the one that cannot be fixed by editing the address — we do not carry to that country.
Everything the API refuses becomes a SendLetterError with a code to branch on.
import { SendLetterError } from 'sendletter'
try { await sendletter.send({ sender, recipient, text }) } catch (error) { if (!(error instanceof SendLetterError)) throw error
if (error.code === 'insufficient_balance') { // Put this in front of the customer; the wallet is short, nothing else. return redirect(error.topUpUrl!) } if (error.isRetryable) { await sleep((error.retryAfter ?? 5) * 1000) } }
isRetryable covers 429 and 5xx. Nothing else should be retried: a 400 means the letter will be refused just as firmly the second time.
Status changes arrive as a POST to the URL you registered. Verify them. Without that, anyone who learns your endpoint can tell your system a letter was delivered.
import { verifyWebhook, SendLetterError } from 'sendletter'
export async function POST(request: Request) { const rawBody = await request.text() // the raw text, not the parsed object
let event try { event = verifyWebhook({ rawBody, signature: request.headers.get('x-sendletter-signature'), secret: process.env.SENDLETTER_WEBHOOK_SECRET!, }) } catch (error) { if (error instanceof SendLetterError) return new Response('nope', { status: 400 }) throw error }
if (await alreadyHandled(event.id)) return new Response('ok') // see below await handle(event) // letter.posted, ... return new Response('ok') }
Two things this shape gets right and hand-rolled verification usually does not:
JSON.stringify does not promise to reproduce them. Read the body as text, verify, then parse.letter.posted handled twice should not bill a customer twice.Events: letter.submitted, letter.printed, letter.posted, letter.delivered, letter.failed, letter.refunded.
A sk_test_ key runs the full chain — submitted → printed → posted → delivered — with webhooks firing exactly as they will in production, while touching no wallet and no printer. client.isTestMode tells you which kind of key you are holding, which is worth asserting in a deploy check: the two look alike in a log and only one of them costs money.
sendletter.eu/en/developers · OpenAPI at /api/v1/openapi.json · MIT