1xOps Command Center
Persistent terminal sessions, processes and text-file tools under one folder and command policy
Installation
Ajoutez ceci à la configuration MCP de votre client (Claude Desktop : claude_desktop_config.json ; Cursor : .cursor/mcp.json ; VS Code et les autres utilisent la même forme « mcpServers »).
@1xops/command-centerclaude mcp add 1xops-command-center -- npx -y @1xops/command-center@0.4.2
{
"mcpServers": {
"1xops-command-center": {
"command": "npx",
"args": [
"-y",
"@1xops/command-center@0.4.2"
]
}
}
}
Documentation
Tirée du README du projet sur GitHub, actualisée chaque semaine. Les liens ouvrent GitHub.
1xOps Command Center
Your AI agent keeps a terminal open — tests, logs, REPLs and SSH — inside the folders you allow.
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 on your machine with your permissions and sends nothing anywhere.
/plugin marketplace add 1xOps/command-center
/plugin install command-center@command-center
💼 What teams use it for
| Scenario | How it works | Why it helps |
|---|---|---|
| 🧪 Fix a failing test suite | Run the tests, read the failures, edit, run again — in the same shell | The environment stays set up; the engineer reviews one diff |
| 🚨 Watch logs during an incident | Start a tail, read new output on demand, stop it with force_terminate | A second pair of eyes on live output; nothing left running afterwards |
| 📊 Check data in a REPL | python3 -i or node -i keeps the data loaded across turns | Answers come from the data, not from a script re-run each time |
| 🔐 Diagnose a server over SSH | One ssh session kept open across turns | Faster remote triage. The blocklist checks the remote command and each typed line; the remote account's permissions are still the real limit |
| 🏢 One approved setup for the team | Commit a pinned .mcp.json | Every seat runs the same reviewed version |
🧩 Clients and platforms
| Client | Install | macOS | Linux | Windows |
|---|---|:-:|:-:|:-:|
| Claude Code — plugin (server + 6 skills) | /plugin install above | ✓ | ✓ | ✓ ¹ |
| Claude Code — server only | claude mcp add | ✓ | ✓ | ✓ ¹ |
| Claude Desktop | .mcpb from Releases | ✓ | | ✓ ¹ |
| OpenAI Codex CLI | codex mcp add | ✓ | ✓ | ✓ ¹ |
| VS Code (agent mode) | .vscode/mcp.json | ✓ | ✓ | ✓ ¹ |
Node.js 24 or later (Claude Desktop installs it from the .mcpb). 20 tools — see mcp-server/README.md.
¹ Windows code paths and tests exist; a Windows CI run has not happened yet.
⚙️ Install for each client (pinned to 0.4.2)
Replace /path/to/project with the folders the agent may use; they become allowedDirectories for that session.
The plugin passes no folder. With no folder and an empty
allowedDirectoriesthere is no folder limit. SetallowedDirectoriesin~/.command-center/config.json, or use a server-only install with a folder.
# Claude Code, server only
claude mcp add command-center -- npx -y @1xops/command-center@0.4.2 /path/to/project
# OpenAI Codex CLI
codex mcp add command-center -- npx -y @1xops/command-center@0.4.2 /path/to/project
VS Code — .vscode/mcp.json:
{ "servers": { "command-center": { "type": "stdio", "command": "npx", "args": ["-y", "@1xops/command-center@0.4.2", "${workspaceFolder}"] } } }
Claude Desktop — open command-center-0.4.2.mcpb from Releases; it asks which folders Command Center may use.
🏢 Team configuration (one pinned setup for every seat)
Claude Code — commit .mcp.json at the project root:
{ "mcpServers": { "command-center": { "command": "npx", "args": ["-y", "@1xops/command-center@0.4.2", "."] } } }
Codex — ~/.codex/config.toml:
[mcp_servers.command-center]
command = "npx"
args = ["-y", "@1xops/command-center@0.4.2", "/path/to/project"]
Check where a build came from: npm view @1xops/command-center@0.4.2 dist.attestations (npm provenance from the CI release).
📦 Container (a real boundary for the host)
Non-root user; sees only the mounted folder. Build from a checkout of this repo:
docker build -t command-center:0.4.2 mcp-server
claude mcp add command-center -- docker run -i --rm --network none -v "/path/to/project:/workspace" command-center:0.4.2
--network none cuts network access for untrusted work; drop it if sessions need the network.
🛡️ Security model
Command Center runs commands with your permissions and trusts the AI client driving it. It does not detect prompt injection.
| Control | What it does | Security boundary? | |
|---|---|---|---|
allowedDirectories | Every file tool and session working folder must be inside these folders (symlinks resolved first). Empty = no limit | No | |
blockedCommands | Refuses listed programs wherever they start a command, incl. after ; && `\ | $(…),sh -c,env/timeoutwrappers; always refuseseval/Invoke-Expression. Defaults includesudo,dd,mount,diskpart,reg` | No |
| Person-only settings | set_config_value refuses allowedDirectories, blockedCommands, defaultShell; file tools refuse the config folder | No | |
| Container | Non-root, only the mounted folder visible | Yes, for the host filesystem |
Limits: a program started in a session can reach any path and network you can, and could edit the config file (it applies at the next start). The command check reads command lines (including lines typed into a shell or ssh session), not scripts or REPL input. Each session keeps its last 1 MiB of output in memory.
Privacy: no telemetry, analytics, update checks or remote calls. See SECURITY.md · PRIVACY.md.
📁 In this repository
| Folder | What it is |
|---|---|
mcp-server/ | npm package @1xops/command-center: server, tests, Claude Desktop bundle, container |
plugins/command-center/ | Claude Code plugin: the pinned server plus six skills |
docs/supply-chain/register.md | Every shipped package and its licence, signed by the owner |
MCP Registry io.github.1xOps/command-center · Apache-2.0 © 2026 1xOps · Report vulnerabilities privately: SECURITY.md
Questions fréquentes
Qu'est-ce que 1xOps Command Center ?
Persistent terminal sessions, processes and text-file tools under one folder and command policy
Comment installer 1xOps Command Center ?
Il s'exécute sur votre machine. Dans Claude Code : claude mcp add 1xops-command-center -- npx -y @1xops/command-center@0.4.2. Pour les autres clients, collez la configuration JSON de cette page dans leurs réglages MCP.
Faut-il une clé API pour 1xOps Command Center ?
Son entrée au registre n'indique aucune clé ni secret obligatoire. Certaines fonctions peuvent tout de même demander un compte auprès du service auquel il se connecte.
1xOps Command Center est-il open source ?
Oui. Son code est sur GitHub sous licence Apache-2.0.
Qui maintient 1xOps Command Center ?
Il est publié par 1xOps. AI.tn le référence sans le maintenir ni le recommander.
Issu du registre MCP officiel. Être listé n'est pas une recommandation : vérifiez le code et les permissions d'un serveur avant de lui donner accès à vos données.