Agents

Give coding agents the Vectis skill and MCP server so they can prepare environments, connect repositories and diagnose jobs.

Agents use the same service and the same commands as you: the vectis CLI with JSON output, or the vectis-mcp server. The Vectis skill teaches them the workflow and the rules, such as never approving a pairing request on your behalf.

First install the command line tools from the app, so vectis and vectis-mcp are on your PATH.

Claude Code

Install the plugin, which contains the skill and registers the MCP server:

/plugin marketplace add kerddotdev/vectis
/plugin install vectis@vectis

Or add only the MCP server:

claude mcp add vectis -- vectis-mcp

Codex

Add the server to ~/.codex/config.toml:

[mcp_servers.vectis]
command = "vectis-mcp"

Copy skills/vectis into your Codex skills directory to add the skill.

Cursor and other MCP clients

Any client that starts stdio MCP servers can run vectis-mcp. For Cursor, add to ~/.cursor/mcp.json:

{
  "mcpServers": {
    "vectis": { "command": "vectis-mcp" }
  }
}

The skill is a plain SKILL.md that works with any agent that reads skills.

MCP tools

Tool	Use
`vectis_capabilities`	Supported commands and queries, with the command schema
`vectis_status`	Machine, environments, VMs, recent operations and cloud connection
`vectis_command`	Submit a command with an idempotency key
`vectis_activities`, `vectis_activity`	What the machine was asked to do, and one intent with the operations that carried it
`vectis_operation`, `vectis_wait`	Read one operation, or wait for it; a wait that times out returns the current state
`vectis_logs`	The newest service log lines
`vectis_repositories`, `vectis_jobs`, `vectis_github_accounts`	Connections with their labels, job results, linked accounts
`vectis_storage`, `vectis_doctor`	Disk usage and runtime diagnostics
`vectis_github_connect`	The page that links GitHub and installs the App
`vectis_service`, `vectis_cloud`	Login service and pairing, on the Mac itself only
`vectis_machines`	Your Macs, after `vectis login`

To let an agent control another Mac, sign in once with vectis login and start the server with vectis-mcp --machine <machine-id>. A remote session never falls back to the local Mac.

vectis_status returns a compact summary: machine and cloud state, runner capacity, environments, non-stopped instances, counts within the status window, and the newest 20 operations and activities with shortened messages. It omits full operation results. Read vectis_activities for unfinished activities and the newest 100 terminal activities, vectis_activity for one retained activity and all its steps, or vectis_operation for a full result. These detail tools query individual records, locally and remotely, and remain available when a record falls outside the status window. Tool results are returned once in structuredContent, with an empty content array.

Rules agents follow

Humans approve pairing, sign-in and GitHub linking in the browser. Agents hand over the link and wait.
An accepted operation is not a finished one. Agents report the final status, and follow nextStep for action_required.
Agents reuse an idempotency key only to retry the exact same command.

Documentation for agents

llms.txt indexes every page, llms-full.txt contains all of them, and appending .md to any page URL returns its Markdown.