MCP configuration

Automated setup

opentide setup mcp --cursor --yes
opentide setup mcp --vscode --generic --yes

Minimal config

VS Code workspace MCP (.vscode/mcp.json) uses a top-level servers object. Cursor, Claude Code, and the generic template use mcpServers.

Repo-root placeholders are host-specific. VS Code and Cursor expand ${workspaceFolder}. Claude Code expands ${CLAUDE_PROJECT_DIR}. The generic file is copied into arbitrary hosts, so it does not set OPENTIDE_REPO_ROOT — the server walks up from cwd to the nearest detection workspace (get_repo_root). Set an absolute path when cwd is not inside the detection workspace.

VS Code

{
  "servers": {
    "opentide": {
      "command": "opentide",
      "args": ["mcp", "start"],
      "env": {
        "OPENTIDE_REPO_ROOT": "${workspaceFolder}"
      }
    }
  }
}

Cursor

{
  "mcpServers": {
    "opentide": {
      "command": "opentide",
      "args": ["mcp", "start"],
      "env": {
        "OPENTIDE_REPO_ROOT": "${workspaceFolder}"
      }
    }
  }
}

Claude Code

{
  "mcpServers": {
    "opentide": {
      "command": "opentide",
      "args": ["mcp", "start"],
      "env": {
        "OPENTIDE_REPO_ROOT": "${CLAUDE_PROJECT_DIR}"
      }
    }
  }
}

Generic

{
  "mcpServers": {
    "opentide": {
      "command": "opentide",
      "args": ["mcp", "start"]
    }
  }
}

When the generic file is imported into a host that does expand placeholders, add that host's variable (or a real path) yourself.

Bundled templates: src/opentide/data/setup/mcp/.

Environment variables

Set in the MCP host's server environment block when the catalogue is not discoverable from the process cwd:

If OPENTIDE_REPO_ROOT is unset, get_repo_root() walks up from cwd to the nearest directory holding .opentide/ or objects/, without leaving the enclosing git checkout, and falls back to the git top level. See Repository root resolution. A literal unexpanded token such as ${workspaceFolder} is treated as a path, not interpolated by the server.

Cursor example

{
  "mcpServers": {
    "opentide": {
      "command": "opentide",
      "args": ["mcp", "start"],
      "env": {
        "OPENTIDE_REPO_ROOT": "/absolute/path/to/detection-repo"
      }
    }
  }
}

Multi-repo workspaces

When the editor workspace is the opentide package repo but content lives elsewhere, always set OPENTIDE_REPO_ROOT to the detection content root (an absolute path, not an editor placeholder the host will not expand).

Query validation policy

Agents must treat validate_query responses with supported: false as not validated for CrowdStrike and HarfangLab. Never infer a pass.

Deploy safety

deploy_rule defaults to dry_run=true. Agents should only set dry_run=false with explicit human approval.

Related

• Tools
• Usage: Agentic setup