How to Use MCP to Debug Webhooks with AI

You: "Why is my stripe-production endpoint failing?"

AI: I'll check the recent logs for your stripe-production endpoint.

    Found 14 failed deliveries in the last 24 hours. All return HTTP 422 
    from your target URL https://api.myapp.com/webhooks/stripe.

    Response body from your server:
    { "error": "Invalid signature", "expected": "sha256=...", "received": "sha256=..." }

    The HMAC signatures don't match. This usually means:
    1. Your signing secret in code doesn't match the one in Mitte
    2. The request body is being modified before verification (e.g., JSON.parse then stringify)

    Recommendation: Make sure you verify the signature against the RAW request body, 
    not the parsed JSON. Here's the fix for your Express handler:

    // ❌ Wrong — body has been parsed 
    app.post('/webhooks/stripe', express.json(), (req, res) => {
      verify(JSON.stringify(req.body), sig, secret)  
    })

    // ✅ Correct — use raw body
    app.post('/webhooks/stripe', express.raw({type: 'application/json'}), (req, res) => {
      verify(req.body, sig, secret)  
    })

    Want me to send a test event to verify after you apply the fix?

{
  "servers": {
    "mitte": {
      "url": "https://mitte.run/api/mcp",
      "headers": {
        "Authorization": "Bearer mk_your_api_key_here"
      }
    }
  }
}

{
  "mcpServers": {
    "mitte": {
      "url": "https://mitte.run/api/mcp",
      "headers": {
        "Authorization": "Bearer mk_your_api_key_here"
      }
    }
  }
}

{
  "mcpServers": {
    "mitte": {
      "url": "https://mitte.run/api/mcp",
      "headers": {
        "Authorization": "Bearer mk_your_api_key_here"
      }
    }
  }
}

You: "All my webhook deliveries are failing. What's going on?"

AI: Let me check your dashboard summary and endpoints.

    Dashboard Summary (last 24h):
    - Total events: 342
    - Success: 0 (0%)  
    - Failed: 342 (100%)
    
    All 3 endpoints are affected. Checking logs for your most active endpoint...
    
    All failures show: "ECONNREFUSED 10.0.1.5:8080"
    
    Your target server at 10.0.1.5:8080 is unreachable. This is a private IP — 
    is your backend server down or was the URL misconfigured?
    
    Your endpoints are targeting:
    1. stripe-prod → http://10.0.1.5:8080/webhooks/stripe
    2. github-deploy → http://10.0.1.5:8080/webhooks/github  
    3. shopify-orders → http://10.0.1.5:8080/webhooks/shopify
    
    These look like internal IPs. If you recently migrated to a new server, 
    you'll need to update all target URLs.
    
    Want me to update them to a new URL?

You: "My Shopify endpoint is flaky — sometimes it works, sometimes it doesn't"

AI: I'll analyze recent logs for your shopify-orders endpoint.

    Last 50 deliveries:
    - 38 succeeded (76%)
    - 12 failed (24%)
    
    Pattern: All failures have response time > 29,500ms and return HTTP 504 (Gateway Timeout).
    Successful deliveries average 2.3 seconds response time.
    
    Your server is timing out on ~24% of requests. The failures correlate with 
    larger payload sizes (>50KB) — specifically bulk order webhooks from Shopify.
    
    Recommendations:
    1. Return 200 immediately, process the webhook async via a queue
    2. If you're doing DB writes synchronously, batch them
    3. Consider using Mitte's body transform to extract only the fields you need,
       reducing payload processing time
    
    Example transform to extract just order essentials:
    ({ body }) => ({
      orderId: body.id,
      email: body.email,
      total: body.total_price,
      items: body.line_items.map(i => ({ sku: i.sku, qty: i.quantity }))
    })
    
    Want me to add this transform to your endpoint?

You: "I need to start receiving GitHub webhooks for my repo. Set it up."

AI: I'll create a new endpoint and guide you through GitHub configuration.

    ✅ Created endpoint "github-webhooks" 
    URL: https://hook.mitte.run/e/gh_a1b2c3d4

    Now configure GitHub:
    1. Go to your repo → Settings → Webhooks → Add webhook
    2. Payload URL: https://hook.mitte.run/e/gh_a1b2c3d4
    3. Content type: application/json
    4. Secret: (generate one and add it to Mitte as a signing secret)
    5. Events: Choose "Send me everything" or select specific events
    
    Common events to select:
    - push (code pushes)
    - pull_request (PRs opened/merged)
    - issues (issues created/closed)
    - release (new releases)
    
    Want me to send a test event to verify the endpoint is working?

You: "What's my webhook usage looking like? Am I near any limits?"

AI: Here's your current plan usage:

    Plan: Pro ($12/mo)
    
    Endpoints: 7 / Unlimited ✅
    Events this month: 34,521 / 50,000 (69%) ⚠️
    Log retention: 30 days
    AI features: Enabled
    
    At your current rate (~1,640 events/day), you'll hit 50,000 
    around day 30 of your billing cycle. You're cutting it close.
    
    Your most active endpoints:
    1. stripe-prod: 18,240 events (53%)
    2. shopify-orders: 12,103 events (35%)
    3. github-deploy: 3,891 events (11%)
    4. Others: 287 events (1%)
    
    If you need headroom, consider filtering out webhook event types 
    you don't actually process to reduce volume.

❌ "Something's wrong with my webhooks"
✅ "Why are deliveries failing on my stripe-prod endpoint since yesterday?"

❌ "Show me the logs"
✅ "Analyze my recent failures and tell me what's going wrong"

❌ "What should I name the new endpoint?"
✅ "Create a new endpoint for Stripe webhooks targeting https://api.myapp.com/hooks/stripe"

"Create an endpoint for GitHub, send a test event, then show me the log"