tdoms-mcp 0.6.1 → 0.6.2

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 +42 -25
  2. package/package.json +1 -1
  3. package/src/index.js +20 -1
package/README.md CHANGED
@@ -4,38 +4,37 @@ Standalone TD/OMS change-management MCP for IBM Bob, Codex, Claude-compatible cl
4
4
 
5
5
  This is an independent community project. It is not affiliated with, maintained by, or endorsed by Remain Software, IBM, or their affiliates. TD/OMS, Octo, IBM, IBM i, and IBM Bob are trademarks of their respective owners.
6
6
 
7
- ## Setup
7
+ ## Install
8
8
 
9
- Install the published command-line package:
9
+ TD/OMS MCP is a command-line MCP server, not an application dependency. Install it globally so local agents can launch the `tdoms-mcp` command:
10
10
 
11
11
  ```shell
12
12
  npm install --global tdoms-mcp
13
13
  tdoms-mcp ui
14
14
  ```
15
15
 
16
- Or run it from a source checkout:
16
+ To try it without installing it globally:
17
17
 
18
- ```powershell
19
- npm install
20
- npm run ui
18
+ ```shell
19
+ npx --yes tdoms-mcp@latest ui
21
20
  ```
22
21
 
23
- Open `http://127.0.0.1:3737`, add the TD/OMS connection, and test it. Credentials and tokens stay in the local TD/OMS MCP data directory and are never returned to agents.
22
+ Open `http://127.0.0.1:3737`, add a TD/OMS connection, and test it. Credentials and tokens stay in the local TD/OMS MCP data directory and are never returned to agents.
24
23
 
25
24
  The Agent setup view detects supported MCP clients and can install or update this server after confirmation. Known configuration files are backed up before each change and restored automatically when a client command fails.
26
25
 
27
26
  Keep TLS verification enabled. Publicly trusted certificates work without configuration. For an internal certificate authority, set the optional CA certificate file in the connection manager or set `TDOMS_MCP_CA_FILE` to an approved PEM file supplied by the organization.
28
27
 
29
- Start the compact agent-neutral profile:
28
+ After a global installation, start the compact agent-neutral profile:
30
29
 
31
- ```powershell
32
- npm run mcp
30
+ ```shell
31
+ tdoms-mcp mcp
33
32
  ```
34
33
 
35
34
  Start the complete named-tool profile:
36
35
 
37
- ```powershell
38
- npm run mcp:full
36
+ ```shell
37
+ tdoms-mcp mcp --profile full
39
38
  ```
40
39
 
41
40
  The equivalent environment setting is `TDOMS_MCP_PROFILE=core` or `TDOMS_MCP_PROFILE=full`. `core` is the default.
@@ -67,25 +66,25 @@ tool_timeout_sec = 60
67
66
 
68
67
  Restart or reload the agent's MCP servers after changing the configuration.
69
68
 
70
- Detect supported local clients from the command line:
69
+ Detect supported local clients from the installed command:
71
70
 
72
- ```powershell
73
- npm run clients
71
+ ```shell
72
+ tdoms-mcp clients
74
73
  ```
75
74
 
76
75
  Install or update one detected client:
77
76
 
78
- ```powershell
79
- node src/index.js install-client ibm-bob --confirm
80
- node src/index.js install-client codex --confirm
81
- node src/index.js install-client claude-code --confirm
82
- node src/index.js install-client vscode --confirm
77
+ ```shell
78
+ tdoms-mcp install-client ibm-bob --confirm
79
+ tdoms-mcp install-client codex --confirm
80
+ tdoms-mcp install-client claude-code --confirm
81
+ tdoms-mcp install-client vscode --confirm
83
82
  ```
84
83
 
85
84
  Configure every detected client that is not already configured:
86
85
 
87
- ```powershell
88
- npm run clients:install
86
+ ```shell
87
+ tdoms-mcp install-detected --confirm
89
88
  ```
90
89
 
91
90
  Documented adapters are included for IBM Bob, Codex, Claude Code sessions, Claude Desktop chat, VS Code, Cursor, Windsurf, Kiro, Gemini CLI, Zed, and OpenCode. Microsoft Store Claude installations use the app's virtualized configuration directory automatically.
@@ -128,11 +127,29 @@ The `full` profile exposes 226 tools: the seven universal tools plus the existin
128
127
 
129
128
  All tools that can change TD/OMS require explicit confirmation. `tdoms_call_api` remains available in `full` as an advanced escape hatch for documented endpoints.
130
129
 
131
- ## Validation
130
+ ## CLI Reference
131
+
132
+ ```text
133
+ tdoms-mcp ui Open the local connection and agent setup UI
134
+ tdoms-mcp clients List detected MCP-capable agents
135
+ tdoms-mcp install-client <id> --confirm Configure one detected agent
136
+ tdoms-mcp install-detected --confirm Configure all detected agents
137
+ tdoms-mcp mcp Start the core stdio MCP server
138
+ tdoms-mcp mcp --profile full Start the complete tool profile
139
+ tdoms-mcp smoke Check local configuration without connecting
140
+ tdoms-mcp secure-storage Harden the local data directory
141
+ tdoms-mcp --help Show command help
142
+ ```
132
143
 
133
- ```powershell
144
+ ## Development
145
+
146
+ The following commands are only for contributors working from a cloned source repository. They are not required after installing the npm package.
147
+
148
+ ```shell
149
+ npm install
134
150
  npm test
135
151
  npm run smoke
152
+ npm run ui
136
153
  ```
137
154
 
138
155
  Tests use mocked TD/OMS clients and do not mutate a real environment. Live mutation tests must be enabled deliberately against a dedicated test system.
@@ -154,7 +171,7 @@ node -e "console.log(require('node:crypto').randomBytes(32).toString('base64'))"
154
171
  On Windows, restrict an existing data directory to the current user, SYSTEM, and local Administrators:
155
172
 
156
173
  ```powershell
157
- npm run secure-storage
174
+ tdoms-mcp secure-storage
158
175
  ```
159
176
 
160
177
  Native WSL uses its own Linux data directory and requires Node.js 18 or newer. To reuse the Windows installation and Windows credentials from WSL, launch Windows `node.exe`; otherwise configure the connection separately inside WSL. Avoid sharing credential files through `/mnt/c` unless the Windows ACL has been hardened.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "tdoms-mcp",
3
- "version": "0.6.1",
3
+ "version": "0.6.2",
4
4
  "description": "Agent-neutral MCP server for TD/OMS change-management workflows.",
5
5
  "type": "module",
6
6
  "license": "MIT",
package/src/index.js CHANGED
@@ -11,6 +11,11 @@ const profileFlagIndex = process.argv.indexOf("--profile");
11
11
  const profile = profileFlagIndex >= 0 ? process.argv[profileFlagIndex + 1] : process.env.TDOMS_MCP_PROFILE;
12
12
 
13
13
  async function main() {
14
+ if (["--help", "-h", "help"].includes(command)) {
15
+ printHelp();
16
+ return;
17
+ }
18
+
14
19
  const store = new ConnectionStore();
15
20
  const clientManager = new ClientManager();
16
21
 
@@ -69,10 +74,24 @@ async function main() {
69
74
  }
70
75
 
71
76
  console.error(`Unknown command: ${command}`);
72
- console.error("Expected one of: mcp, ui, dev, smoke, secure-storage, clients, install-client, install-detected");
77
+ printHelp(console.error);
73
78
  process.exit(1);
74
79
  }
75
80
 
81
+ function printHelp(write = console.log) {
82
+ write(`TD/OMS MCP
83
+
84
+ Usage:
85
+ tdoms-mcp ui
86
+ tdoms-mcp clients
87
+ tdoms-mcp install-client <id> --confirm
88
+ tdoms-mcp install-detected --confirm
89
+ tdoms-mcp mcp [--profile core|full]
90
+ tdoms-mcp smoke
91
+ tdoms-mcp secure-storage
92
+ tdoms-mcp --help`);
93
+ }
94
+
76
95
  main().catch((error) => {
77
96
  console.error(error);
78
97
  process.exit(1);