Workspace MCP

Workspace MCP is a generic, secure local development platform that exposes controlled developer capabilities to AI clients through the Model Context Protocol (MCP).

It is not a Merciless Janitors Studios product. MJS is one consumer and may ship an extension package—the core must work for any developer who has never heard of MJS.

Mission

Allow AI assistants to work naturally inside explicitly authorized development workspaces—with deny-by-default security, audit logging, and capability-aware adaptation to each repository.

Related MCP server: Local-MCP-Bridge

Status

M2 Tools (Implemented)

Permission profiles: observer (read+search), maintainer (+commands). See config/examples/commands.json.

M1 Tools (Implemented)

Writes, search, commands, and extensions are M2+ — see docs/hds/product/roadmap.md.

Installation

cd ~/Documents/dev/workspace-mcp
npm install
npm run build

Configuration

Copy examples and edit paths for your machine:

mkdir -p ~/.config/workspace-mcp/grants
cp config/examples/workspaces.json ~/.config/workspace-mcp/
cp config/examples/grants/local-dev.json ~/.config/workspace-mcp/grants/
cp config/examples/commands.json ~/.config/workspace-mcp/
chmod 600 ~/.config/workspace-mcp/grants/local-dev.json

Override config directory: WORKSPACE_MCP_CONFIG_DIR

Cursor / MCP Client

Add to MCP settings (stdio):

{
  "mcpServers": {
    "workspace-mcp": {
      "command": "node",
      "args": ["/absolute/path/to/workspace-mcp/dist/index.js"],
      "env": {
        "WORKSPACE_MCP_PRINCIPAL_ID": "local-dev"
      }
    }
  }
}

Client smoke tests are M5 — configuration above is not yet validated against all clients.

Development

npm test        # 15 tests — security + auth + tools
npm run build
npm run dev     # stdio server via tsx

Core vs Extensions

The core must not depend on any extension.

Documentation Map

Claim Boundaries

• Not production-ready · M1 read-only only · Client integrations unverified (M5)

• No writes/search/commands until M2/M3