Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Set up and run an Epeaky den on a server you already have, over your own SSH.
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.
EPEAKY_HOST_SSHYou 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": {
"epeaky-host": {
"command": "npx",
"args": [
"-y",
"epeaky-host-mcp"
],
"env": {
"EPEAKY_HOST_SSH": "your-value"
}
}
}
}Run this in your terminal
claude mcp add epeaky-host --env EPEAKY_HOST_SSH=your-value -- npx -y epeaky-host-mcpFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"epeaky-host": {
"command": "npx",
"args": [
"-y",
"epeaky-host-mcp"
],
"env": {
"EPEAKY_HOST_SSH": "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": {
"epeaky-host": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"epeaky-host-mcp"
],
"env": {
"EPEAKY_HOST_SSH": "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.
EPEAKY_HOST_SSH 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 zyn-io, 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.
The registry does not list a required key, though some servers ask you to sign in on first use.
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.1) reached the registry 21 days 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, Microsoft Exchange Online MCP
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.
Exchange Online admin for MSPs: forwarding audits, EWS posture and offboarding, no PowerShell
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.
Set up and run an Epeaky den on a server you already have, from any MCP client (Claude Desktop, Claude Code, others). It works over your own SSH: it holds no keys, keeps nothing, and never creates, rents or buys a server.
claude mcp add epeaky-host -- npx -y epeaky-host-mcp
or, in any MCP client's config:
{ "command": "npx", "args": ["-y", "epeaky-host-mcp"] }
Your SSH key must already reach the server (ssh user@server works without a password). Node 22 or later.
This is apart from epeaky-mcp on purpose: that one is an agent in a den's rooms; this one has root on the den's server. Give each to an agent knowingly.
| Tool | Changes the server | What it does |
|---|---|---|
host_check | no | the system, memory, disk, sudo, ports 80/443, Docker, whether the domain points at the server (from a public resolver), NAT and the firewall, as what is fine and what to fix |
host_install | yes | Docker if missing, the den and Caddy in /opt/epeaky, a certificate, the firewall's ports; returns the first invite |
host_status | no | owner, members, requests to join, invites |
host_logs | no | the den's last log lines |
host_owner | yes | make a device (m-…, as its page shows it) the owner |
host_invite | yes | one-use invite links |
host_withdraw | yes | withdraw an invite and the pass it let in |
host_approve, host_decline | yes | answer a request to join |
host_setting | yes | change a known setting in /opt/epeaky/.env (backed up first), then restart |
host_update | yes | the latest Epeaky |
Tools that change the server are marked so (readOnlyHint: false), so your client asks you before each call. Invite links come back with an instruction to show them only to you.
user@host), the domain, ids (hex), device names, counts, and each setting by its own rule. ssh hands its command to the server's shell as one string, so this check, not argument lists, is what keeps a value from becoming a command; values are single-quoted as well.DEN_ENTRY, DEN_ROOMS, DEN_DONATE, DEN_DONATE_LABEL, DEN_ISSUER_LABEL, DEN_SCREEN, DEN_SCREEN_BITRATE, DEN_RETENTION_DAYS, DEN_LIMITS, DEN_PUBLIC_IP. Secrets and the domain are never touched.StrictHostKeyChecking=accept-new), as a first manual ssh would after you said yes; a changed key is refused.EPEAKY_HOST_SSH points at another ssh.
npm test
They check the tool list (nothing makes a server; what changes is marked), that bad values never reach ssh, the commands each tool runs, the settings rules, the check's report, and that every epeaky command and setting used exists in the installer and the den.