Validatar Agent Kit for Devin

Set up the Validatar Agent Kit in Devin Desktop (which replaced Windsurf) or the Devin CLI. When you finish, Devin can explore your Validatar catalog, create and run tests, and package test packs.

Before you start

• Devin Desktop or the Devin CLI installed and signed in.
• Python 3.9 or newer on the PATH (python --version).
• Your Validatar instance address, for example https://acme.cloud.validatar.com.
• A Validatar user that can create tests in at least one project, ideally a sandbox project.

Get the kit

1. Download Validatar Agent Kit for Devin from the Validatar Marketplace.
2. Extract the zip. It holds one folder, validatar-kit-devin/. Use it as your working folder, or copy its contents into an existing repository (see below).

Create your tokens and set the variables

1. In Validatar, open your user profile, User Tokens. Create a token of type MCP. For MCP + API mode (optional), also create a token of type API with the scopes Authoring, Execution, Data Steward and Catalog.

2. Set the environment variables for your user account:

   Variable	Value
   VALIDATAR_URL	Your instance address, no trailing slash
   VALIDATAR_MCP_TOKEN	The MCP token
   VALIDATAR_API_TOKEN	The API token (optional: MCP + API mode)

   Windows (PowerShell): setx VALIDATAR_URL "https://acme.cloud.validatar.com", and the same for each token. macOS or Linux: export lines in ~/.zshrc or ~/.bashrc.

3. In the kit folder, run python validatar/scripts/setup.py configure, then python validatar/scripts/setup.py check.

Check the connection

setup.py configure wrote .devin/mcp_config.json with your instance address:

{
  "mcpServers": {
    "validatar": {
      "url": "https://acme.cloud.validatar.com/core/mcp",
      "transport": "http",
      "headers": { "x-val-api-token": "${env:VALIDATAR_MCP_TOKEN}" }
    }
  }
}

1. Restart Devin Desktop and open the kit folder (or run devin in it).
2. Open the MCP settings: validatar is connected.
3. Ask: "Connect to Validatar and tell me what projects and data sources I have."

Note: If validatar answers 401, Devin did not expand the variable. Copy the validatar entry into .devin/mcp_config.local.json with the token itself in the header. That file is meant for secrets, and the kit's .gitignore keeps it out of version control.

The always-on instructions are in AGENTS.md, and the skills in .agents/skills/ (type / and a skill name to call one). In Code mode Devin asks before running commands; to let the helper scripts run, allow Exec(python validatar/scripts/*) in Devin's command rules.

Use the kit in an existing repository

Copy AGENTS.md (or append its content to yours), .agents/skills/validatar-*, .devin/mcp_config.json (or merge its validatar entry), the validatar/ folder and the lines from .gitignore.

Troubleshooting