@vibe-assurance/cli

Connect AI coding agents to your Vibe Assurance governance platform via the Model Context Protocol (MCP).

Installation

npm install -g @vibe-assurance/cli

Quick Start

1. Login to Vibe Assurance:

   vibe login

   This opens your browser for authentication.

2. Configure your MCP client:

   vibe setup-claude

   This adds the Vibe Assurance MCP server to your MCP client configuration.

3. Restart your AI agent and start using governance tools!

CLI Commands

| Command | Description | |---------|-------------| | vibe login | Authenticate with Vibe Assurance | | vibe logout | Clear stored credentials | | vibe whoami | Show current authenticated user | | vibe mcp-server | Start the MCP server (used by AI coding agents) | | vibe setup-claude | Configure MCP client to use Vibe Assurance | | vibe --version | Show CLI version |

Project Commands

| Command | Description | |---------|-------------| | vibe projects | List your accessible projects | | vibe project current | Show current project | | vibe project select | Switch to a different project |

Environment Commands

| Command | Description | |---------|-------------| | vibe env | Show current environment | | vibe env list | List available environments | | vibe env prod | Switch to production |

MCP Tools

Once configured, your AI coding agent has access to these tools:

Context & Templates

| Tool | Description | |------|-------------| | vibe_get_context | Get your governance context (CRs, risks, vulns, next CR ID) | | vibe_get_template | Get a document template | | vibe_list_templates | List available templates |

Artifacts (Governance Documents)

| Tool | Description | |------|-------------| | vibe_store_artifact | Store a created document (CR, risk, vulnerability, plan, etc.) | | vibe_update_artifact | Update an existing artifact | | vibe_append_file | Safely add a file to an artifact without replacing others | | vibe_list_artifacts | List your stored artifacts | | vibe_get_artifact | Get a specific artifact by ID | | vibe_delete_artifact | Delete an artifact |

Artifact Types

| Type | Description | Example ID | |------|-------------|------------| | CR | Change Requests | CR-2026-051 | | RISK | Risk Register Entries | RISK-001 | | VULNERABILITY | Security Vulnerabilities | VUL-059 | | REPORT | Security/Audit Reports | RPT-2026-001 | | PLAN | Strategic & Technical Plans | PLAN-2026-002 | | CONFIG | Configuration Documentation | CFG-001 | | ARCHITECTURE | Architecture Documentation | ARCH-001 |

Strategic Plans

| Tool | Description | |------|-------------| | vibe_get_strategic_plans | List strategic plans (filter by status) | | vibe_store_plan | Create a new strategic plan | | vibe_update_plan | Update plan content, title, or metadata | | vibe_update_plan_status | Update plan status (Draft/Active/Completed/Closed) | | vibe_delete_plan | Delete a strategic plan |

Risk Register

| Tool | Description | |------|-------------| | vibe_get_risk_register | Get project's risk register | | vibe_add_risk | Add a new risk with auto-calculated severity | | vibe_get_risk | Get specific risk by ID | | vibe_update_risk | Update risk status, treatment, or reassess |

Vulnerability Register

| Tool | Description | |------|-------------| | vibe_get_vulnerability_register | Get project's vulnerability register | | vibe_add_vulnerability | Add vulnerability with OWASP validation | | vibe_get_vulnerability | Get specific vulnerability by ID | | vibe_update_vulnerability | Update vulnerability status or link to CR |

Example Session

User: Create a change request for adding user authentication

AI Agent: I'll help you create a change request. Let me get your context first.

[Calls vibe_get_context]
[Calls vibe_get_template("change-request")]

Based on your governance context, your next CR ID is CR-2026-001.

[Creates the CR documents...]
[Calls vibe_store_artifact(...)]

Your CR-2026-001 has been stored! View it at:
https://vibeassurance.app/governance-changes

Configuration

Environment Variables

| Variable | Description | |----------|-------------| | VIBE_API_URL | Override API URL (for development) |

Credential Storage

Credentials are stored securely using:

• macOS: Keychain Access
• Windows: Credential Manager
• Linux: libsecret (if available)

If the system keychain is unavailable, credentials fall back to ~/.vibe/credentials.json with restricted permissions (600).

Requirements

• Node.js 18 or later
• Vibe Assurance account - Sign up
• MCP-compatible AI agent (e.g., Claude Code, Gemini CLI, or any MCP client)

Troubleshooting

"Not authenticated" error

Run vibe login to authenticate. If you see this error during MCP server startup, your session may have expired.

MCP server not connecting

1. Run vibe setup-claude again
2. Restart your AI agent completely
3. Check that vibe command is in your PATH

"Port 38274 is already in use"

Another vibe login process is running. Wait for it to complete or terminate it.

Keychain access denied

The CLI will automatically fall back to file-based storage. This is secure but less convenient.

On Linux, install libsecret for keychain support:

# Ubuntu/Debian
sudo apt-get install libsecret-1-dev

# Fedora
sudo dnf install libsecret-devel

Debug mode

To see detailed logs:

DEBUG=vibe* vibe mcp-server

Uninstalling

# Remove the CLI
npm uninstall -g @vibe-assurance/cli

# Clear stored credentials
vibe logout

# Or manually:
rm -rf ~/.vibe/

Then remove the MCP configuration from your AI agent's config file.

Security

• Credentials are stored in the OS keychain when available
• Tokens are never logged or exposed in console output
• All API communication uses HTTPS
• Tokens auto-refresh when expired

License

MIT

Links

• Vibe Assurance - AI Governance Platform
• MCP Protocol - Model Context Protocol specification