Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Create Elaan notification types, templates and brands, trigger sends, and debug delivery.
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.
ELAAN_API_KEYValues 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": {
"elaan": {
"command": "npx",
"args": [
"-y",
"@elaanio/mcp"
],
"env": {
"ELAAN_API_KEY": "your-value"
}
}
}
}Run this in your terminal
claude mcp add elaan --env ELAAN_API_KEY=your-value -- npx -y @elaanio/mcpFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"elaan": {
"command": "npx",
"args": [
"-y",
"@elaanio/mcp"
],
"env": {
"ELAAN_API_KEY": "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": {
"elaan": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@elaanio/mcp"
],
"env": {
"ELAAN_API_KEY": "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.
These 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 against the domain elaan.io (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: ELAAN_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.3) 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, EmbeddedCI BenchPod
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.
Drive a BenchPod hardware-in-the-loop bench: power, flash, UART, I2C, CAN, analog and logic.
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 Model Context Protocol server for Elaan, so the tedious half of a notification integration happens in your editor instead of by hand in a console: creating notification types, writing templates for three channels, setting up per-tenant brands, and working out why a message did not arrive.
Documentation: elaan.io/docs.html
Create a service key (sk_…) in the console, then add the server to your assistant's MCP config. Nothing to install — npx fetches it on first run.
Claude Code — .mcp.json in your project, or ~/.claude.json for every project:
{
"mcpServers": { "elaan": { "command": "npx", "args": ["-y", "@elaanio/mcp"], "env": { "ELAAN_API_KEY": "sk_..." } } } }
Cursor — the same block in .cursor/mcp.json. Most other MCP clients take the same shape.
Self-hosting Elaan? Point it at your own install:
"env": {
"ELAAN_API_KEY": "sk_...", "ELAAN_API_BASE": "https://elaan.internal.example.com/v1" }
| Area | Tools |
|---|---|
| Notification types | list, get, create, update (channel defaults, variables, opt-out policy), delete, restore |
| Templates | list, get, create, update, delete across email / inbox / push; preview an email render; report templates affected by a type's variables |
| Brands | list, create, update (values and sender), delete |
| Contacts | list, get, create, read and set preferences |
| Sending | trigger a notification to 1–100 recipients |
| Debugging | event status with per-channel outcomes, the delivery log with filters, aggregate stats |
Ask for what you want and let it do the fan-out:
Create an
order_shippedtype that goes to email and the inbox, with anorder_idvariable, then
write both templates using our
acmebrand.
A customer says they never got their shipping email. Event id is
01J…— what happened?
Transport credentials. /v1/email-transport and /v1/push-transport are not exposed at all. They hold SMTP passwords and FCM service accounts, and an agent has no business reading or rotating them. Configure those in the console.
See your API key. It is read from the environment, never accepted as a tool argument, because arguments are model-visible and end up in transcripts.
Note that delete_template is a hard delete with no restore, while delete_notification_type is soft and reversible with restore_notification_type. trigger_notification sends real messages.
pnpm install
pnpm --filter @elaanio/mcp build pnpm --filter @elaanio/mcp test # spawns the server, speaks JSON-RPC to a stub API
The test drives the real binary over stdio rather than importing the source, which is how it caught a zod v4 behaviour that made every create_notification_type call fail before it left the process.
MIT