Allows AI assistants to manage browser profiles, control web pages, execute scripts, and manage automation schedules via the Veilus desktop app.
Also known as veilus/sdk, veilus-mcp
- Stars
- 0
- Tools
- —
- Downloads, 30 days
- —
- Latest version
- 0.1.0
- Last commit
- Oct 28, 2026
- License
- —
What is Veilus MCP?
Veilus allows AI assistants to manage browser profiles, control web pages, execute scripts, and manage automation schedules via the Veilus desktop app.
Summary generated from the project's README
About Veilus MCP server
Veilus provides a bridge between AI assistants and the Veilus desktop application to enable browser automation. Developers using Claude Code, Cursor, or Claude Desktop can connect to the app to manage browser profiles and control web pages directly through an MCP client. The server functions by running the Veilus binary with an mcp subcommand, allowing users to interact with the desktop software via standard input and output.
To use this server, you must have the Veilus desktop app installed and running with the local API enabled. A Pro plan or higher is required to access the MCP server and local API features. Setup involves providing a VEILUS_API_TOKEN generated from the app's settings. Users can specify the location of the application using the VEILUS_BINARY environment variable, particularly on non-macOS systems, to ensure the client can successfully execute commands.
What you can do with it
- 1Automate web page interactionsYou can instruct an AI to drive a running browser profile to perform tasks on a webpage.
- 2Execute and store automation scriptsThe server allows for the saving and running of scripts to automate web workflows.
- 3Schedule browser automation tasksDevelopers can use the tool to create specific schedules for browser activities.
Written from the project's README. Every use case is checked against a quote from it.
How to install Veilus MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall Veilus MCP in Claude Code
$ claude mcp add --env 'VEILUS_API_TOKEN=<YOUR_VEILUS_API_TOKEN>' veilus -- npx -y veilus-mcpInstall Veilus MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"veilus": {
"command": "npx",
"args": [
"-y",
"veilus-mcp"
],
"env": {
"VEILUS_API_TOKEN": "<YOUR_VEILUS_API_TOKEN>"
}
}
}
}Install Veilus MCP in VS Code
.vscode/mcp.json
{
"servers": {
"veilus": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"veilus-mcp"
],
"env": {
"VEILUS_API_TOKEN": "<YOUR_VEILUS_API_TOKEN>"
}
}
}
}Install Veilus MCP in VS Code CLI
$ code --add-mcp '{"name":"veilus","type":"stdio","command":"npx","args":["-y","veilus-mcp"],"env":{"VEILUS_API_TOKEN":"<YOUR_VEILUS_API_TOKEN>"}}'Install Veilus MCP in Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"veilus": {
"command": "npx",
"args": [
"-y",
"veilus-mcp"
],
"env": {
"VEILUS_API_TOKEN": "<YOUR_VEILUS_API_TOKEN>"
}
}
}
}Install Veilus MCP in Codex
$ codex mcp add veilus --env 'VEILUS_API_TOKEN=<YOUR_VEILUS_API_TOKEN>' -- npx -y veilus-mcpInstall Veilus MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.veilus] command = "npx" args = ["-y", "veilus-mcp"] [mcp_servers.veilus.env] VEILUS_API_TOKEN = "<YOUR_VEILUS_API_TOKEN>"
Install Veilus MCP in Gemini CLI
$ gemini mcp add -s user -e 'VEILUS_API_TOKEN=<YOUR_VEILUS_API_TOKEN>' veilus npx -- -y veilus-mcpInstall Veilus MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"veilus": {
"command": "npx",
"args": [
"-y",
"veilus-mcp"
],
"env": {
"VEILUS_API_TOKEN": "<YOUR_VEILUS_API_TOKEN>"
}
}
}
}Configuration
VEILUS_API_TOKENRequiredSecretAPI token from the API & MCP page of the Veilus app
VEILUS_BINARYPath to the Veilus app binary, if not in the default macOS location
Automated checks
Ran Nov 14, 2026Full report →Passed our automated checks. That is not a security audit: read the code and give the server the narrowest access it needs. How checks work · What to fix for more points
- Source repository linked and reachableveilus/sdk is public and reachablegithub.com/veilus/sdk ↗Pass
- Package names this repository as its sourceveilus-mcp names veilus/sdk as sourcenpmjs.com/package/veilus-mcp ↗Pass
- Build provenance (Sigstore attestation)No build attestation published for this releaseNot checked
- Open source license (OSI)No licenseFinding
- Commit or release in the last yearLast commit or release 2026-10-28github.com/veilus/sdk ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNo popular package one edit away from veilus-mcpPass
- No critical advisory in the package or its dependencies1 resolved dependencies checked; no critical advisoryosv.dev ↗Pass
- No hidden instructions to the model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNot checked
- Remote endpoint answers the MCP handshakeNot checked
README
View on GitHubveilus-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.
Veilus MCP questions
How do I add Veilus MCP to Claude Code?
Run claude mcp add --env 'VEILUS_API_TOKEN=<YOUR_VEILUS_API_TOKEN>' veilus -- npx -y veilus-mcp in your terminal. Add --scope user to make it available in every project.
How do I add Veilus MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
Can I use this with Claude Desktop or Cursor?
Yes, the server can be used with Claude Code, Cursor, Claude Desktop, or any standard stdio MCP client.