Cazon MCP Server

Give Claude, Copilot, and Cursor an engineering manager. This MCP server connects AI coding assistants to Cazon's error intelligence, enabling them to triage your bug backlog by impact, find patterns, and prioritize what to fix first.

Features

• 🚨 Intelligent Triage - Categorizes errors by impact (Critical/High/Medium/Low) with occurrence counts, trends, and user impact
• 🔍 Error Analysis - Get AI-powered debugging suggestions for any error
• 📊 Pattern Recognition - Discover common error patterns across your codebase
• 🔎 Similar Errors - Find previously seen similar errors with solutions
• 📖 Rich Context - Full stack traces, impact scores, affected users, and status tracking
• 🤖 AI Integration - Works with Claude Desktop, Continue.dev, and other MCP clients

Installation

From npm (recommended):

npm install -g @cazon/mcp-server

From source:

cd mcp-server
npm install
npm run build

Configuration

Create a .env file:

CAZON_API_KEY=your-cazon-api-key
CAZON_BASE_URL=https://cazon.dev  # or http://localhost:3030 for local
**After installing via npm:**

Add to your Claude Desktop config (`~/Library/Application Support/Claude/claude_desktop_config.json` on macOS):

```json
{
  "mcpServers": {
    "cazon": {
      "command": "cazon-mcp",
      "env": {
        "CAZON_API_KEY": "your-api-key-here",
        "CAZON_BASE_URL": "https://cazon.dev"
      }
    }
  }
}

If running from source:

Get your API key from cazon.dev/dashboard.

Usage

Claude Desktop

Add to your Claude Desktop config (~/Library/Application Support/Claude/claude_desktop_config.json on macOS):

{
  "mcpServers": {
    "cazon": {
      "command": "node",
      "args": ["/absolute/path/to/cazon/mcp-server/dist/index.js"],
      "env": {
        "CAZON_API_KEY": "your-api-key-here",
        "CAZON_BASE_URL": "https://cazon.dev"
      }
    }
  }
}

Restart Claude Desktop. You should see Cazon resources and tools available.

Continue.dev

Add to your Continue config (~/.continue/config.json):

{
  "mcpServers": [
    {
      "name": "cazon",
      "command": "node",
      "args": ["/absolute/path/to/cazon/mcp-server/dist/index.js"],
      "env": {
        "CAZON_API_KEY": "your-api-key-here"
      }
    }
  ]
}

Direct Usage (stdio)

npm run dev

MCP Resources

Resources provide read-only context for AI assistants:

cazon://history/recent

Recent errors captured by Cazon with their analysis

cazon://patterns/common

Frequently occurring error patterns in your codebase

cazon://errors/{errorId}

Detailed analysis of a specific error

MCP Tools

Tools are actions AI assistants can invoke:

cazon_triage_errors ⭐ NEW

Intelligent error prioritization - Analyzes all errors and categorizes them by urgency

Returns a formatted report with:

• 🚨 Critical - Impact ≥80, Occurrences ≥50, or Increasing trend (fix immediately)
• 🔴 High - Impact 60-80 (fix this sprint)
• 🟡 Medium - Impact 30-60 (schedule for next sprint)
• 🟢 Low - Impact <30 (backlog)

Each error includes:

• Impact score (0-100)
• Occurrence count
• Affected user count
• Trend indicator (📈 Increasing, 📉 Decreasing, ➡️ Stable)
• Stack location
• AI-generated suggestion
• Error ID for deep linking

Parameters: None

Example output:

## 🚨 CRITICAL (Fix Immediately)

### 1. TypeError: Cannot read property 'length' of undefined
- **Impact Score:** 87/100 (critical)
- **Occurrences:** 45
- **Affected Users:** 15
- **Trend:** 📈 Increasing
- **Location:** checkout.js:156
- **Suggestion:** Add null check before accessing array properties
- **Error ID:** abc123...

## Key Insights
- 2 errors with increasing frequency (potential regressions)
- 1 high-occurrence errors (≥50 occurrences)
- 3 errors affecting multiple users

cazon_analyze_error

Analyze an error and get debugging suggestions

Parameters:

• errorMessage (string, required) - The error message
• stack (string, optional) - Stack trace
• metadata (object, optional) - Additional context

Example:

{
  "errorMessage": "TypeError: Cannot read property 'length' of undefined",
  "stack": "at calculateTotal (app.js:42:15)",
  "metadata": {
    "environment": "development"
  }
}

cazon_find_similar

Find similar errors from your history

Parameters:

• errorMessage (string, required) - Error to find similarities for

cazon_get_patterns

Get common error patterns from your codebase

Parameters: None

Development

# Watch mode for development
npm run watch

# In another terminal
npm run dev

# Build for production
npm run build

Example Conversations

Once configured, you can ask Claude:

"Triage my errors and tell me what to fix first"

Claude will use cazon_triage_errors to analyze all errors, categorize by priority, and give you a report like an engineering manager would.

"What are the most critical bugs affecting users?"

Claude accesses the cazon://history/recent resource which includes impact scores, affected user counts, and trends.

"I'm getting a TypeError: Cannot read property 'length' of undefined. Can you help?"

Claude will use cazon_analyze_error to get AI-powered debugging suggestions.

"What are the most common errors in my codebase?"

Claude will use cazon_get_patterns to show frequently occurring patterns.

"Have I seen this error before: 'ReferenceError: foo is not defined'?"

Claude will use cazon_find_similar to search your error history.

Architecture

┌─────────────────────────────────────────────────────────────┐
│  AI Assistant (Claude, Continue.dev, etc.)                  │
└────────────────────┬────────────────────────────────────────┘
                     │ MCP Protocol (stdio)
                     ▼
┌─────────────────────────────────────────────────────────────┐
│  Cazon MCP Server                                            │
│  • Resources (read-only context)                             │
│  • Tools (actions)                                           │
└────────────────────┬────────────────────────────────────────┘
                     │ HTTP/REST
                     ▼
┌─────────────────────────────────────────────────────────────┐
│  Cazon API (cazon.dev)                                       │
│  • Pattern matching                                          │
│  • AI analysis                                               │
│  • Error storage                                             │
└─────────────────────────────────────────────────────────────┘

Troubleshooting

Server not appearing in Claude Desktop

1. Check the config path is correct (absolute path)
2. Verify API key is valid
3. Look at Claude Desktop logs: ~/Library/Logs/Claude/mcp*.log

Connection errors

• Verify CAZON_BASE_URL is correct
• Check API key has proper permissions
• Ensure Cazon backend is running (if using localhost)

TypeScript errors

npm run build

Fix any compilation errors before running.

License

MIT

Support

• Documentation: cazon.dev/docs