Featured

Deploy OpenClaw in 60 seconds — 20% off logoDeploy OpenClaw in 60 seconds — 20% off

Launch OpenClaw on Hostinger in about 60 seconds and keep your agent live 24/7. Our referral link gives you 20% off, no coupon code needed.

Launch on Hostinger
Run your Hermes agent on Hostinger, fully managed logoRun your Hermes agent on Hostinger, fully managed

Launch Hermes on Hostinger in one click, fully managed, no VPS knowledge needed. Use code ZACAARON10 for 10% off.

Launch on Hostinger
Crawl and scrape any site into clean data, 10% off logoCrawl and scrape any site into clean data, 10% off

Firecrawl crawls and scrapes any site into clean markdown for your agent. Get 1,000 free credits, and new users get 10% off their first purchase.

Try Firecrawl free
6,000+ web scrapers for your AI agent, start free logo6,000+ web scrapers for your AI agent, start free

Apify gives your agent live web data: 6,000+ prebuilt scrapers and actors, MCP-ready. Sign up free with $5 in usage credits.

Try Apify free
One API to scrape, enrich, and extract the internet. logoOne API to scrape, enrich, and extract the internet.

Context.dev gives your agents a single API to scrape, enrich, and extract live web data — no proxies, no parsers, no maintenance.

Start building free
SetupClaw: done-for-you OpenClaw for founders & exec teams logoSetupClaw: done-for-you OpenClaw for founders & exec teams

White-glove OpenClaw for founders and exec teams (4–50+ employees): we install, harden, integrate your tools, and maintain it — secured from day one.

Get it set up for you
SEO data APIs for your agent, $1 free credit logoSEO data APIs for your agent, $1 free credit

DataForSEO gives your agent live access to SERP results, keyword data, backlinks, and on-page SEO data through one API. New accounts get a $1 credit, good for up to 20,000 keyword or backlink lookups.

Try DataForSEO free
Reach 48,000+ AI builders

A flat monthly placement in front of developers actively installing AI tools. No lock-in, cancel anytime.

Advertise here

Works with

Claude CodeClaude DesktopCursorVS CodeClineCodex CLIOpenClaw+ any MCP client

Install to Claude Code

This server doesn't publish a one-line install command. Follow the setup in the source repository.

Summary

Helps debug conversion tracking issues across GoHighLevel, Meta CAPI, webhooks, and GTM by providing tools to fetch events, contacts, logs, and perform full analysis.

README.md

Smart Conversion Debugging MCP Server

An MCP server that helps debug conversion tracking issues across GoHighLevel, Meta CAPI, webhooks, and GTM.

Quick Start

# Install dependencies
npm install

# Test tools locally
node test.js

# Run interactive CLI agent
node agent.js

# Start MCP server (for AI client connections)
node index.js

Available Tools

| Tool | Description | |------|-------------| | getWebhookEvents | Returns stored webhook events | | getGHLContacts | Fetch contacts from GoHighLevel | | getMetaEvents | Returns Meta CAPI tracked events | | getGTMEvents | Returns frontend GTM events | | getSystemLogs | Returns error logs | | debugConversion | Full analysis with issues + fixes |

---

Connecting to MCP Clients

1. Claude Desktop

Edit your Claude Desktop config file:

Windows: %APPDATA%\Claude\claude_desktop_config.json

macOS: ~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "conversion-debugger": {
      "command": "node",
      "args": ["D:/first mcp server/index.js"],
      "env": {
        "USE_MOCK_DATA": "true"
      }
    }
  }
}

Restart Claude Desktop after saving. You'll see the tools available in the chat.

---

2. VS Code with GitHub Copilot

Add to your VS Code settings.json or workspace settings:

{
  "github.copilot.chat.mcpServers": {
    "conversion-debugger": {
      "command": "node",
      "args": ["D:/first mcp server/index.js"],
      "env": {
        "USE_MOCK_DATA": "true"
      }
    }
  }
}

Or create .vscode/mcp.json in your workspace:

{
  "servers": {
    "conversion-debugger": {
      "command": "node",
      "args": ["${workspaceFolder}/index.js"],
      "env": {
        "USE_MOCK_DATA": "true"
      }
    }
  }
}

---

3. Cursor IDE

Add to Cursor settings (~/.cursor/mcp.json or project .cursor/mcp.json):

{
  "mcpServers": {
    "conversion-debugger": {
      "command": "node",
      "args": ["D:/first mcp server/index.js"],
      "env": {
        "USE_MOCK_DATA": "true"
      }
    }
  }
}

---

4. Continue.dev

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

{
  "experimental": {
    "modelContextProtocolServers": [
      {
        "transport": {
          "type": "stdio",
          "command": "node",
          "args": ["D:/first mcp server/index.js"]
        }
      }
    ]
  }
}

---

5. Custom MCP Client (Node.js)

import { Client } from "@modelcontextprotocol/sdk/client/index.js";
import { StdioClientTransport } from "@modelcontextprotocol/sdk/client/stdio.js";
import { spawn } from "child_process";

const transport = new StdioClientTransport({
  command: "node",
  args: ["D:/first mcp server/index.js"],
});

const client = new Client({ name: "my-client", version: "1.0.0" });
await client.connect(transport);

// List available tools
const tools = await client.listTools();
console.log(tools);

// Call a tool
const result = await client.callTool({
  name: "debugConversion",
  arguments: {},
});
console.log(result);

await client.close();

---

Environment Variables

Copy .env.example to .env and configure:

# Use mock data (set to false for live API calls)
USE_MOCK_DATA=true

# GoHighLevel
GHL_API_KEY=your_api_key
GHL_LOCATION_ID=your_location_id

# Meta CAPI
META_ACCESS_TOKEN=your_access_token
META_PIXEL_ID=your_pixel_id

---

Example AI Prompts

Once connected to an MCP client, try these prompts:

  1. "Debug my conversion tracking"
  • The AI will call debugConversion and explain the issues
  1. "Show me all GHL contacts from today"
  • Calls getGHLContacts with date filters
  1. "Compare webhook events with Meta events"
  • Calls multiple tools and cross-references data
  1. "Why are some conversions not reaching Meta?"
  • Full debugging workflow with root cause analysis

---

Project Structure

first mcp server/
├── index.js              # MCP server entry point
├── agent.js              # Interactive CLI agent
├── test.js               # Tool testing script
├── package.json
├── .env.example
├── config/
│   └── env.js            # Environment configuration
├── clients/
│   ├── httpClient.js     # HTTP utilities
│   ├── ghlClient.js      # GoHighLevel API client
│   └── metaClient.js     # Meta CAPI client
├── data/
│   ├── mockData.js       # Mock data for testing
│   └── dataProvider.js   # Live/mock data switching
└── tools/
    ├── utils.js
    ├── getWebhookEvents.js
    ├── getGHLContacts.js
    ├── getMetaEvents.js
    ├── getGTMEvents.js
    ├── getSystemLogs.js
    └── debugConversion.js

See related servers & alternatives →

Related MCP servers

Browse all →

Related guides

Hand-picked reading to help you choose and use Browser & Scraping servers.