Web Task

A local MCP server that runs browser tasks, sessions and recipes for automation, with optional planner backends.

What you can do

Run browser automation tasks and keep them in reusable sessions, driven from an assistant over MCP or HTTP. Apply bundled recipes for repeatable browser workflows, with an optional recipes directory override. Optionally route task planning through a CLIProxy or OpenCode backend, configured by base URL and model. Reuse an existing Chromium or Chrome user-data directory for warmed browser state, and choose a browser channel or visible versus headless mode.

When to use it

Worth adding when an assistant should drive a real browser on the user's desktop for repeatable, recipe-based web tasks, and when you already have a planner backend or a warmed browser profile you want to reuse.

Requirements

Runs as a local process on the user's machine via the npm package web-task-api over stdio; desktop only, not usable from the web. Needs Node.js and a Playwright-compatible browser. Optional settings include BROWSER_CHANNEL, BROWSER_USER_DATA_DIR, HEADLESS, the WEB_TASK_API_DATA_DIR, WEB_TASK_API_RECIPES_DIR and WEB_TASK_API_TEMP_DIR paths, and the CLIProxy or OpenCode base URL and model variables.