AgentUtility Browser Workflow

ai.agentutilityPublished by agentutility.aiv0.1.1Updated Oct 24, 2026

MCP server for the @agentutility browser-workflow cluster — pay-per-call x402 tools, no API keys…

VerifiedSTDIODesktop onlyBrowser Automation

Overview

AI-generated overview

A local MCP server from AgentUtility's browser-workflow cluster that gives an assistant pay-per-call browser workflow tools without API keys.

What you can do
Provides browser-workflow tools from the AgentUtility cluster to a connected assistant, billed per call through x402 rather than an API key. The manifest lists no individual tools, so the exact actions available are not documented here. It runs as a local process on the user's machine over stdio.
When to use it
Consider it when you want an assistant to run AgentUtility browser workflows and are willing to pay per call instead of managing API keys. Because the tool list is not published, check the provider's documentation before relying on specific capabilities.
Requirements
Runs as a local process over stdio, installed from the npm package @agentutility/mcp-browser-workflow, so Node.js and npm are needed. Desktop only; no web-executable version. No authentication, environment variables or headers are declared.
Before you install
Calls are pay-per-call through x402, so using the tools spends money; confirm pricing and payment setup first. The manifest declares no authentication, so review how payment is authorized. The tool list is not published, so what the assistant can do is unclear until verified.

Installation

In SourceWeft

  1. Open AgentUtility Browser Workflow 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.1.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.