Veilus

Name: Veilus
Author: veilus

Local

docs.veilus.ioBrowser Automation0Updated 1d ago

Repository Visit website

About Veilus

Veilus is an MCP server launcher for the Veilus desktop app, for people using AI assistants or other stdio MCP clients to control browser profiles. It exposes profile, page, script, and scheduling operations through the installed app.

Key features

01List and launch browser profiles
02Control pages in running profiles
03Save and run scripts
04Create schedules

Use cases

01Launch a browser profile from an assistant
02Drive pages in an active profile
03Run a saved browser script
04Schedule profile tasks

MCP support

The Veilus app provides the MCP server; this package locates the installed app and launches its `mcp` subcommand. MCP clients can use it to list and launch profiles, control pages, manage scripts, and create schedules.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config

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

Run commandnpx -y veilus-mcp

Environment variables to set

VEILUS_API_TOKENSecretAPI token from the API & MCP page of the Veilus app

VEILUS_BINARYPath to the Veilus app binary, if not in the default macOS location

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages

npmveilus-mcp0.1.0stdio

Tools

Saved tool list · updated 2w ago

This tool takes no parameters.

Details

From the project 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:

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

Other clients (Cursor, Claude Desktop, …):

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

Finding the app

VEILUS_BINARY, if set: the full path to the app binary. The API & MCP page shows this path.
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.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

Read the getting-started guide

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.