pre.dev Architect MCP Server

### 1. Basic Configuration This is a minimal, ready-to-use configuration to run the **pre.dev Architect MCP Server** via a local binary/CLI called `predev-architect-mcp` (adjust the command/path if your executable name is different). ```json { "pre.dev Architect MCP Server": { "command": { "path": "predev-architect-mcp" }, "category": "DevTools" } } ``` **Explanation (not part of JSON):** - `"pre.dev Architect MCP Server"`: The key under `mcpServers` in `~/.claude/settings.json`. This is how Claude Code will label this server. - `"command.path"`: The executable name or full path to the MCP server. - If installed globally, `predev-architect-mcp` is enough. - If it’s in a specific location, use something like `/usr/local/bin/predev-architect-mcp`. - `"category": "DevTools"`: Lets Claude group this under development tools in the UI. --- ### 2. Advanced Configuration This version adds: - Explicit arguments - Environment variables - A working directory - A timeout for starting the server ```json { "pre.dev Architect MCP Server": { "command": { "path": "/usr/local/bin/predev-architect-mcp", "args": [ "--log-level", "info", "--port", "8765" ] }, "env": { "ARCHITECT_ENV": "development", "ARCHITECT_API_TOKEN": "your-dev-api-token-here", "ARCHITECT_CONFIG_PATH": "/Users/yourname/.config/predev-architect/config.yaml" }, "workingDirectory": "/Users/yourname/projects", "startTimeoutMs": 15000, "category": "DevTools" } } ``` **Explanation (not part of JSON):** - `"command.path"`: Full path to the server binary for reliability. - `"command.args"`: - `--log-level info`: More verbose logs while still being readable. - `--port 8765`: Forces the MCP server to bind on a specific port if it supports that. - `"env"`: - `ARCHITECT_ENV`: Tells the server to run in `development` mode (e.g., less strict, more logs). - `ARCHITECT_API_TOKEN`: API token for talking to pre.dev Architect’s backend (replace with a real token or use your secret manager). - `ARCHITECT_CONFIG_PATH`: Path to a config file where project/workspace defaults are stored. - `"workingDirectory"`: Default directory where the MCP server will run; useful if it infers monorepos or architecture from the filesystem. - `"startTimeoutMs"`: How long Claude waits (in ms) for the MCP server to start before giving up. - `"category"`: Still categorized as `DevTools`. --- ### 3. Use Case Specific Configuration **Use Case: Production Architecture Review & Change Proposals for a Monorepo** This configuration is tailored for using pre.dev Architect as a “production-aware” architecture assistant on a large monorepo, with: - A specific monorepo root as working directory - A “production” environment - Read-only mode to prevent destructive operations - A dedicated config for CI/CD and deployment topology ```json { "pre.dev Architect MCP Server": { "command": { "path": "/opt/predev/architect-mcp", "args": [ "--log-level", "warn", "--mode", "readonly", "--project-root", "/srv/monorepo", "--profile", "production" ] }, "env": { "ARCHITECT_ENV": "production", "ARCHITECT_API_TOKEN": "prod-architect-api-token", "ARCHITECT_ORG_ID": "your-org-id", "ARCHITECT_PROJECT_ID": "main-monorepo", "ARCHITECT_DEPLOYMENT_DESCRIPTOR": "/srv/monorepo/infra/deploy/production-architecture.yaml" }, "workingDirectory": "/srv/monorepo", "startTimeoutMs": 30000, "category": "DevTools" } } ``` **Explanation (not part of JSON):** - `"command.path"`: Assumes the binary is installed in `/opt/predev/architect-mcp` on a server or devbox. - `"command.args"`: - `--log-level warn`: Less noisy logs, better for production-like usage. - `--mode readonly`: Ensures the MCP only analyzes and proposes changes, not modify files or infra directly (if supported). - `--project-root /srv/monorepo`: Explicitly points to your monorepo root so the server can understand the full architecture. - `--profile production`: Tells the server to use production-specific defaults (e.g., stricter validation). - `"env"`: - `ARCHITECT_ENV=production`: Enables production-related checks and constraints. - `ARCHITECT_API_TOKEN`: Production token (store securely; avoid committing this). - `ARCHITECT_ORG_ID` / `ARCHITECT_PROJECT_ID`: Lets the server correlate local repo state with your pre.dev Architect organization and project. - `ARCHITECT_DEPLOYMENT_DESCRIPTOR`: Points to a file describing your production services, dependencies, and deployment topology, allowing Claude to ask the MCP for architecture-aware insights. - `"workingDirectory"`: Set to the monorepo root where architecture analysis will run. - `"startTimeoutMs": 30000`: Longer timeout in case the server does heavy initialization on a large codebase. - `"category"`: Still `DevTools`, but this config is tuned for production architecture review and change proposal workflows.