OpenCode

OpenCode configures MCP servers under the mcp key in its JSON config. Use ~/.config/opencode/opencode.json for every project, or opencode.json in a repository root for one project. Project config takes precedence over global config for conflicting keys.

Configuration

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dagu": {
      "type": "remote",
      "url": "http://localhost:8080/mcp",
      "enabled": true,
      "headers": {
        "Authorization": "Bearer {env:DAGU_MCP_API_KEY}"
      }
    }
  }
}

"type": "remote" selects an HTTP MCP server. Drop the headers block when the Dagu server runs with authentication disabled, and set "enabled": false to keep the entry without connecting.

OpenCode interpolates {env:VARIABLE_NAME} from the environment, substituting an empty string when the variable is unset. {file:path} reads a value from a file, which suits a key kept outside the repository.

Verify

opencode mcp list

Related

OpenCode can also run as a workflow step through the harness executor, which is the inverse relationship: Dagu drives OpenCode instead of OpenCode driving Dagu.

Reference: OpenCode MCP servers documentation.