Connect MCP

Vatio provides an MCP server over stdio. In your MCP client's server settings, use this command and arguments:

{
  "mcpServers": {
    "vatio": {
      "command": "vatio",
      "args": ["mcp"]
    }
  }
}

Use your client's configuration format if it differs. If your client cannot find vatio on its PATH, use "command": "npx" with "args": ["-y", "@vatio-ai/cli@latest", "mcp"] instead. Log in with the CLI first. Start the server in the workspace directory, or pass the absolute workspace path as workspace_dir on tool calls:

{
  "args": ["--env", "pr-42"],
  "workspace_dir": "/path/to/support-agent"
}

That is a call to vatio_push. Each MCP tool takes the arguments after its CLI command as an array of strings. A message containing spaces is one array element.

What it exposes

MCP exposes docs, diagnostics, validation, deployment, chat, knowledge, secrets, tokens, widget inspection, and channel management. Login, workspace creation, issue submission, configuration, channel connection/disconnection, chat deletion, and knowledge-base deletion use the CLI directly. Browser consent and verification codes require the account holder.

Limits

MCP command output is limited to 20,000 characters. For the full docs, use vatio_docs with args: ["--save", "/absolute/path/vatio-docs.md"] and read that file with your coding agent's file tools. Commands time out after 180 seconds.