Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Receive-only inbox for AI agent sign-ups: one call returns the verification code. Never sends.
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.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Works in Claude on the web, desktop and mobile:
https://mail.zoomfort.com/mcpRun this in your terminal
claude mcp add --transport http mail https://mail.zoomfort.com/mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"mail": {
"url": "https://mail.zoomfort.com/mcp"
}
}
}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": {
"mail": {
"type": "http",
"url": "https://mail.zoomfort.com/mcp"
}
}
}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.
ChatGPT connects only to servers on the internet:
https://mail.zoomfort.com/mcpMenu names can differ slightly by plan and over time.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
We have not read this server’s tool list yet; we check endpoints in rotation.
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 7, 2026
The registry name was verified against the domain zoomfort.com (the registry checks domain ownership)
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Not checked yet; we check endpoints in rotation
Not checked yet; we check endpoints in rotation
Not checked yet; we read the tool list when we check the endpoint
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.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
The GitHub repo last changed –, and the latest version (1.0.0) reached the registry 21 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
In the same category: Spec Driven Development, Remote Desktop Commander, Detailing Manager
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.
Connect your auto detailing studio's tasks, cars, clients and revenue to Claude or ChatGPT.
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.
Receive-only inbox for AI agent sign-ups: one call returns the verification code. Never sends.
zoomfort gives an AI agent its own email address. The agent signs up for a service with that address, then asks zoomfort for the verification code or link. zoomfort only receives mail: it cannot send, reply or forward, and it never opens or follows links in mail.
This repository holds the public description of the hosted MCP server: this README, the registry file server.json and an agent usage file, skills/zoomfort/SKILL.md. The server itself runs at https://mail.zoomfort.com/mcp; there is nothing to install or self-host.
Create a free account at https://zoomfort.com/app/signup. New accounts open every day; when the day's places are taken, register interest at https://zoomfort.com/#invite or email hello@zoomfort.com and we will send you an invite. Once your account exists, sign in at https://mail.zoomfort.com/app and create an address, such as signup@yourname.zoomfort.com. Mail to an address you have not created is refused.
Four read-only tools, each marked readOnlyHint: true:
| Tool | What it does | Permission |
|---|---|---|
get_addresses | Lists the inbox addresses your credential can reach. | any valid credential |
wait_for_code | Waits up to 25 seconds for a verification code from a sender that passed the sender check. | read:codes |
wait_for_link | Waits up to 25 seconds for a verification link from a sender that passed the sender check. Returns the link; zoomfort never opens it. | read:codes |
list_recent_mail | Lists recent mail summaries, newest first. Quarantine is left out unless asked for. | read:mailbox |
The tools cannot send, delete, move or mark mail, and do not return raw mail, headers or attachment content.
Endpoint: https://mail.zoomfort.com/mcp, Streamable HTTP, POST only. Use this exact path: /mcp/ with a trailing slash does not work.
Claude (OAuth). Open Settings › Connectors › Add custom connector, enter https://mail.zoomfort.com/mcp and approve the connection on zoomfort. You choose which addresses it can read and whether it can read codes, mail or both. A connection counts as one of your keys, expires after 90 days without use, and can be disconnected any time in Settings › API keys.
Other clients (API key). In zoomfort, open Settings › API keys › Create key, give it read:codes (add read:mailbox if the agent should list mail) and only the addresses it needs. The full key is shown once. Keep it in the environment as ZOOMFORT_API_KEY and send it as Authorization: Bearer . Never put the key in a URL or in tool arguments.
Cursor, .cursor/mcp.json:
{
"mcpServers": { "zoomfort": { "url": "https://mail.zoomfort.com/mcp", "headers": { "Authorization": "Bearer ${env:ZOOMFORT_API_KEY}" } } } }
Claude Code, .mcp.json:
{
"mcpServers": { "zoomfort": { "type": "http", "url": "https://mail.zoomfort.com/mcp", "headers": { "Authorization": "Bearer ${ZOOMFORT_API_KEY}" } } } }
Codex, ~/.codex/config.toml:
[mcp_servers.zoomfort]
url = "https://mail.zoomfort.com/mcp" bearer_token_env_var = "ZOOMFORT_API_KEY"
These client examples follow each vendor's documentation and have not all been tested end to end.
The same lookups are plain HTTPS calls with the same key:
curl --get 'https://mail.zoomfort.com/api/v1/code' \
-H "Authorization: Bearer $ZOOMFORT_API_KEY" \ --data-urlencode 'to=signup@yourname.zoomfort.com' \ --data-urlencode 'from_domain=service.example' \ --data-urlencode 'since=2026-10-17T08:00:00Z' \ --data-urlencode 'wait=25'
/api/v1/link returns a verification link the same way. OAuth connections work only at /mcp, not in the REST API. Full reference: https://zoomfort.com/docs
since, so an older code is never picked up.from_domain, the domain of the service you expect mail from.link_host, sender and subject before following a link.The agent usage file skills/zoomfort/SKILL.md spells this out for Claude Code, Cursor, Codex and OpenClaw.
The usage file is also packaged as a Claude Code plugin, so an agent can load it without reading these docs:
/plugin install zoomfort --marketplace chronicle-digital-solutions-ltd/zoomfort-mcp
The plugin holds only the skill. Connect the MCP server or set ZOOMFORT_API_KEY as described above.
All keys and connected apps of one account share 120 requests a minute and 20 waiting calls a minute (the waiting calls are wait_for_code, wait_for_link and REST calls that wait), so more keys do not raise them. On Free, ordinary mail is kept 7 days. Plans and limits: https://zoomfort.com/docs#limits
hello@zoomfort.com