Skip to content
mcp/harbor
Grok

Web Task for Grok

io.github.jojo-labs/web-task-api

Browser tasks, sessions, and recipes for MCP and HTTP automation.

client:Grok transport:stdio runtime:npm

Install Web Task in Grok

.mcp.json (in your project root)

Held in this page only — never stored, logged, or sent anywhere but back to your screen. 

{
  "mcpServers": {
    "web-task-api": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "web-task-api"
      ],
      "env": {
        "WEB_TASK_API_DATA_DIR": "<WEB_TASK_API_DATA_DIR>",
        "WEB_TASK_API_RECIPES_DIR": "<WEB_TASK_API_RECIPES_DIR>",
        "WEB_TASK_API_TEMP_DIR": "<WEB_TASK_API_TEMP_DIR>",
        "WEB_TASK_API_MODEL": "<WEB_TASK_API_MODEL>",
        "WEB_TASK_API_VARIANT": "<WEB_TASK_API_VARIANT>",
        "WEB_TASK_API_PI_URL": "<WEB_TASK_API_PI_URL>",
        "WEB_TASK_API_PI_MODEL": "<WEB_TASK_API_PI_MODEL>",
        "WEB_TASK_API_PI_VARIANT": "<WEB_TASK_API_PI_VARIANT>",
        "CLIPROXY_BASE_URL": "<CLIPROXY_BASE_URL>",
        "CLIPROXY_AUTH_TOKEN": "<CLIPROXY_AUTH_TOKEN>",
        "CLIPROXY_MODEL": "<CLIPROXY_MODEL>",
        "OPENCODE_BASE_URL": "<OPENCODE_BASE_URL>",
        "OPENCODE_MODEL": "<OPENCODE_MODEL>",
        "BROWSER_USER_DATA_DIR": "<BROWSER_USER_DATA_DIR>",
        "BROWSER_CHANNEL": "<BROWSER_CHANNEL>",
        "HEADLESS": "<HEADLESS>"
      }
    }
  }
}

Grok Build reads Claude Code's .mcp.json and Claude Desktop's config unchanged, so a server you have already set up there needs nothing new. The Grok web app and X integration do not take custom servers. Grok docs

Web Task in other clients

Web Task MCP server