Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Form backend that routes: one tool per Postbag API operation, plus quickstart and explain.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
POSTBAG_API_KEY, POSTBAG_API_URLValues marked secret are keys to your account. Never share them or paste them into a chat.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"postbag": {
"command": "npx",
"args": [
"-y",
"@postbag/mcp"
],
"env": {
"POSTBAG_API_KEY": "your-value",
"POSTBAG_API_URL": "your-value"
}
}
}
}Run this in your terminal
claude mcp add postbag --env POSTBAG_API_KEY=your-value --env POSTBAG_API_URL=your-value -- npx -y @postbag/mcpFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"postbag": {
"command": "npx",
"args": [
"-y",
"@postbag/mcp"
],
"env": {
"POSTBAG_API_KEY": "your-value",
"POSTBAG_API_URL": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"postbag": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@postbag/mcp"
],
"env": {
"POSTBAG_API_KEY": "your-value",
"POSTBAG_API_URL": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
POSTBAG_API_URL envThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026
The registry name was verified against the domain postbag.dev (the registry checks domain ownership)
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: POSTBAG_API_KEY
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.1.1) reached the registry 3 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, zanadir
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
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.
Find what a repository's CI is missing, and which security checks cannot fail the build.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
A form backend that routes. Point any HTML form at a Postbag endpoint and it lands in your inbox — then goes wherever it should: email, Telegram, a webhook, a partner, your CRM. Built for people who run many sites, and for the AI agents that build them.
<form action="https://api.postbag.dev/s/fm_8f3kq2" method="POST">
Send
That's the whole integration for one form. Everything else — grouping forty forms into one stream, mapping their different fields onto one shape, sending that shape to a partner between two dates, a daily digest, never losing a submission — is there when you need it and invisible when you don't.
New here (human or AI agent)? Read [`CLAUDE.md`](./CLAUDE.md) first.
Every website has forms. Every form needs somewhere to go. Formspree and friends solve "somewhere" for one site; they fall over when you have fifteen sites feeding one partner with fifteen slightly different forms. Postbag is the source of truth for what each form collects, what each downstream system receives, and the versioned contract between them.
The database makes it correct; events make it fast.
A submission is accepted the instant it is a row. Delivery is a durable outbox that a worker drains with retries. Realtime nudges are an accelerator, never a transport. If every event stream in the system died, every submission would still arrive — late, never lost. (Inherited from the lead pipeline this generalises; see docs/ARCHITECTURE.md.)
Phase 1 — MVP live at postbag.dev (site, docs, dashboard at /app, API at /v1). See PROGRESS.md for the live blueprint and docs/ROADMAP.md for phases.
Start at docs/README.md.
The server, dashboard, site and domain packages (apps/*, packages/core, packages/db, packages/auth) are licensed under AGPL-3.0. The client packages that run inside your own code — @postbag/sdk, the postbag CLI and @postbag/mcp — are MIT. Rationale in ADR-006.