Web Task

io.github.jojo-labsPublished by GitHub account jojo-labsv0.10.1Updated Oct 27, 2026

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

VerifiedSTDIODesktop onlyProductivity & WorkflowBrowser Automation

Overview

AI-generated overview

Web Task exposes browser tasks, sessions and recipes to an assistant over MCP, running as a local stdio process on the desktop.

What you can do
  • Run and manage browser tasks driven by an assistant
  • Keep and reuse browser sessions and profiles
  • Use bundled or custom recipes for repeatable web automation
  • Point the browser at a specific channel or an existing user-data directory
  • Choose a planner backend and model for task planning
When to use it
Worth adding when you want an assistant to carry out repeatable browser work on your own machine, such as scripted web tasks or sessions that keep their logged-in state, rather than one-off page reads.
Requirements
Runs as a local npm package over stdio, desktop only, with no declared authentication. A browser is needed (Playwright, optionally a channel such as chrome or an existing user-data directory). Planner backends are configured by environment variables: WEB_TASK_API_PI_URL, OPENCODE_BASE_URL, or the legacy CLIPROXY_BASE_URL with CLIPROXY_AUTH_TOKEN. Data, temp and recipes directories can be overridden.
Before you install
CLIPROXY_AUTH_TOKEN is a secret passed by environment variable. Reusing an existing browser user-data directory gives the assistant access to warmed browser state, which may include logged-in sessions and cookies. Browser tasks act on live sites and can submit or change data. Task data and prompts go to whichever planner backend you configure, which may be a remote service.

Installation

In SourceWeft

  1. Open Web Task in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.10.1LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.