iso27001-mcp 0.8.7 → 0.8.8

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (3) hide show
  1. package/README.md +44 -9
  2. package/dist/index.js +270 -1101
  3. package/package.json +6 -5
package/README.md CHANGED
@@ -2,7 +2,7 @@
2
2
 
3
3
  **Turn Claude into an ISO 27001 compliance assistant** — controls, risk register, policies, evidence tracking, SoA generation, and full audit workflows in one local encrypted MCP server.
4
4
 
5
- [![Socket Badge](https://badge.socket.dev/npm/package/iso27001-mcp/0.8.7)](https://socket.dev/npm/package/iso27001-mcp/overview/0.8.7)
5
+ [![Socket Badge](https://badge.socket.dev/npm/package/iso27001-mcp/0.8.8)](https://socket.dev/npm/package/iso27001-mcp/overview/0.8.8)
6
6
  [![npm version](https://img.shields.io/npm/v/iso27001-mcp.svg)](https://npmjs.com/package/iso27001-mcp)
7
7
  [![npm downloads](https://img.shields.io/npm/dt/iso27001-mcp.svg)](https://npmjs.com/package/iso27001-mcp)
8
8
  [![CI](https://github.com/Sushegaad/MCP-Server-for-ISO27001/actions/workflows/ci.yml/badge.svg)](https://github.com/Sushegaad/MCP-Server-for-ISO27001/actions/workflows/ci.yml)
@@ -47,17 +47,36 @@ The difference from generating static documents: Claude can *query, reason, and
47
47
  ### Prerequisites
48
48
 
49
49
  - **Node.js 20.11.0+** — [nodejs.org](https://nodejs.org) or [nvm](https://github.com/nvm-sh/nvm) / [Volta](https://volta.sh)
50
- - **Build tools** (for the encrypted SQLite native module):
51
- - **macOS:** `xcode-select --install`
52
- - **Ubuntu/Debian:** `sudo apt-get install build-essential python3`
53
- - **Windows:** [Visual Studio Build Tools](https://visualstudio.microsoft.com/downloads/) "Desktop development with C++"
50
+
51
+ > **Build tools are usually not needed.** The package ships pre-built binaries for macOS (arm64 + x64), Windows (x64), and Linux (x64/glibc). Try `npm install -g iso27001-mcp` first — if it succeeds, you're done.
52
+ >
53
+ > <details><summary>↳ If the install fails with a <code>node-gyp</code> error, expand for OS-specific fix</summary>
54
+ >
55
+ > - **macOS:** `xcode-select --install`
56
+ > - **Ubuntu / Debian:** `sudo apt-get install build-essential python3`
57
+ > - **Windows:** [Visual Studio Build Tools](https://visualstudio.microsoft.com/downloads/) → "Desktop development with C++"
58
+ >
59
+ > </details>
60
+ >
61
+ > <details><summary>↳ If you get an <code>EACCES</code> permission error on macOS or Linux</summary>
62
+ >
63
+ > Your Node.js was installed system-wide and `npm install -g` needs write access to a root-owned directory. **Do not use `sudo npm install -g`** — it causes other issues. Instead, install Node via [nvm](https://github.com/nvm-sh/nvm) or [Volta](https://volta.sh), which place Node in your home directory where no elevated permissions are required.
64
+ >
65
+ > </details>
66
+ >
67
+ > <details><summary>↳ If you get <code>command not found</code> on Windows after a successful install</summary>
68
+ >
69
+ > The npm global bin directory (`%APPDATA%\npm`) may not be on your PATH yet. **Open a new terminal window** — the installer updates PATH for new sessions but not the one already open. If it still fails, add `%APPDATA%\npm` to your PATH manually in System Settings → Environment Variables.
70
+ >
71
+ > </details>
54
72
 
55
73
  ### Three commands to get running
56
74
 
57
75
  ```bash
58
- npm install -g iso27001-mcp # 1. install globally
59
- iso27001-mcp init # 2. interactive setup — secrets, database, API key, Claude config
60
- iso27001-mcp doctor # 3. verify everything is working
76
+ npm install -g iso27001-mcp # 1. install globally
77
+ iso27001-mcp init --yes # 2. one-shot setup — all defaults, no prompts
78
+ # (omit --yes to choose custom paths interactively)
79
+ iso27001-mcp doctor # 3. verify everything is working
61
80
  ```
62
81
 
63
82
  After running `iso27001-mcp doctor` you should see:
@@ -79,7 +98,23 @@ iso27001-mcp — health check
79
98
  All 10 checks passed. Restart Claude Desktop if you just ran init.
80
99
  ```
81
100
 
82
- Then **restart Claude Desktop** (quit fully and reopen). You should see 63 tools in the tools panel.
101
+ Then **restart Claude Desktop fully** and you should see 63 tools in the tools panel.
102
+
103
+ > **macOS:** press **Cmd+Q** to quit (clicking the red dot only closes the window — the server won't reload).
104
+ > **Windows:** right-click the taskbar icon → **Quit**.
105
+
106
+ ### Tools not appearing after restart?
107
+
108
+ Check the MCP server log — Claude Desktop writes server stderr here:
109
+
110
+ ```
111
+ macOS: ~/Library/Logs/Claude/mcp-server-iso27001-mcp.log
112
+ Windows: %APPDATA%\Claude\Logs\mcp-server-iso27001-mcp.log
113
+ ```
114
+
115
+ Common causes: wrong Node.js version loaded by Claude Desktop, missing `DB_ENCRYPTION_KEY` in the config, or a database path that doesn't exist yet. Run `iso27001-mcp doctor` in a fresh terminal for a guided diagnosis.
116
+
117
+ > **Switched Node versions with nvm or Volta?** The absolute Node.js path baked into your Claude Desktop config at init time now points to a deleted binary. Re-run `iso27001-mcp init` — it will detect your current setup and update the path. Your existing database and API keys are preserved (the wizard aborts if your secrets file already exists and you run with `--yes`).
83
118
 
84
119
  ### Five prompts to try first
85
120