@1xops/command-center 0.4.0 → 0.4.1

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 (2) hide show
  1. package/README.md +62 -94
  2. package/package.json +4 -4
package/README.md CHANGED
@@ -1,141 +1,109 @@
1
1
  # 1xOps Command Center
2
2
 
3
- An MCP server that gives Claude and OpenAI agents **persistent terminal sessions** (tests, builds, logs, REPLs, SSH) and **text-file tools**, limited to the folders a person allows, with one command blocklist. It runs on your machine with your permissions and sends nothing anywhere.
3
+ **Your AI agent keeps a terminal open — tests, logs, REPLs and SSH — inside the folders you allow.**
4
4
 
5
- - **Clients:** Claude Code, Claude Desktop, OpenAI Codex CLI, Gemini CLI, Cursor, VS Code, and any other MCP client that starts a stdio server.
6
- - **Platforms:** macOS, Linux and Windows. macOS and Linux are tested locally before each push; all three run in CI on every release pull request to `main`.
7
- - **Requires:** Node.js 24 or later (Claude Code, Codex). Claude Desktop installs it from one file.
8
- - **Package:** `@1xops/command-center` · MCP Registry name `io.github.1xOps/command-center` · Apache-2.0.
5
+ A local MCP server: shell sessions that stay open between turns, plus text-file tools, under one folder limit and one command blocklist that only a person can change. It runs with your permissions and sends nothing anywhere.
9
6
 
10
- ## Install (always pin the version)
11
-
12
- Replace `/path/to/project` with the folders the agent may use. Folders given at launch become `allowedDirectories` for that session.
13
-
14
- **Claude Code: plugin (server plus usage skills)**
15
-
16
- ```
17
- /plugin marketplace add 1xOps/command-center-mcp
18
- /plugin install command-center@command-center
19
- ```
7
+ | | |
8
+ |---|---|
9
+ | 🧩 **Clients** | Claude Code (plugin or server only), Claude Desktop (`.mcpb`), OpenAI Codex CLI, VS Code |
10
+ | 💻 **Platforms** | macOS, Linux, Windows (Windows not yet run in CI) |
11
+ | ⚙️ **Requires** | Node.js 24+ (Claude Desktop installs it from the `.mcpb`) |
12
+ | 📦 **Package** | `@1xops/command-center` · MCP Registry `io.github.1xOps/command-center` · 2 runtime deps (MCP SDK, zod) · Apache-2.0 |
20
13
 
21
- **Claude Code: server only**
14
+ ## 💼 What teams use it for
22
15
 
23
- ```bash
24
- claude mcp add command-center -- npx -y @1xops/command-center@0.4.0 /path/to/project
25
- ```
16
+ | Scenario | Why it helps |
17
+ |---|---|
18
+ | 🧪 **Fix failing tests** — run, read failures, edit, re-run in one shell | Environment stays set up; one diff to review |
19
+ | 🚨 **Watch logs in an incident** — tail, read on demand, stop when done | Live second pair of eyes; nothing left running |
20
+ | 📊 **Check data in a REPL** — `python3 -i` / `node -i` keeps data loaded | Answers from the data itself |
21
+ | 🔐 **Diagnose over SSH** — one session kept open | Faster triage; the remote account's permissions are the limit there |
22
+ | 🏢 **One team setup** — commit a pinned `.mcp.json` | Every seat runs the same reviewed version |
26
23
 
27
- **OpenAI Codex CLI**
24
+ ## 🚀 Install (pinned)
28
25
 
29
- ```bash
30
- codex mcp add command-center -- npx -y @1xops/command-center@0.4.0 /path/to/project
31
- ```
32
-
33
- **Gemini CLI**
26
+ Replace `/path/to/project` with the folders the agent may use; they become `allowedDirectories`.
34
27
 
35
28
  ```bash
36
- gemini extensions install https://github.com/1xOps/command-center-mcp
37
- ```
29
+ # Claude Code: plugin (server + 6 skills) — passes no folder; see Settings
30
+ /plugin marketplace add 1xOps/command-center
31
+ /plugin install command-center@command-center
38
32
 
39
- The extension (`gemini-extension.json`) runs the pinned server with the current folder allowed. To choose folders, add it to `~/.gemini/settings.json` instead:
33
+ # Claude Code: server only
34
+ claude mcp add command-center -- npx -y @1xops/command-center@0.4.1 /path/to/project
40
35
 
41
- ```json
42
- { "mcpServers": { "command-center": { "command": "npx", "args": ["-y", "@1xops/command-center@0.4.0", "/path/to/project"] } } }
36
+ # OpenAI Codex CLI
37
+ codex mcp add command-center -- npx -y @1xops/command-center@0.4.1 /path/to/project
43
38
  ```
44
39
 
45
- **Cursor:** add to `~/.cursor/mcp.json` (all projects) or `.cursor/mcp.json` (one project):
40
+ <details>
41
+ <summary><b>VS Code, Claude Desktop, team setup, container</b></summary>
46
42
 
43
+ **VS Code** — `.vscode/mcp.json`:
47
44
  ```json
48
- { "mcpServers": { "command-center": { "command": "npx", "args": ["-y", "@1xops/command-center@0.4.0", "/path/to/project"] } } }
45
+ { "servers": { "command-center": { "type": "stdio", "command": "npx", "args": ["-y", "@1xops/command-center@0.4.1", "${workspaceFolder}"] } } }
49
46
  ```
50
47
 
51
- **VS Code (agent mode):** add to `.vscode/mcp.json`:
48
+ **Claude Desktop (macOS, Windows)** — open `command-center-0.4.1.mcpb` from [Releases](https://github.com/1xOps/command-center/releases); it asks which folders to allow.
52
49
 
50
+ **Team setup** — commit `.mcp.json` (Codex: same args under `[mcp_servers.command-center]` in `~/.codex/config.toml`):
53
51
  ```json
54
- { "servers": { "command-center": { "type": "stdio", "command": "npx", "args": ["-y", "@1xops/command-center@0.4.0", "${workspaceFolder}"] } } }
52
+ { "mcpServers": { "command-center": { "command": "npx", "args": ["-y", "@1xops/command-center@0.4.1", "."] } } }
55
53
  ```
54
+ Provenance of a build: `npm view @1xops/command-center@0.4.1 dist.attestations`.
56
55
 
57
- On Windows, if a client cannot start `npx`, use `"command": "npx.cmd"`.
58
-
59
- **Claude Desktop (macOS, Windows):** download `command-center-0.4.0.mcpb` from the [release](https://github.com/1xOps/command-center-mcp/releases) and open it. The installer asks which folders Command Center may use.
60
-
61
- **Container (any OS with Docker):** it sees only the folder you mount.
62
-
56
+ **Container** — from a repo checkout; sees only the mounted folder:
63
57
  ```bash
64
- docker build -t command-center:0.4.0 mcp-server
65
- claude mcp add command-center -- docker run -i --rm -v "/path/to/project:/workspace" command-center:0.4.0
58
+ docker build -t command-center:0.4.1 mcp-server
59
+ claude mcp add command-center -- docker run -i --rm --network none -v "/path/to/project:/workspace" command-center:0.4.1
66
60
  ```
61
+ </details>
67
62
 
68
- ## Team configuration (one approved setup for every seat)
69
-
70
- Commit this to the project as `.mcp.json` (Claude Code). Every engineer then runs the same pinned version with the same folders:
71
-
72
- ```json
73
- {
74
- "mcpServers": {
75
- "command-center": {
76
- "command": "npx",
77
- "args": ["-y", "@1xops/command-center@0.4.0", "."]
78
- }
79
- }
80
- }
81
- ```
82
-
83
- The Codex equivalent, in `~/.codex/config.toml`:
84
-
85
- ```toml
86
- [mcp_servers.command-center]
87
- command = "npx"
88
- args = ["-y", "@1xops/command-center@0.4.0", "/path/to/project"]
89
- ```
90
-
91
- Check what a seat runs with `npm view @1xops/command-center@0.4.0 dist.attestations`. It shows the build provenance npm recorded at publish.
92
-
93
- ## Tools (20)
63
+ ## 🛠️ Tools (20)
94
64
 
95
65
  | Area | Tools |
96
66
  |---|---|
97
67
  | Processes | `start_process`, `interact_with_process`, `read_process_output`, `force_terminate`, `list_sessions` |
98
68
  | Files (text; images returned as images) | `read_file`, `read_multiple_files`, `write_file`, `edit_block`, `list_directory`, `get_file_info`, `create_directory`, `move_file` |
99
- | Search (ripgrep when installed) | `search`; for large result sets, paged: `start_search`, `get_more_search_results`, `stop_search` (up to 10 kept, each freed 10 minutes after its last read) |
100
- | System (read-only) | `list_processes`: the OS process list with memory, on macOS, Linux and Windows |
69
+ | Search (ripgrep when installed) | `search`; paged: `start_search`, `get_more_search_results`, `stop_search` |
70
+ | System (read-only) | `list_processes` |
101
71
  | Settings | `get_config`, `set_config_value` |
102
72
 
103
- PDF, Word, Excel and PowerPoint files are handled by the official document skills: `pdf`, `docx`, `xlsx` and `pptx` from Anthropic's skills repository. They work in Claude and, as Agent Skills, in Codex (`.agents/skills`). Each lists the tools it needs, for example LibreOffice or Python packages.
73
+ For PDF, Word, Excel and PowerPoint, use Anthropic's document skills (`pdf`, `docx`, `xlsx`, `pptx`).
104
74
 
105
- ## Settings
75
+ ## 🛡️ Settings and security
106
76
 
107
- Settings live in `~/.command-center/config.json` (on Windows, `%USERPROFILE%\.command-center\config.json`). The file is created with defaults on first start.
77
+ `~/.command-center/config.json` (Windows: `%USERPROFILE%\.command-center\config.json`), created on first start.
108
78
 
109
79
  | Key | Purpose | Who can change it |
110
80
  |---|---|---|
111
- | `allowedDirectories` | Folders every file tool and working directory must be inside. Folders given at launch override this. **Empty means no folder limit.** | a person only |
81
+ | `allowedDirectories` | Folders every file tool and working folder must be inside. Launch folders override it. **Empty = no folder limit** | a person only |
112
82
  | `blockedCommands` | Programs refused wherever they start a command (defaults include `sudo`, `dd`, `mount`, `diskpart`, `reg`) | a person only |
113
- | `defaultShell` | Shell for sessions (default: your login shell; PowerShell on Windows) | a person only |
114
- | `fileReadLineLimit` | Lines per `read_file` (default 1000) | person or agent |
115
- | `fileWriteLineLimit` | Lines per `write_file` call (default 50) | person or agent |
116
-
117
- An agent cannot widen its own access: `set_config_value` refuses the first three keys.
83
+ | `defaultShell` | Session shell (login shell; PowerShell on Windows) | a person only |
84
+ | `fileReadLineLimit` / `fileWriteLineLimit` | Lines per read (1000) / per write (50) | person or agent |
118
85
 
119
- ## Security
86
+ <details>
87
+ <summary><b>Limits you should know</b></summary>
120
88
 
121
- Command Center runs commands with your permissions. `allowedDirectories` and `blockedCommands` are guardrails against mistakes, **not a sandbox**: a program started in a session can reach anything you can. For untrusted work, use the container. See [SECURITY.md](SECURITY.md).
89
+ - Guardrails against mistakes, **not a sandbox**: a program started in a session can reach any path and network you can, and could edit the config file (applies at next start).
90
+ - The command check reads command lines — not scripts, REPL input, or what is typed over SSH.
91
+ - Each session keeps its last 1 MiB of output in memory; a secret a command prints is visible to the client.
92
+ - For untrusted work, use the container. No telemetry or remote calls. See [SECURITY.md](SECURITY.md) · [PRIVACY.md](PRIVACY.md).
93
+ </details>
122
94
 
123
- ## Development
95
+ <details>
96
+ <summary><b>Development and releases</b></summary>
124
97
 
125
98
  ```bash
126
- npm ci
127
- npm test # build + all tests (node:test)
128
- task setup # once per clone: turns on the git-standard hooks
129
- task check # every local gate before the owner commits develop
130
- task mcp:verify # from the repo root: timed end-to-end check with evidence
131
- task mcp:act # the real CI workflow's macOS job on this Mac (act, no runner image)
132
- task mcp:ci-local # the Linux CI job in the pinned Wolfi image
133
- task mcp:supply-chain # SBOM and the signed dependency register
99
+ npm ci && npm test # build + all tests
100
+ task check # every local gate (from the repo root)
101
+ task mcp:ci-local # Linux CI job in the pinned Wolfi image
102
+ task mcp:supply-chain # SBOM against the signed dependency register
134
103
  task mcp:release-rehearsal # what would be published, publishing nothing
135
104
  ```
136
105
 
137
- Releases run in CI from a tag `mcp-server-vX.Y.Z`. They publish only after the owner approves, through the `release` environment (see `.github/workflows/mcp-server-release.yml`).
138
-
139
- ## Licence
106
+ Releases run in CI from a tag `command-center-vX.Y.Z` and publish to npm with provenance (OIDC trusted publishing) only after the owner approves the `release` environment.
107
+ </details>
140
108
 
141
- Apache-2.0 © 2026 1xOps (nnthanh101, nnthanh101@gmail.com). See [LICENSE](LICENSE). The npm packages it depends on keep their own licences; the list is in the supply-chain register.
109
+ Apache-2.0 © 2026 1xOps. Dependencies keep their own licences; see the [supply-chain register](https://github.com/1xOps/command-center/blob/develop/docs/supply-chain/register.md).
package/package.json CHANGED
@@ -1,17 +1,17 @@
1
1
  {
2
2
  "name": "@1xops/command-center",
3
- "version": "0.4.0",
3
+ "version": "0.4.1",
4
4
  "description": "1xOps Command Center: an MCP server for persistent terminal sessions, processes and text-file work, with one folder and command policy for Claude and OpenAI clients",
5
5
  "mcpName": "io.github.1xOps/command-center",
6
6
  "license": "Apache-2.0",
7
7
  "author": "1xOps (nnthanh101) <nnthanh101@gmail.com> (https://github.com/1xOps)",
8
- "homepage": "https://github.com/1xOps/command-center-mcp/tree/develop/mcp-server",
8
+ "homepage": "https://github.com/1xOps/command-center/tree/develop/mcp-server",
9
9
  "repository": {
10
10
  "type": "git",
11
- "url": "git+https://github.com/1xOps/command-center-mcp.git",
11
+ "url": "git+https://github.com/1xOps/command-center.git",
12
12
  "directory": "mcp-server"
13
13
  },
14
- "bugs": "https://github.com/1xOps/command-center-mcp/issues",
14
+ "bugs": "https://github.com/1xOps/command-center/issues",
15
15
  "type": "module",
16
16
  "engines": {
17
17
  "node": ">=24"