Postbag MCP server
{
"mcpServers": {
"postbag": {
"command": "npx",
"args": [
"-y",
"@postbag/mcp@latest"
]
}
}
}{
"mcpServers": {
"postbag": {
"command": "npx",
"args": [
"-y",
"@postbag/mcp@latest"
]
}
}
}{
"mcpServers": {
"postbag": {
"command": "npx",
"args": [
"-y",
"@postbag/mcp@latest"
]
}
}
}{
"servers": {
"postbag": {
"command": "npx",
"args": [
"-y",
"@postbag/mcp@latest"
]
}
}
}{
"mcpServers": {
"postbag": {
"command": "npx",
"args": [
"-y",
"@postbag/mcp@latest"
]
}
}
}file .mcp.json (in your project root)file claude_desktop_config.jsonfile ~/.cursor/mcp.jsonfile .vscode/mcp.jsonfile ~/.codeium/windsurf/mcp_config.jsoninstall npx -y @postbag/mcpversion 0.1.1
What it does
Postbag is a form backend that accepts HTML form submissions and routes them to multiple destinations like email, Telegram, webhooks, and CRMs. It is built for developers managing multiple sites and for AI agents that build forms, providing a centralized source of truth for form data mapping and delivery.
- Accept form submissions from HTML forms across multiple websites and route them to a single inbox or partner system.
- Map different form fields from multiple sites onto a single standardized data shape for downstream systems.
- Set up conditional delivery rules, such as sending form submissions to specific destinations between certain dates or as daily digests.
Tools this server exposes
| Tool | Does |
|---|---|
| postbag_quickstart | Provides a quickstart guide for getting started with Postbag. |
| postbag_explain | Explains how Postbag works and its core concepts. |
Before you enable it
An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.