nodebench-mcp 1.4.0 → 1.4.1

package/README.md

@@ -1,6 +1,6 @@
 # NodeBench MCP Server
 
-A fully local, zero-config MCP server with 46 tools for AI-powered development workflows.
+A fully local, zero-config MCP server with **60 tools** for AI-powered development workflows.
 
 **Features:**
 - Web search (Gemini/OpenAI/Perplexity)
@@ -9,13 +9,23 @@ A fully local, zero-config MCP server with 46 tools for AI-powered development w
 - AGENTS.md self-maintenance
 - AI vision for screenshot analysis
 - 6-phase verification flywheel
+- Self-reinforced learning (trajectory analysis, health reports, improvement recommendations)
+- Autonomous agent bootstrap and self-maintenance
 - SQLite-backed learning database
 
-## Quick Start (1 minute)
+## Quick Start (30 seconds)
 
-### 1. Add to Claude Code settings
+### Option A: Claude Code CLI (recommended)
 
-Add to `~/.claude/settings.json`:
+```bash
+claude mcp add nodebench -- npx -y nodebench-mcp
+```
+
+That's it. One command, 60 tools. No restart needed.
+
+### Option B: Manual config
+
+Add to `~/.claude/settings.json` (global) or `.claude.json` (per-project):
 
 ```json
 {
@@ -28,7 +38,7 @@ Add to `~/.claude/settings.json`:
 }
 ```
 
-That's it. Restart Claude Code and you have 46 tools.
+Then restart Claude Code.
 
 ---
 
@@ -114,11 +124,14 @@ In Claude Code, try these prompts:
 | **Learning** | `record_learning`, `search_learnings`, `search_all_knowledge` | Persistent knowledge base |
 | **Flywheel** | `run_closed_loop`, `check_framework_updates` | Automated workflows |
 | **Recon** | `run_recon`, `log_recon_finding`, `log_gap` | Discovery and gap tracking |
+| **Agent Bootstrap** | `bootstrap_project`, `setup_local_env`, `triple_verify`, `self_implement` | Self-discover infrastructure, auto-configure |
+| **Autonomous** | `assess_risk`, `decide_re_update`, `run_self_maintenance`, `run_autonomous_loop` | Risk-tiered autonomous execution |
+| **Self-Eval** | `log_tool_call`, `get_trajectory_analysis`, `get_self_eval_report`, `get_improvement_recommendations` | Self-reinforced learning loop |
 | **Meta** | `findTools`, `getMethodology` | Tool discovery, methodology guides |
 
 ---
 
-## Methodology Topics (15 total)
+## Methodology Topics (17 total)
 
 Ask Claude: `Use getMethodology("topic_name")`
 
@@ -137,6 +150,34 @@ Ask Claude: `Use getMethodology("topic_name")`
 - `tech_stack_2026` — Dependency management
 - `telemetry_setup` — Observability setup
 - `agents_md_maintenance` — Keep docs in sync
+- `agent_bootstrap` — Self-discover and auto-configure infrastructure
+- `autonomous_maintenance` — Risk-tiered autonomous execution
+- `self_reinforced_learning` — Trajectory analysis and improvement loop
+
+---
+
+## Self-Reinforced Learning (v1.4.0)
+
+The MCP learns from its own usage. As you develop with the tools, the system accumulates trajectory data and surfaces recommendations.
+
+```
+Use → Log → Analyze → Recommend → Apply → Re-analyze
+```
+
+**Try it:**
+```
+> Use getMethodology("self_reinforced_learning") for the 5-step guide
+> Use get_self_eval_report to see your project's health score
+> Use get_improvement_recommendations to find actionable improvements
+> Use get_trajectory_analysis to see your tool usage patterns
+```
+
+The health score is a weighted composite:
+- Cycle completion (25%) — Are verification cycles being completed?
+- Eval pass rate (25%) — Are eval runs succeeding?
+- Gap resolution (20%) — Are logged gaps getting resolved?
+- Gate pass rate (15%) — Are quality gates passing?
+- Tool error rate (15%) — Are tools running without errors?
 
 ---
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "nodebench-mcp",
-  "version": "1.4.0",
+  "version": "1.4.1",
   "description": "NodeBench MCP server — 60 tools for AI-powered development. Self-reinforced learning, trajectory analysis, web search, GitHub discovery, vision analysis, verification flywheel, autonomous self-maintenance.",
   "type": "module",
   "bin": {