Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Operate an Enoch control plane through MCP tools
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.
ENOCH_API_URL, ENOCH_API_TOKENValues 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": {
"enoch": {
"command": "uvx",
"args": [
"enoch-mcp"
],
"env": {
"ENOCH_API_URL": "your-value",
"ENOCH_API_TOKEN": "your-value"
}
}
}
}Run this in your terminal
claude mcp add enoch --env ENOCH_API_URL=your-value --env ENOCH_API_TOKEN=your-value -- uvx enoch-mcpFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"enoch": {
"command": "uvx",
"args": [
"enoch-mcp"
],
"env": {
"ENOCH_API_URL": "your-value",
"ENOCH_API_TOKEN": "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": {
"enoch": {
"type": "stdio",
"command": "uvx",
"args": [
"enoch-mcp"
],
"env": {
"ENOCH_API_URL": "your-value",
"ENOCH_API_TOKEN": "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.
ENOCH_API_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 6, 2026
The registry name was verified with the GitHub account alias8818, 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: ENOCH_API_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.1.1) reached the registry 6 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, Zoo 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.
An MCP server that provides access to the Zoo API for various CAD operations and tools.
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.
`enoch-mcp` is a local Model Context Protocol stdio server for a configured Enoch FastAPI control-plane API. It lets MCP clients inspect and operate Enoch through typed tools without exposing a raw shell or reimplementing Enoch business logic.
Enoch system repo · Docs · MCP
Authorization: Bearer to API requests using the configured token.http://localhost:8787Run from PyPI with uvx:
uvx enoch-mcp --api-url http://localhost:8787 --api-token '<token>'
Or configure with environment variables:
export ENOCH_API_URL='http://localhost:8787'
export ENOCH_API_TOKEN=' ' uvx enoch-mcp
For local development from a checkout:
git clone https://github.com/alias8818/enoch-mcp.git
cd enoch-mcp uv sync --dev uv run enoch-mcp --api-url http://localhost:8787 --api-token ' '
| Option | Environment variable | Default | Description |
|---|---|---|---|
--api-url | ENOCH_API_URL | http://localhost:8787 | Base URL for the Enoch API. |
--api-token | ENOCH_API_TOKEN | none | Bearer token for the Enoch API. |
--worker-probes-json | ENOCH_WORKER_PROBES_JSON | none | Optional JSON map for direct worker diagnostics. |
--worker-probes-file | ENOCH_WORKER_PROBES_FILE | none | Optional path to a JSON map for direct worker diagnostics. |
The token is required. If it is missing, tool calls fail before making an HTTP request.
Worker probes are disabled unless ENOCH_WORKER_PROBES_JSON or ENOCH_WORKER_PROBES_FILE is configured. This keeps the default package a thin control-plane bridge. When configured, the MCP exposes named diagnostics for worker truth: API health, worker-gate dashboard status, active process markers, bounded log tails, disk space, and expected artifact presence.
Example:
{
"cpu": { "api_url": "http://127.0.0.1:18788", "api_token": "worker-api-token", "service_name": "enoch-control-plane", "project_root": "/srv/enoch/projects" }, "gpu": { "api_url": "http://127.0.0.1:18789", "api_token": "worker-api-token", "ssh_host": "worker-gpu.example.internal", "ssh_user": "enoch", "service_name": "enoch-control-plane", "project_root": "/srv/enoch/projects", "log_paths": ["/var/log/enoch-control-plane.log"] } }
Supported fields per lane:
api_url: worker-gate base URL. Used first for /healthz, /dashboard/api, /dashboard/api/run/{run_id}, and /project-status/{project_id}.api_token: worker bearer token. Treated as secret.ssh_host, ssh_user, ssh_port: optional SSH fallback/debug target.service_name: systemd unit name for service checks and journal tails.project_root, state_dir: fixed worker roots used for disk and artifact checks.log_paths: fixed worker-gate log paths that may be tailed.SSH probes only run fixed diagnostic commands. They do not accept arbitrary shell input from the MCP client. User-supplied IDs are limited to safe run/project identifier characters, log output is bounded, SSH uses batch mode and no stdin, and the recommended deployment is a read-only worker user or forced-command policy.
{
"mcpServers": { "enoch": { "command": "uvx", "args": ["enoch-mcp"], "env": { "ENOCH_API_URL": "http://localhost:8787", "ENOCH_API_TOKEN": "replace-with-token" } } } }
For local development, point the MCP client at the checkout:
{
"mcpServers": { "enoch": { "command": "uv", "args": ["--directory", "/path/to/enoch-mcp", "run", "enoch-mcp"], "env": { "ENOCH_API_URL": "http://localhost:8787", "ENOCH_API_TOKEN": "replace-with-token" } } } }
Use the equivalent local stdio-server settings for Cursor, Copilot, Windsurf, or other MCP clients.
uv sync --dev
uv run pytest -q gitleaks detect --no-git --redact
This package is public. Examples must use placeholders and local URLs only. Do not publish private hostnames, LAN/Tailscale IPs, operator paths, or live tokens.