English Français العربية

Web Task

Official registry Search and web

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

Source code

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

NPM package web-task-api
Claude Code 
claude mcp add web-task -e 'WEB_TASK_API_DATA_DIR=<WEB_TASK_API_DATA_DIR>' -e 'WEB_TASK_API_RECIPES_DIR=<WEB_TASK_API_RECIPES_DIR>' -e 'WEB_TASK_API_TEMP_DIR=<WEB_TASK_API_TEMP_DIR>' -e 'WEB_TASK_API_MODEL=<WEB_TASK_API_MODEL>' -e 'WEB_TASK_API_VARIANT=<WEB_TASK_API_VARIANT>' -e 'WEB_TASK_API_PI_URL=<WEB_TASK_API_PI_URL>' -e 'WEB_TASK_API_PI_MODEL=<WEB_TASK_API_PI_MODEL>' -e 'WEB_TASK_API_PI_VARIANT=<WEB_TASK_API_PI_VARIANT>' -e 'CLIPROXY_BASE_URL=<CLIPROXY_BASE_URL>' -e 'CLIPROXY_AUTH_TOKEN=<your cliproxy_auth_token>' -e 'CLIPROXY_MODEL=<CLIPROXY_MODEL>' -e 'OPENCODE_BASE_URL=<OPENCODE_BASE_URL>' -e 'OPENCODE_MODEL=<OPENCODE_MODEL>' -e 'BROWSER_USER_DATA_DIR=<BROWSER_USER_DATA_DIR>' -e 'BROWSER_CHANNEL=<BROWSER_CHANNEL>' -e 'HEADLESS=<HEADLESS>' -- npx -y web-task-api@0.10.1
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "web-task": {
            "command": "npx",
            "args": [
                "-y",
                "web-task-api@0.10.1"
            ],
            "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": "<your 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>"
            }
        }
    }
}

Environment variables

  • WEB_TASK_API_DATA_DIR Optional mutable data root for web-task-api runs, sessions, profiles, and temp state. When omitted, the runtime uses a platform user-data directory instead of the ambient cwd.
  • WEB_TASK_API_RECIPES_DIR Optional recipes directory override. When omitted, web-task-api reads bundled recipes from the installed package.
  • WEB_TASK_API_TEMP_DIR Optional temp root override used when incoming temp env variables point at your home directory or working directory.
  • WEB_TASK_API_MODEL Optional shared default planner model for catalog-backed PI and OpenCode selections. Defaults to deepseek/deepseek-v4-flash.
  • WEB_TASK_API_VARIANT Optional shared default planner thinking variant for catalog-backed PI and OpenCode selections. Defaults to high.
  • WEB_TASK_API_PI_URL Optional PI engine base URL for the preferred planner backend. Defaults to http://127.0.0.1:8793.
  • WEB_TASK_API_PI_MODEL Optional PI-specific planner model override. Defaults to WEB_TASK_API_MODEL when omitted.
  • WEB_TASK_API_PI_VARIANT Optional PI-specific thinking variant override. Defaults to WEB_TASK_API_VARIANT when omitted.
  • CLIPROXY_BASE_URL Optional CLIProxy base URL for the legacy fallback planner backend.
  • CLIPROXY_AUTH_TOKEN secret Optional CLIProxy auth token for the legacy fallback planner backend.
  • CLIPROXY_MODEL Optional CLIProxy model alias for the legacy fallback planner backend.
  • OPENCODE_BASE_URL Optional OpenCode base URL for the compatibility planner backend.
  • OPENCODE_MODEL Optional OpenCode model name for the compatibility planner backend. Defaults to WEB_TASK_API_MODEL when omitted.
  • BROWSER_USER_DATA_DIR Optional existing Chromium/Chrome user-data directory for warmed browser state reuse.
  • BROWSER_CHANNEL Optional Playwright browser channel override, for example `chrome`.
  • HEADLESS Optional browser headless toggle. Set `false` to prefer a visible browser.

Frequently asked questions

What is Web Task?

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

How do I install Web Task?

It runs on your machine. In Claude Code: claude mcp add web-task -e 'WEB_TASK_API_DATA_DIR=<WEB_TASK_API_DATA_DIR>' -e 'WEB_TASK_API_RECIPES_DIR=<WEB_TASK_API_RECIPES_DIR>' -e 'WEB_TASK_API_TEMP_DIR=<WEB_TASK_API_TEMP_DIR>' -e 'WEB_TASK_API_MODEL=<WEB_TASK_API_MODEL>' -e 'WEB_TASK_API_VARIANT=<WEB_TASK_API_VARIANT>' -e 'WEB_TASK_API_PI_URL=<WEB_TASK_API_PI_URL>' -e 'WEB_TASK_API_PI_MODEL=<WEB_TASK_API_PI_MODEL>' -e 'WEB_TASK_API_PI_VARIANT=<WEB_TASK_API_PI_VARIANT>' -e 'CLIPROXY_BASE_URL=<CLIPROXY_BASE_URL>' -e 'CLIPROXY_AUTH_TOKEN=<your cliproxy_auth_token>' -e 'CLIPROXY_MODEL=<CLIPROXY_MODEL>' -e 'OPENCODE_BASE_URL=<OPENCODE_BASE_URL>' -e 'OPENCODE_MODEL=<OPENCODE_MODEL>' -e 'BROWSER_USER_DATA_DIR=<BROWSER_USER_DATA_DIR>' -e 'BROWSER_CHANNEL=<BROWSER_CHANNEL>' -e 'HEADLESS=<HEADLESS>' -- npx -y web-task-api@0.10.1. For other clients, paste the JSON configuration from this page into their MCP settings.

Does Web Task need an API key?

Yes. It expects CLIPROXY_AUTH_TOKEN, which you set in its configuration.

Is Web Task open source?

Its code is public on GitHub, but the repository does not declare a standard license.

Who maintains Web Task?

It is published by jojo-labs. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.