Veilus

io.github.veilusPublished by GitHub account veilusv0.1.0Updated Oct 24, 2026

Drive Veilus browser profiles from an AI assistant: profiles, pages, scripts, schedules.

VerifiedSTDIODesktop onlyProductivity & WorkflowBrowser Automation

Overview

AI-generated overview

Launcher that connects an AI assistant to the Veilus desktop app to manage browser profiles, drive pages, run scripts and create schedules.

What you can do
  • List and launch Veilus browser profiles
  • Drive the page of a running profile
  • Save and run scripts
  • Create schedules
  • Find the installed Veilus app binary and start its MCP subcommand
When to use it
Use it when you already run the Veilus desktop app on macOS and want an assistant such as Claude Code, Cursor or Claude Desktop to operate browser profiles, pages, scripts and schedules from the chat.
Requirements
The Veilus desktop app installed and running, with the local API enabled on its API & MCP page, which also issues the token. A Pro plan or higher (7-day Pro trial available). Node.js 18 or newer. The VEILUS_API_TOKEN environment variable is required; VEILUS_BINARY sets the app binary path when it is not in the default macOS location.
Before you install
Requires the VEILUS_API_TOKEN secret, which grants access to the app's local API. The server can launch profiles, drive pages, run scripts and create schedules, so actions change state in the app and the browser. Paid Pro plan needed after the trial. Desktop only; on non-macOS systems the binary path must be set manually.

Installation

In SourceWeft

  1. Open Veilus 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

veilus-mcp

MCP server launcher for Veilus, a desktop app for running browser profiles. It lets Claude Code, Cursor, Claude Desktop or any stdio MCP client list and launch profiles, drive a running profile's page, save and run scripts, and create schedules.

The MCP server itself is the Veilus app (its binary has an mcp subcommand). This package finds the installed app and runs <app binary> mcp, passing stdin, stdout, stderr and the environment through unchanged, so you can configure it with npx instead of a machine-specific path.

Requirements

  • The Veilus desktop app, installed and running, with the local API turned on from the API & MCP page in the app sidebar. That page also creates the token.
  • A Pro plan or higher: the MCP server and local API are not on the Free plan. The app includes a 7-day Pro trial.
  • Node.js 18 or newer.

Setup

Claude Code:

bash
claude mcp add --scope user veilus -e VEILUS_API_TOKEN=<token> -- npx -y veilus-mcp

Other clients (Cursor, Claude Desktop, …):

json
{  "mcpServers": {    "veilus": {      "command": "npx",      "args": ["-y", "veilus-mcp"],      "env": { "VEILUS_API_TOKEN": "<token>" }    }  }}

Finding the app

  1. VEILUS_BINARY, if set: the full path to the app binary. The API & MCP page shows this path.
  2. On macOS: /Applications/Veilus.app/Contents/MacOS/veilus, then the same under ~/Applications.

On other systems, set VEILUS_BINARY.

If the app is not found, veilus-mcp still starts and lists the Veilus tools, but every tool call returns an error asking you to install the app. This is how MCP directories can inspect the server without the app.

The tool list in tools.json is generated from the Veilus docs catalog with npm run sync-tools; don't edit it by hand.

License

MIT or Apache-2.0, at your option.

Source: mcp/README.md at commit 2715afa

Tools

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

Version history

1
  1. v0.1.0LatestOct 16, 2026

Score

40% 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
  • License10 pts

    Declare a license in the repository or the registry entry.