Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
End-to-end encrypted inbox where AI agents deliver files and request human approval.
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.
ARELAY_TOKEN, ARELAY_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": {
"arelay": {
"command": "npx",
"args": [
"-y",
"@arelay/cli",
"mcp"
],
"env": {
"ARELAY_TOKEN": "your-value",
"ARELAY_URL": "your-value"
}
}
}
}Run this in your terminal
claude mcp add arelay --env ARELAY_TOKEN=your-value --env ARELAY_URL=your-value -- npx -y @arelay/cli mcpFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"arelay": {
"command": "npx",
"args": [
"-y",
"@arelay/cli",
"mcp"
],
"env": {
"ARELAY_TOKEN": "your-value",
"ARELAY_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": {
"arelay": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@arelay/cli",
"mcp"
],
"env": {
"ARELAY_TOKEN": "your-value",
"ARELAY_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.
ARELAY_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 7, 2026
The registry name was verified with the GitHub account mmmikael, which owns the repo
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: ARELAY_TOKEN
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.2.0) 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, OpenTakeoff
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.
Construction takeoff for AI agents: load plans, set scale, measure, count, export with provenance.
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.
Agent Relay is where your AI agents ask permission. Agents draft emails, request spend, and deliver finished work into a private, end-to-end encrypted inbox; nothing leaves, sends, or charges until you approve it. Anything that can make HTTP requests can use it — Cursor, Codex, Claude Code, cron jobs, webhooks, or your own backend — and it is open source under MIT, so you can run it yourself.
An optional Email Review Relay plugin adds a human-in-the-loop outbound email path: agents submit encrypted drafts, you preview them in the same inbox, then approve or reject before anything is sent. It is enabled on arelay.app; self-hosters can turn it on with EMAIL_REVIEW_RELAY_ENABLED=true (setup).
Two ways to use it:
The hosted service at arelay.app handles deployment, database, storage, backups, TLS, and updates. The security model is the same as self-hosting: encrypted deliveries are decrypted in your browser, not on the server. The one exception is approving an email draft: the decrypted email is sent to the server in that request so it can be delivered, and is never stored as plaintext. Email itself is not end-to-end encrypted, so the recipient's mail provider sees the same content permanently.
Sign-in uses passkeys (WebAuthn), not passwords or social login. No Google, Apple, or Microsoft account is required. If terms or privacy are updated later, existing accounts are prompted to accept the new versions before continuing.
Agent Relay is agent-agnostic: any client that speaks HTTP and follows the E2EE envelope format can deliver. Pick the path that fits your setup:
| Integration path | Best for |
|---|---|
| CLI & MCP server | Fastest start: one command from any shell, or native MCP tools in Claude Code, Cursor, and Claude Desktop |
| Agent skill | Cursor, Codex, Claude Code, Hermes Agent, and other Agent Skills hosts |
| Direct HTTP API | Custom scripts, backends, webhooks, scheduled jobs |
| Platform plugins | Platform-specific hooks, e.g. Hermes cron delivery |
Whichever path you choose, set these where your agent runs — never commit tokens:
| Variable | Value for arelay.app |
|---|---|
ARELAY_URL | https://arelay.app |
ARELAY_TOKEN | Token from Account → Agent tokens |
Every request uses Authorization: Bearer .
The @arelay/cli npm package wraps the API and all envelope encryption. Deliver from any shell:
export ARELAY_TOKEN=ar_... # from Account → Agent tokens
npx -y @arelay/cli send report.md --title "Q2 revenue report"
Or register it as an MCP server so agents can deliver work natively (deliver_to_inbox, list_inbox_sessions, submit_email_draft tools):
# Claude Code
claude mcp add arelay --env ARELAY_TOKEN=ar_... -- npx -y @arelay/cli mcp
npx -y @arelay/cli check verifies the token and encryption setup. The package also exports a typed SDK (import { ArelayClient } from '@arelay/cli') — see its README. Self-hosters point it at their deployment with ARELAY_URL.
Install the agent-relay skill (requires portal E2EE setup):
npx skills add mmmikael/arelay-skills --skill agent-relay -g -y
Hermes Agent:
hermes skills tap add mmmikael/arelay-skills
hermes skills install mmmikael/arelay-skills/agent-relay
Anything that can POST JSON can deliver: fetch the public key from GET /api/agent/e2ee/config, encrypt locally, create a session, and upload artifacts. See the API reference and the bundled Node reference scripts in the skill for working encryption code.
Hermes cron (--deliver arelay) needs arelay-hermes-plugin. Cron runs in the gateway, not the interactive CLI — put credentials in ~/.hermes/.env (including AGENT_RELAY_HOME_CHANNEL=https://arelay.app), install the plugin, then restart the gateway:
hermes plugins install mmmikael/arelay-hermes-plugin --enable
hermes gateway start /cron add "0 9 * * *" "Your prompt. Never use [SILENT]." --deliver arelay
All agent deliveries must be end-to-end encrypted. Complete Set up encryption during Get started; unlock in the browser when viewing the inbox. Agents fetch your public key from GET /api/agent/e2ee/config and upload encrypted sessions and artifacts. Plaintext agent payloads return 400 (plaintext_not_allowed); unconfigured accounts get 428 (e2ee_required).
On arelay.app, agents POST encrypted email drafts; each appears as an inbox session you Approve (send via your Cloudflare credentials) or Reject.
API details and self-host setup: Plugins.
Run Agent Relay on your own PostgreSQL and S3-compatible storage. Useful when you need full data residency control or a private deployment.
npm install
cp .env.example .env npm run db:migrate:local npm run dev
Open http://127.0.0.1:5173 and create an account with a passkey. Without Cloudflare or SMTP configured, verification codes are printed to the server console.
Database schema changes are managed with Drizzle migrations. Edit the Drizzle schema, generate a migration with npm run db:generate, review the generated SQL, then apply it with npm run db:migrate:local.
Run unit tests:
npm test
To test migrations against a disposable empty database, set TEST_DATABASE_URL and run:
npm run db:smoke
| Variable | Description |
|---|---|
SESSION_SECRET | Secret for signing human session cookies. Generate with openssl rand -hex 32. |
SESSION_VERSION | Bump this to invalidate existing human sessions. |
ORIGIN | Public site URL for CSRF checks and absolute links. In production, set to your canonical URL, for example https://arelay.app. |
WEBAUTHN_RP_NAME | Passkey relying party display name. Defaults to Agent Relay. |
WEBAUTHN_RP_ID | Passkey relying party ID. For production on arelay.app, use arelay.app. |
WEBAUTHN_ORIGIN | Expected passkey origin, for example https://arelay.app. |
| DATABASE_URL | PostgreSQL connection string.
Only the beginning is shown; read the rest in the repo