Web Task MCP Server

Web Task is an MCP integration. Browser tasks, sessions, and recipes for MCP and HTTP automation.

Packages and local setup

The published npm package is web-task-api, version 0.10.1. Its declared MCP transport is stdio.

The package declares 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: 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..

Before connecting

Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.

Project and source

View the publisher’s registry entry · Project repository. This profile uses version 0.10.1 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.

Browse related browser automation MCP servers for tools that cover the same kind of work.