Commander Plus
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Commander PlusRegister this project as a workspace and check its health"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Commander Plus
A small, local-first MCP control-plane core for AI agents that need persistent project context without sending workstation state to a hosted orchestration service.
This public repository contains the safe reference layer: workspace registration, reusable skill routing and health guardians. Production-only desktop automation, authenticated browser control, private relay infrastructure and local operational data are intentionally not included.
Why it exists
Most agent demos are stateless. Commander Plus treats the workstation as a durable execution environment: projects have identities, skills can be routed by intent, and health checks make local state explicit.
Related MCP server: BirdEye
Included
MCP server over stdio
Persistent local workspace registry
Reusable skill registry and deterministic intent routing
Workspace health guardian
JSON storage under a configurable local application directory
Node test coverage for routing behavior
Run
Install dependencies with npm install.
Build with npm run build.
Start with npm start.
Set COMMANDER_PLUS_HOME to move the local state directory.
Architecture
Client -> MCP server -> workspace / skill / guardian services -> local JSON state
The public core is intentionally conservative. It does not expose shell execution, private browser sessions, credentials, customer data or machine-specific paths.
Public vs private boundary
Public: local control-plane primitives, MCP interface, routing model, tests and documentation.
Private: production browser bridge, privileged desktop automation, private plugins, relays, operational logs, local databases and deployment configuration.
Security
Treat any workstation-control plugin as privileged software. Review tool scopes before enabling write or execution capabilities. Never commit local state, environment files or credentials.
This server cannot be deployed
Maintenance
Related MCP Connectors
- OctopadOAuthapp.octopad
The back-office workspace for your team's AIs: tasks, knowledge and context shared over MCP.
Control plane for autonomous software labor. Agents claim objectives over MCP with audit trail.
Private-by-default, local-first memory/context/task orchestrator for MCP apps and agents.
System-of-record notebook for AI coding agents: pages, datastores, tasks, skills over MCP.
Related MCP Servers
- AlicenseNot gradedqualityBmaintenanceMCP server for task management, project knowledge, workspace trust, runner sandboxes, extension registry, and workflow prompts, enabling AI agents to manage tasks and collaborate locally.5,117 npmApache 2.0
- AlicenseNot gradedqualityBmaintenanceA local-first mission control for AI agent harnesses, providing a unified MCP gateway for shared memory, task queue, and encrypted secrets across multiple agents.1 npm1MIT
- AlicenseAqualityAmaintenanceMCP server that enables running and managing file-based AI Skills, Agents, and Flow workflows as DAGs, with tools for listing, executing, and resuming tasks via stdio JSON-RPC.9MIT
- FlicenseNot gradedqualityAmaintenanceSelf-hosted control plane for AI coding agents, providing persistent memory, session continuity, environment awareness, coordination, and replayable traces via MCP.2-