Setup Guide
Configure VertaaUX MCP Server in Claude Desktop, Cursor, Continue.dev, and other MCP clients
Setup Guide
Configure the VertaaUX MCP Server in your AI assistant. This guide covers setup for all major MCP clients.
Prerequisites: Node.js 18+ and a VertaaUX API key. Get your key from the dashboard.
Claude Desktop (Recommended)
Claude Desktop provides the best integration for the VertaaUX MCP Server.
Configuration File Location
~/Library/Application Support/Claude/claude_desktop_config.jsonCreate the directory if it doesn't exist:
mkdir -p ~/Library/Application\ Support/Claude%APPDATA%\Claude\claude_desktop_config.jsonTypically at:
C:\Users\<username>\AppData\Roaming\Claude\claude_desktop_config.json~/.config/Claude/claude_desktop_config.jsonAdd VertaaUX Server
Add this configuration to your claude_desktop_config.json:
{
"mcpServers": {
"vertaaux": {
"command": "npx",
"args": ["@vertaaux/mcp-server"],
"env": {
"VERTAAUX_API_KEY": "vx_live_your_key_here"
}
}
}
}If you have existing MCP servers, add VertaaUX alongside them:
{
"mcpServers": {
"existing-server": {
"command": "npx",
"args": ["other-mcp-server"]
},
"vertaaux": {
"command": "npx",
"args": ["@vertaaux/mcp-server"],
"env": {
"VERTAAUX_API_KEY": "vx_live_your_key_here"
}
}
}
}Restart Claude Desktop
After saving the configuration:
- macOS: Press Cmd+Q to fully quit, then reopen
- Windows: Right-click the tray icon > Quit, then reopen
- Linux: Close all windows and relaunch
Simply closing the window isn't enough. You must fully quit the application for config changes to take effect.
Verify Installation
Ask Claude:
"What MCP tools do you have available?"
You should see VertaaUX tools listed, including audit_url, suggest_fix, and others.
Cursor
Cursor IDE supports MCP servers through its extension system.
Configuration
- Open Cursor Settings (Cmd/Ctrl + ,)
- Navigate to Extensions > MCP
- Click Add Server
Enter this configuration:
{
"name": "vertaaux",
"command": "npx",
"args": ["@vertaaux/mcp-server"],
"env": {
"VERTAAUX_API_KEY": "vx_live_your_key_here"
}
}Alternative: Manual Config
Add to your Cursor configuration file:
{
"servers": [
{
"name": "vertaaux",
"command": "npx",
"args": ["@vertaaux/mcp-server"],
"env": {
"VERTAAUX_API_KEY": "vx_live_your_key_here"
}
}
]
}Continue.dev
Continue.dev is an open-source AI coding assistant that supports MCP.
Configuration
Add VertaaUX to your ~/.continue/config.json:
{
"mcpServers": [
{
"name": "vertaaux",
"command": "npx",
"args": ["@vertaaux/mcp-server"],
"env": {
"VERTAAUX_API_KEY": "vx_live_your_key_here"
}
}
]
}Restart the Continue extension after updating the configuration.
Generic MCP Client
For any MCP-compatible client using stdio transport:
Server Command
npx @vertaaux/mcp-serverTransport
- Type: stdio (standard input/output)
- Protocol: MCP 1.0
Required Environment
| Variable | Required | Description |
|---|---|---|
VERTAAUX_API_KEY | Yes | Your API key (starts with vx_live_ or vx_test_) |
VERTAAUX_API_BASE | No | Custom API endpoint (default: https://vertaaux.ai/api/v1) |
Running Locally
If you want to run the server directly:
VERTAAUX_API_KEY=vx_live_xxx npx @vertaaux/mcp-serverThe server communicates via stdin/stdout using JSON-RPC messages.
Environment Variables
| Variable | Default | Description |
|---|---|---|
VERTAAUX_API_KEY | (required) | Your VertaaUX API key |
VERTAAUX_API_BASE | https://vertaaux.ai/api/v1 | Custom API base URL |
DEBUG | false | Enable debug logging |
Using Different Environments
For staging/test environments:
{
"mcpServers": {
"vertaaux-staging": {
"command": "npx",
"args": ["@vertaaux/mcp-server"],
"env": {
"VERTAAUX_API_KEY": "vx_test_staging_key",
"VERTAAUX_API_BASE": "https://staging.vertaaux.ai/api/v1"
}
}
}
}Troubleshooting
Server Not Starting
Symptoms: No tools available, "MCP server not responding"
Solutions:
-
Verify Node.js 18+ is installed:
node --version # Should be v18.x or higher -
Test the server manually:
VERTAAUX_API_KEY=vx_live_xxx npx @vertaaux/mcp-server --version -
Check for npx caching issues:
npx --clear-cache
API Key Issues
Symptoms: "Unauthorized" or "Invalid API key" errors
Solutions:
-
Verify key format: Should start with
vx_live_orvx_test_ -
Check key is set correctly (no extra spaces/quotes):
"env": { "VERTAAUX_API_KEY": "vx_live_abc123" // No quotes around the key } -
Verify key is active in your dashboard
Permission Errors
Symptoms: "EACCES" or permission denied errors
Solutions:
-
Ensure npx has execute permissions:
which npx # Verify npx location ls -la $(which npx) # Check permissions -
Try using absolute path:
{ "command": "/usr/local/bin/npx", "args": ["@vertaaux/mcp-server"] }
Tools Not Appearing
Symptoms: Server connects but no tools show up
Solutions:
-
Fully restart your client application (not just close window)
-
Check server logs for initialization errors
-
Verify the API key has audit permissions enabled
Verifying Setup
After configuration, verify everything works:
Step 1: Check Tools
Ask your AI assistant:
"What VertaaUX tools do you have available?"
Expected response should list: audit_url, get_findings, explain_finding, suggest_fix, etc.
Step 2: Test Audit
"Run a basic audit of https://example.com"
Should return audit results with findings.
Step 3: Test Fix Suggestion
If the audit has findings:
"Suggest a fix for the first finding"
Should return a code patch with confidence score.
Multiple Environments
You can configure multiple VertaaUX servers for different environments:
{
"mcpServers": {
"vertaaux-prod": {
"command": "npx",
"args": ["@vertaaux/mcp-server"],
"env": {
"VERTAAUX_API_KEY": "vx_live_production_key"
}
},
"vertaaux-staging": {
"command": "npx",
"args": ["@vertaaux/mcp-server"],
"env": {
"VERTAAUX_API_KEY": "vx_test_staging_key",
"VERTAAUX_API_BASE": "https://staging.vertaaux.ai/api/v1"
}
}
}
}Then specify which to use:
"Using the staging VertaaUX server, audit https://staging.mysite.com"
Related
- Quickstart - Get your first AI-suggested fix
- Tools Reference - All available MCP tools
- API Authentication - API key management
Was this page helpful?