Skip to main content
Glama

Ziggy MCP

A Model Context Protocol (MCP) server that connects Claude AI to Google Sheets for automated revenue tracking, lead management, and business operations.

Features

  • πŸ“Š Dashboard: Real-time revenue metrics and KPIs

  • 🎯 Lead Pipeline: Track prospects from first contact to close

  • πŸ“§ Gmail Integration: Search emails and automate outreach

  • πŸ“… Calendar Sync: Track meetings and follow-ups

  • πŸ“ Knowledge Matrix: Development log with timestamp tracking

  • βœ… Task Management: Prioritize and track project tasks

  • πŸ“ˆ Analytics: Daily metrics and performance tracking

Related MCP server: Revenue Engine MCP

Prerequisites

  • Node.js 18.0.0 or higher

  • Google Account with Sheets and Gmail access

  • Claude Desktop or compatible MCP client

  • Google Apps Script (for backend API)

  • Playwright (for browser automation)

Installation

1. Clone the Repository

git clone https://github.com/yourusername/ziggy-mcp.git
cd ziggy-mcp

2. Install Dependencies

npm run setup
# This installs Node packages AND Playwright browsers

Manual alternative:

npm install
npx playwright install chromium

3. Set Up Google Sheets Backend

  1. Create a new Google Sheet

  2. Go to Extensions > Apps Script

  3. Delete any existing code

  4. Copy all files from /apps-script directory:

    • Code.js - Sheet setup script

    • API.js - Main API handlers

    • calendarSync.js - Calendar integration

    • appsscript.json - Manifest

  5. Click Save (disk icon)

  6. Click Run > setupRevenueEngine

  7. Authorize the script when prompted

  8. Wait 30-60 seconds for completion

  9. Deploy as web app:

    • Click Deploy > New deployment

    • Type: Web app

    • Execute as: Me

    • Who has access: Anyone

    • Click Deploy

    • Copy the Web app URL

4. Configure the MCP Server

Edit index.js and update the API URL:

const API_URL = "YOUR_GOOGLE_APPS_SCRIPT_WEB_APP_URL";

5. Connect to Claude Desktop

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

{
  "mcpServers": {
    "ziggy": {
      "command": "node",
      "args": ["/absolute/path/to/ziggy-mcp/index.js"]
    }
  }
}

Replace /absolute/path/to/ziggy-mcp/ with your actual installation path.

6. Restart Claude Desktop

Quit and reopen Claude Desktop to load the MCP server.


Browser Automation Setup

Setting Up Authenticated Sessions

For Upwork, LinkedIn, and other platforms:

Step 1: Open browser in visible mode

Open Upwork in browser with visible mode

Step 2: I'll open a browser window - YOU log in manually

Step 3: Save the session

Save browser session as "upwork"

Step 4: Test it

Browse upwork.com using saved session

Supported Platforms

  • βœ… Upwork - Job search, proposal submission

  • βœ… LinkedIn - Profile research, connection requests

  • βœ… Any website - Custom scraping and automation

Security Notes

  • Sessions stored locally in sessions/ folder

  • NEVER commit session files to git

  • Sessions contain your auth tokens

  • Expire after ~30 days

  • Re-authenticate when needed


Usage

Basic Commands

Get Dashboard:

Show me my revenue dashboard

View Pipeline:

What leads are in my pipeline?

Add a Lead:

Add a new lead: Acme Corp, contact John Smith, email john@acme.com

Check Gmail:

Search my unread emails

Log Development Work:

Log to knowledge matrix: Fixed authentication bug in Gmail integration [45m]

Knowledge Matrix

The Knowledge Matrix is a structured development log that tracks:

  • πŸ› Bugs & Fixes - Issues and resolutions

  • ✨ Features Added - New functionality

  • πŸ§ͺ Testing Results - Test outcomes

  • 🎯 Decisions & Direction - Strategic choices

  • πŸ“š Documentation Updates - Doc changes

  • πŸš€ Next Session Goals - Future work

Write Entry:

Write matrix entry for Bugs & Fixes: "3:45pm EST πŸ›[BUG-001] Fixed Gmail auth timeout [30m]"

Query Matrix:

Search matrix for "authentication"

Daily Summary:

Generate matrix summary for today

Browser Automation

Take Screenshot:

Take a screenshot of competitor-site.com

Extract Data:

Extract pricing from acme.com/pricing

Fill Form:

Fill the contact form at example.com with lead data for John Doe

Research:

Browse to linkedin.com/company/acme and extract company info

Automated Outreach (after session setup):

Search Upwork for "web automation" jobs and show top 5

Project Structure

ziggy-mcp/
β”œβ”€β”€ index.js                 # Main MCP server
β”œβ”€β”€ package.json            # Node dependencies
β”œβ”€β”€ browser/                # Browser automation
β”‚   β”œβ”€β”€ playwright.js      # Core browser functions
β”‚   β”œβ”€β”€ upwork.js          # Upwork automation
β”‚   └── linkedin.js        # LinkedIn automation
β”œβ”€β”€ apps-script/            # Google Apps Script files
β”‚   β”œβ”€β”€ Code.js            # Sheet setup
β”‚   β”œβ”€β”€ API.js             # API endpoints
β”‚   β”œβ”€β”€ calendarSync.js    # Calendar integration
β”‚   └── appsscript.json    # Manifest
β”œβ”€β”€ sessions/               # Saved browser sessions (gitignored)
β”œβ”€β”€ screenshots/            # Captured screenshots (gitignored)
β”œβ”€β”€ docs/                   # Documentation
β”‚   β”œβ”€β”€ MATRIX.md          # Knowledge Matrix guide
β”‚   β”œβ”€β”€ BUG-TRACKING.md    # Bug tracking system
β”‚   └── BROWSER-GUIDE.md   # Browser automation guide
└── README.md              # This file

Security & Privacy

  • All data stored in your Google Sheets

  • API calls authenticated through Google Apps Script

  • No external databases or third-party services

  • File system access restricted to project directory

  • Gmail read-only access (send requires explicit approval)

Troubleshooting

MCP Server Not Connecting

  1. Check Claude Desktop config path is correct

  2. Verify Node.js version: node --version (should be β‰₯18.0.0)

  3. Check console: Cmd+Shift+I in Claude Desktop

  4. Verify API_URL is set correctly in index.js

Google Apps Script Issues

  1. Ensure script is deployed as web app

  2. Check execution permissions (should be "Anyone")

  3. Re-authorize if needed: Run > setupRevenueEngine

  4. Check Apps Script logs: View > Logs

Gmail Integration

  1. Ensure Gmail API is enabled in Apps Script

  2. Check OAuth scopes in appsscript.json

  3. Re-authorize if permissions changed

Development

Running Locally

node index.js

Managing Apps Script

Install clasp for local Apps Script development:

npm install -g @google/clasp
clasp login
clasp pull  # Download from Google
clasp push  # Upload to Google

Debugging

Enable debug logging in index.js:

const DEBUG = true;

Logs written to debug.log in project directory.

Roadmap

  • Add Slack integration

  • Export reports to PDF

  • AI-powered lead scoring

  • Automated follow-up reminders

  • Invoice generation

  • Team collaboration features

Contributing

  1. Fork the repository

  2. Create a feature branch: git checkout -b feature/amazing-feature

  3. Commit changes: git commit -m 'Add amazing feature'

  4. Push to branch: git push origin feature/amazing-feature

  5. Open a Pull Request

License

MIT License - see LICENSE file for details

Support

Acknowledgments


Made with ❀️ for solopreneurs and small teams

Available Tools

13 tools
add_leadC

Add a new lead to the pipeline

Inputs: companyName (required), notes, contactName, contactEmail, +1 more.

browse_pageB

Navigate to URL and return page content

Inputs: url (required), session.

get_dashboardB

Get current revenue dashboard with all key metrics

Inputs: no named parameters.

get_email_contentC

Get full content of an email thread

Inputs: threadId (required).

get_pipelineA

Get all leads in the pipeline

Inputs: no named parameters.

query_matrixC

Search Knowledge Matrix

Inputs: keyword (required).

read_fileB

Read file contents

Inputs: path (required).

save_browser_sessionD

Save browser session

Inputs: sessionName (required).

search_gmailC

Search Gmail inbox

Inputs: query, maxResults.

take_screenshotC

Capture screenshot of webpage

Inputs: url (required), filename.

update_leadC

Update an existing lead

Inputs: leadId (required), notes, status.

write_fileD

Write file contents

Inputs: path (required), content (required).

write_matrix_entryC

Write entry to Knowledge Matrix

Inputs: topic (required), content (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    C2.8/5.0

    Scored across 13 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action: dashboard metrics vs. pipeline leads, Gmail search vs. email content, knowledge matrix write vs. query, and browser vs. file operations. No two tools appear to perform the same function, and their descriptions make the boundaries clear.

    Naming Consistency5/5

    All tool names follow a consistent lower_snake_case verb_noun pattern, such as get_dashboard, add_lead, search_gmail, write_matrix_entry, and read_file. There are no mixed conventions, vague one-word names, or irregular verb styles.

    Tool Count4/5

    With 13 tools, the count is well within a reasonable range for a multi-purpose assistant spanning CRM, email, knowledge, browser, and file domains. The set is broad but each tool earns its place, though the wide scope keeps it from feeling tightly focused.

    Completeness3/5

    Core workflows are covered for each domain, but there are notable gaps: no send/reply for Gmail, no delete/list for files or leads, and limited browser interaction beyond navigation and screenshots. Agents can complete basic tasks but may hit dead ends in fuller lifecycle workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • -
      license
      Not graded
      quality
      Not graded
      maintenance
      Connects Claude AI to GoHighLevel CRM, enabling comprehensive automation across 269+ tools including contact management, messaging, sales pipeline, appointments, marketing, and e-commerce operations.
      16 npm
      -