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).
web-task-apiclaude 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 '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.2.4
{
"mcpServers": {
"web-task": {
"command": "npx",
"args": [
"-y",
"web-task-api@0.2.4"
],
"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>",
"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_DIROptional 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_DIROptional recipes directory override. When omitted, web-task-api reads bundled recipes from the installed package.WEB_TASK_API_TEMP_DIROptional temp root override used when incoming temp env variables point at your home directory or working directory.CLIPROXY_BASE_URLOptional CLIProxy base URL for the cliproxy planner backend.CLIPROXY_AUTH_TOKENsecret Optional CLIProxy auth token for the cliproxy planner backend.CLIPROXY_MODELOptional CLIProxy model alias for the cliproxy planner backend.OPENCODE_BASE_URLOptional OpenCode base URL for the opencode planner backend.OPENCODE_MODELOptional OpenCode model name for the opencode planner backend.BROWSER_USER_DATA_DIROptional existing Chromium/Chrome user-data directory for warmed browser state reuse.BROWSER_CHANNELOptional Playwright browser channel override, for example `chrome`.HEADLESSOptional 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 '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.2.4. 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 rich-jojo. 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.