Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
A real inbox for agents: read mail, draft replies you approve, wait for verification codes.
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://mcp.mailly.site/mcpRun this in your terminal
claude mcp add --transport http mailly https://mcp.mailly.site/mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"mailly": {
"url": "https://mcp.mailly.site/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": {
"mailly": {
"type": "http",
"url": "https://mcp.mailly.site/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://mcp.mailly.site/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 mailly.site (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 (0.3.1) 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, Agent Data Tools: Utilities
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.
103 tools: JSON repair, CSV, hashes, cron, dates, units, validators. 25 free calls.
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.
The MCP server behind Mailly's connector, plus the Mailly plugin for Claude and Codex.
src/: the MCP server, a Cloudflare Worker. It offers typed tools for Mailly mail, drafts, sending, domains, contacts, templates, campaigns, workflows and webhooks. Every tool calls the Mailly REST API with the caller's Mailly API key, so authentication, billing and workspace isolation all stay in the API.ui/: the MCP Apps UI (email and draft cards), bundled into ui:// resources. It is off unless MCP_APPS=1.plugins/mailly: the plugin for Claude (claude.ai, Cowork and Claude Code) and Codex. It points at the hosted server and adds a skill for working with email safely.plugins/openai/mailly: the public ChatGPT/Codex update package, based on the published 0.3.1 release, with its existing listing, review cases, demo link, skill, and PNG icon retained.Add https://mcp.mailly.site/mcp as a remote MCP server and sign in with your Mailly account (OAuth). In ChatGPT, add the published Mailly plugin. In Claude Code you can install the plugin instead:
/plugin install mailly --marketplace superagents-lab/mailly-mcp
This server is an OAuth protected resource. Mailly's API (https://api.mailly.site/api/auth) is the authorization server: clients find it through /.well-known/oauth-protected-resource, sign the user in there, and send the access token here. The server passes the token, or an API key, unchanged to Mailly's REST API, which checks it and the scopes it carries. The tool list is narrowed to the same scopes (GET /me).
The public OpenAI configuration in plugins/openai/mailly/mcp.json and the Codex compatibility configuration in plugins/mailly/.codex-plugin/mcp.json request offline_access in extensions.com.openai.auth.baseScopes. Mailly issues a refresh token only when that scope is granted. Resource discovery and tool scopes describe Mailly data permissions; they do not request offline access on the client's behalf. Without it, sign-in succeeds but access ends when the one-hour access token expires.
For a published OpenAI plugin, upload the updated plugin package to the existing plugin, confirm that the saved MCP authentication settings include offline_access, then reconnect the account and rescan. Deploying the Worker alone does not update those saved settings. Reconnecting with the old settings will still produce a connection without a refresh token. For manually configured clients, include offline_access alongside the desired Mailly scopes when starting OAuth authorization.
Package the contents of plugins/openai/mailly as the upload root. Do not include the repository, marketplace, or the installed plugin's Portal-generated .app.json and apps binding in a public upload. Keep those generated bindings in the installed release; the submission portal owns them. The package version is 0.3.2. Separately, the Worker declares all three tool annotation booleans explicitly, including destructiveHint: false for read-only tools; that server update requires a Worker deployment and rescan. The MCP Registry listing is unchanged.
npm install
npm run dev # wrangler dev on http://localhost:8787/mcp
Call /mcp with Authorization: Bearer (from https://mailly.site/app/developers). Without the MAILLY_API service binding it calls MAILLY_API_URL (default https://api.mailly.site) over the internet. To host your own copy, change the mcp.mailly.site route in wrangler.jsonc. OAuth sign-in only works at https://mcp.mailly.site/mcp, because Mailly issues tokens for that resource; elsewhere use an API key.
npm run typecheck
npm test # builds dist/worker.js and runs it in Miniflare against a stub API
The Mailly server repository runs its OAuth and end-to-end tests against dist/worker.js from a sibling checkout of this repository.
server.json is the listing in the MCP Registry as site.mailly/mcp. The site.mailly namespace is proven by a DNS TXT record on mailly.site, so publish with mcp-publisher login dns --domain mailly.site --private-key and mcp-publisher publish from a machine that holds the key. Bump version for each release.
MIT