Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Beschreibung vom Entwickler (englisches Original)
Local-first evidence tracking, formal logic checks and prerequisite planning for AI agents.
Diese drei werden nie zu einer Punktzahl zusammengefasst: Meinungen, Messungen und Beliebtheit sind verschiedene Dinge.
Für diesen Server haben wir noch keine Zusammenfassung in einfacher Sprache geschrieben. Unten stehen die Fakten, die wir aus der Registry gelesen haben.
Wähle die KI-App, die du nutzt, und kopiere die Einstellungen.
Du brauchst
Welche App nutzt du?
Wähle oben deine App. Wir merken sie uns, damit der Button beim nächsten Mal „In … installieren“ anzeigt.
Öffne Claude Desktop → Settings → Developer → Edit Config und füge dies in claude_desktop_config.json ein
{
"mcpServers": {
"noetra": {
"command": "npx",
"args": [
"-y",
"noetra",
"mcp",
"--project",
"your-value"
]
}
}
}Führe das in deinem Terminal aus
claude mcp add noetra -- npx -y noetra mcp --project your-valueDieser Server braucht Werte in seiner Befehlszeile, also kopier die Einstellungen und trag sie ein.
In .cursor/mcp.json in deinem Projekt oder in ~/.cursor/mcp.json einfügen
{
"mcpServers": {
"noetra": {
"command": "npx",
"args": [
"-y",
"noetra",
"mcp",
"--project",
"your-value"
]
}
}
}Dein Browser fragt, ob er die App öffnen darf, dann zeigt die App die Einstellungen und bittet dich um Bestätigung. Schlüsselwerte bleiben leer, damit du sie selbst einträgst.
Dieser Server braucht Werte in seiner Befehlszeile, also kopier die Einstellungen und trag sie ein.
In .vscode/mcp.json in deinem Projekt einfügen
{
"servers": {
"noetra": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"noetra",
"mcp",
"--project",
"your-value"
]
}
}
}Dein Browser fragt, ob er die App öffnen darf, dann zeigt die App die Einstellungen und bittet dich um Bestätigung. Schlüsselwerte bleiben leer, damit du sie selbst einträgst.
Dieser Server läuft auf deinem Computer, und ChatGPT kann sich nur mit Servern im Internet verbinden. Wähle eine andere App.
Deine Auswahl bleibt in einem Cookie auf diesem Gerät; kein Konto nötig.
Diese Einstellungen werden aus dem Registry-Eintrag des Entwicklers erzeugt. Wenn in der README etwas anderes steht, folge der README.
Läuft auf deinem Computer; die Tool-Liste erscheint nach der Installation in deiner KI-App.
Wir prüfen Informationen, die jeder sehen kann; den Code haben wir nicht gelesen. Checks, die nicht zutreffen, werden nicht mitgezählt. · Geprüft am 7. Nov. 2026
Der Registry-Name wurde mit dem GitHub-Konto NOETRA2 bestätigt, dem das Repo gehört
Dieses Repo haben wir noch nicht von GitHub gelesen
Dieses Repo haben wir noch nicht von GitHub gelesen
Dieser Server läuft auf deinem Computer; es gibt keinen Endpunkt im Internet
Läuft auf deinem Computer und nutzt stattdessen lokale Einstellungen
Läuft auf deinem Computer; Tool-Listen können wir nur von Endpunkten im Internet lesen
Verglichen mit allen aktiven Servern dieser Kategorie in der Registry. Sterne zählen nur, wenn dem Herausgeber das Repo gehört.
Er hat 1 von 1 zutreffenden Basischecks bestanden. Den Code haben wir nicht gelesen. Bevor du einen Schlüssel oder Token hinzufügst, sieh nach, welche Zugriffe der Server verlangt, und nutze einen Schlüssel, der nur die Berechtigungen hat, die du brauchst.
Die Registry nennt keinen erforderlichen Schlüssel, manche Server bitten dich aber bei der ersten Nutzung, dich anzumelden.
Er läuft auf deinem Computer. Deine KI-App startet ihn bei Bedarf, und die Daten laufen nicht über die Server des Entwicklers (außer der Server ruft selbst einen Onlinedienst auf).
Das GitHub-Repo wurde zuletzt – geändert, und die neueste Version (0.1.0-alpha.4) kam vor 13 Tagen in die Registry.
Apps, die MCP unterstützen, etwa Claude Desktop, Claude Code, Cursor und VS Code. Außerdem brauchst du Node.js auf deinem Computer.
In derselben Kategorie: Spec Driven Development, Remote Desktop Commander, Zendesk
Server derselben Kategorie von anderen Entwicklern, sortiert nach Sternen.
So liest du eine Karte:★ GitHub-SterneiDrei Säulen: Bewertungen · Checks · NutzungiAktualisiert = neueste Version in der Registry veröffentlichti
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.
Zendesk MCP Pack — tickets, users, organizations via OAuth.
Unverändert aus dem Repo des Entwicklers übernommen. PopNx MCP hat den Inhalt weder geprüft noch empfiehlt es ihn. HTML, Bilder und Skripte wurden entfernt. Links führen von dieser Website weg.
Give AI agents a checkable trail: evidence, formal logic and prerequisite plans.
Local-first, open-source MCP server · CLI · TypeScript SDK. The core runs on an ordinary CPU with Node.js; no GPU, AI subscription or model API key needed. It stores attributed evidence, checks supplied integer constraints through Z3, and plans from explicit dependencies. It does not replace your host AI.
Open the recorded preview · Try the engine locally · npm · Connect your agent · Tool API · Launch status
Developer alpha `0.1.0-alpha.4`. Check release availability for current npm, MCP Registry and hosted-demo status. Source and local tarball installation are available independently of those services. Image-to-3D is an optional, unfinished advanced workflow; no validated 90% fidelity claim exists.
With Node.js 24.11+ in 24.x, or Node.js 26+, run the published exact version:
npx --yes noetra@0.1.0-alpha.4 demo
Open http://127.0.0.1:7860. Check a claim, toggle a missing prerequisite or inspect an evidence record. These controls execute the actual engine, not canned results. Every run has a separate in-memory database, discarded afterward. No model downloads or optional 3D tools are installed. Stop with Ctrl+C.
No installation yet? The free online preview lets you inspect real recorded examples and the walkthrough. It displays stored results; it does not run the engine remotely. The command above runs the actual engine locally. The npm artifact was checked against the reviewed upload and a fresh anonymous registry installation passed the MCP/SQLite/Z3 self-test.
Watch the 60-second result walkthrough · How to reproduce the examples
The walkthrough presents actual engine outputs as labelled cards; it is not a browser recording. Capture provenance.
| Example | What NOETRA does | Scope |
|---|---|---|
Integer premise x ≥ 2, claim x ≥ 1 | Z3 checks entailment | Valid only for the supplied integer premises |
Same premise, stronger claim x ≥ 5 | Returns a counterexample | A formal counterexample, not a real-world measurement |
| Build → review → release, tests missing | Reports blocked actions | Actions/effects are supplied; nothing is published |
| One observed test result | Stores origin, digest and limitations | Remains an untrusted observation, not proof |
Maintained by NOETRA2. Core code is MIT licensed. Optional providers have their own licences and are not bundled or installed automatically. NOETRA is independent of Nexa apps and is not endorsed by Tencent, OpenAI, REA, Blender or other upstream projects.
Prerequisite: Node.js 24.11+ in the 24.x line, or Node.js 26+ and npm. No GPU is needed for the core reasoning/MCP tools.
git clone https://github.com/NOETRA2/NOETRA.git
cd NOETRA npm ci --ignore-scripts npm run build node dist/apps/cli/src/index.js help node dist/apps/cli/src/index.js doctor node dist/apps/cli/src/index.js test
GitHub's Code → Download ZIP also provides the source; extract it and run the npm commands from that folder. Once the exact release appears under the verified owner harshavardhan2 on npm, it can be run without a source build:
npx --yes noetra@0.1.0-alpha.4 test
npx --yes noetra@0.1.0-alpha.4 demo
Use a project-local installation for durable AI-host registration, rather than relying on an npm temporary cache path. Availability and publish verification are tracked in the release-status document; these commands are not a claim that an unverified package or hosted endpoint is live.
To build a local distributable:
npm pack
node dist/apps/cli/src/index.js setup --client codex --scope project
node dist/apps/cli/src/index.js setup --client cursor --scope project node dist/apps/cli/src/index.js setup --client claude --scope project
Setup previews configuration first. Cursor/Claude JSON setup requires a reviewed --apply --yes; Codex registration prints a TOML snippet for manual review. Reconnect the host afterward. No existing AI-client or REA settings are silently replaced. See installation.
| Component | Role | What it does not establish |
|---|---|---|
| Codex host agent | Interpreted the brief, authored scripts/candidates and reviewed output | Exact host model identifier was not recorded in the original experiment |
| Built-in image-generation tool | Created reference/concept artwork | Those images are not renders of a mesh; exact image-model/version was not recorded |
| Tencent Hunyuan3D-2mini Turbo | Actual learned lion geometry | Hidden surfaces, accurate anatomy, physical scale and materials remain unverified |
| TripoSR + U2Net/rembg | Optional local shape backend / foreground estimation | Not automatically fused detailed multi-view reconstruction |
| Blender 5.2.2 LTS | Mesh assembly, PBR baking, export and actual renders | A successful render is not an accuracy score |
| xatlas 0.0.11; OpenCV; NumPy/SciPy | UV charts, measured appearance, image/geometry calculations | Colour clusters do not identify anatomy or recover depth |
| Z3 | Checks explicit formal constraints | Does not judge artistic quality or physical truth |
| REA 6.7.0 / optional Ghidra | Authorized software investigation | They are analysis tools, not image-to-3D generators |
The lion model revision is f90a0f7df7d5e6f71109cf333f6a95a0ae3194a6; the upstream source commit is f8db63096c8282cb27354314d896feba5ba6ff8a. The pinned manifest includes full checkpoint/source hashes. Model weights, third-party applications, private accounts and local model caches are excluded.
Hunyuan is a separately licensed optional provider, not MIT-licensed model weights. Review its licence, notice and model/source provenance before provisioning it. Its licence contains territory and use restrictions. Powered by Tencent Hunyuan when that provider is enabled; Tencent does not sponsor, endorse or operate this independent project.
The images below are Blender renders of actual meshes, not generated concept pictures presented as 3D output. Details, settings and limitations are in comparisons.
Left: without NOETRA, a new host-authored procedural lion built directly in Blender from primitives, remeshing and solid geometry. No NOETRA code or learned shape model generated that mesh. Right: with NOETRA, the existing lion created through its Hunyuan3D-2mini Turbo workflow. Both pictures render real meshes using the same clay material, lighting, view directions and normalized height. The procedural lion is stylized; these different methods are not a controlled test of NOETRA's quality or accuracy. The downloadable mesh, script and second angle are in comparisons.
We also ran a separate direct Hunyuan inference with NOETRA bypassed and otherwise matching inputs/settings. That result is identical to the workflow's raw mesh; the report preserves this evidence. No numerical accuracy gain is claimed.
The local core TypeScript/build checks, 71 Node tests and CLI protocol self-test passed. The reconstruction Python suite and focused cache/region tests passed (156 tests across the recorded runs). The example meshes were actually exported, reimported and rendered. GitHub Actions results, once available, are separate from these local checks.
The lion mesh and painting remain partial. Accurate facial anatomy, semantic part-to-mesh correspondence, calibrated detailed multi-view fusion, intrinsic albedo/PBR recovery and reliable unseen geometry are unfinished. The automatic appearance-readiness gate remains false; an explicitly requested unverified paint preview does not override it or replace the accepted model.
Accuracy is not measured by triangle count, watertightness, successful export or a visually pleasing screenshot. We need a defined metric, independent ground-truth 3D data, held-out inputs and reproducible evaluation before making a numerical fidelity claim such as 90%.
Architecture · Tool API · Security · REA · Reconstruction · Appearance analysis · Surface painting · Third-party notices
npm ci --ignore-scripts
npm run check
Python reconstruction tests require separately provisioned local dependencies; model inference is optional and is not run merely by installing the core package. Report reproducible problems through GitHub Issues, with sanitized inputs and logs. Do not upload credentials, private images, AI-client settings or model weights.