Claude Code Integration | Vibe Assurance Docs

What is the Vibe Assurance CLI?

The @vibe-assurance/cli package is an MCP (Model Context Protocol) server that connects Claude Code to your Vibe Assurance account. Once connected, Claude gains access to:

✓ AI Analyst Roles — Security Auditor, Risk Auditor, Implementation Planner, and more
✓ Document Templates — Change Requests, Risk Assessments, Security Reports
✓ Governance Context — Your existing CRs, risks, vulnerabilities, and next CR ID
✓ Artifact Storage — Save generated documents back to your Vibe Assurance account

Prerequisites

Vibe Assurance Account

You need an active account at vibeassurance.app.

Node.js 18+

The CLI requires Node.js version 18 or higher. Download Node.js →

Claude Code

Install Claude Code from claude.ai/code. Works with VS Code, terminals, and more.

Installation

Install the CLI globally

npm install -g @vibe-assurance/cli

This installs the vibe command globally on your system.

Verify installation

vibe --version

Should output 1.0.0 or higher.

Step 1: Authenticate

Run the login command

vibe login

This opens your default browser to the Vibe Assurance login page.

Sign in with your account

Log in using your Vibe Assurance credentials or Microsoft account. After successful authentication, you'll see a success message.

Credentials are stored securely

Your authentication tokens are stored in:

macOS: Keychain Access
Windows: Credential Manager
Linux: libsecret (or ~/.vibe/credentials.json fallback)

Step 2: Configure Claude Code

Run the setup command

vibe setup-claude

This automatically adds Vibe Assurance to Claude Code's MCP configuration.

Restart Claude Code

Close and reopen Claude Code (or run /mcp to refresh MCP servers). You should see "vibeassurance" listed as an active MCP server.

Verify connection

Ask Claude: "List my available vibe tools" — you should see all 14 vibe_* tools.

Available MCP Tools

Once connected, Claude Code has access to these tools:

Role Management

↓ vibe_list_roles

List all available AI analyst roles (Security Auditor, Implementation Planner, etc.)

↓ vibe_get_role

Get the full system prompt for a specific role by ID.

↑ vibe_create_role

Create a new custom AI analyst role with your own system prompt.

↑ vibe_update_role

Update an existing role's system prompt, name, or description.

Context & Templates

↓ vibe_get_context

Get your governance context: existing CRs, open risks, vulnerabilities, and next CR ID.

↓ vibe_list_templates

List available document templates (Change Request, Risk Assessment, etc.)

↓ vibe_get_template

Get a specific template with placeholders and structure.

Artifact Management

↓ vibe_list_artifacts

List your stored artifacts with optional type/status filters.

↓ vibe_get_artifact

Get a specific artifact by ID with full content and files.

↑ vibe_store_artifact

Store a new artifact (CR, Risk, Vulnerability, Report, Policy).

✓ vibe_append_file

Safely add or update a single file in an artifact without affecting other files. Recommended for file operations.

↑ vibe_update_artifact

Update an existing artifact's status, title, or metadata. Use vibe_append_file for file changes.

✕ vibe_delete_artifact

Permanently delete an artifact by ID.

Usage Examples

Act as Implementation Planner

Ask Claude to adopt a governance role:

"Use vibe_get_role to get the implementation-planner role, then act as that role to create a CR for adding user authentication."

Create and Store a Change Request

Generate governance documents and save them:

"Get my governance context, then create a Change Request for the API refactoring we discussed. Store it as a draft using vibe_store_artifact."

Security Audit Workflow

Run a security audit on your codebase:

"Adopt the security-auditor role from Vibe Assurance and scan the src/routes directory for OWASP Top 10 vulnerabilities. Store any findings as vulnerability artifacts."

CLI Commands Reference

Command	Description
`vibe login`	Authenticate with Vibe Assurance via browser
`vibe logout`	Clear stored credentials
`vibe setup-claude`	Configure Claude Code's MCP settings
`vibe mcp-server`	Start the MCP server (used by Claude Code)
`vibe --version`	Show CLI version
`vibe --help`	Show help and available commands

Troubleshooting

"Not authenticated" error

Run vibe login to authenticate. Your session may have expired.

"MCP server not found" in Claude Code

Run vibe setup-claude again, then restart Claude Code completely.

"ENOENT" or "command not found"

Ensure Node.js is installed and npm install -g @vibe-assurance/cli completed successfully.

Tools return empty results

Check that you have data in your Vibe Assurance account. Create some governance roles or artifacts via the web portal first.

Port 38274 already in use

Another vibe login process may be running. Close it and try again.

Manual Configuration (Advanced)

If vibe setup-claude doesn't work, you can manually configure Claude Code:

Edit Claude Code's MCP config

Add to your ~/.claude/mcp.json (or equivalent):

{
  "mcpServers": {
    "vibeassurance": {
      "command": "vibe",
      "args": ["mcp-server"]
    }
  }
}

Need Help?

If you encounter issues not covered here, reach out via our contact page or check the GitHub repository for known issues.