Skip to main content
Glama

Revenue Engine MCP

A Model Context Protocol (MCP) server that connects Claude AI to Google Sheets, Gmail, and Calendar for comprehensive revenue tracking and business management.

Features

  • πŸ“Š Revenue Dashboard - Real-time tracking of leads, revenue, and metrics

  • πŸ”„ Lead Pipeline Management - Track leads from contact to close

  • πŸ“§ Gmail Integration - Search, read, and send emails

  • πŸ“… Calendar Integration - Manage meetings and schedules

  • βœ… Task Management - Track tasks and time

  • πŸ“ Knowledge Matrix - Structured documentation with automated analysis

  • πŸ› Bug Tracking - UID-based bug tracking system

  • πŸ“‚ File Operations - Read, write, and edit local files

Related MCP server: GoHighLevel MCP Server

Installation

Prerequisites

  • Node.js >= 18.0.0

  • Google Account with access to Sheets, Gmail, and Calendar

  • Claude Desktop app

Setup

  1. Clone the repository

git clone https://github.com/YOUR_USERNAME/revenue-engine-mcp.git
cd revenue-engine-mcp
  1. Install dependencies

npm install
  1. Configure Claude Desktop

Add to your claude_desktop_config.json:

{
  "mcpServers": {
    "revenue-engine": {
      "command": "node",
      "args": ["C:\\path\\to\\revenue-engine-mcp\\index.js"]
    }
  }
}
  1. Deploy Google Apps Script

  • Set up your Google Apps Script web app

  • Update the API_URL in index.js with your deployment URL

  1. Restart Claude Desktop

Tools Available

Revenue & Pipeline

  • get_dashboard - Get current revenue metrics

  • get_pipeline - View all leads

  • add_lead - Add new lead

  • update_lead - Update lead status

  • add_revenue - Log closed deal

Email & Calendar

  • search_gmail - Search inbox

  • get_email_content - Read full email

  • send_email - Send email

  • get_upcoming_meetings - View calendar

Knowledge Matrix

  • setup_matrix_sheet - Initialize Matrix

  • write_matrix_entry - Log work

  • matrix_daily_summary - Generate daily summary

  • matrix_time_analysis - Analyze time spent

Task Management

  • add_task - Create task

  • get_tasks - View all tasks

  • update_task - Update task status

File Operations

  • read_file - Read file contents

  • edit_file - Surgical file editing

  • write_file - Write/update files

  • run_command - Execute shell commands

Documentation

See Full Specification for complete documentation.

Version

Current version: 1.7.0

License

MIT

Available Tools

29 tools
add_leadC

Add a new lead to the pipeline

Inputs: companyName (required), contactName, contactEmail, contactPhone, +5 more.

add_revenueC

Add a closed deal

Inputs: clientName (required), contractValue (required), leadId, serviceType, +4 more.

add_taskD

Add a new task

Inputs: taskDescription (required), priority, dueDate, relatedTo, +2 more.

check_new_leadsB

Check for new leads added in last 24 hours that need welcome emails

Inputs: no named parameters.

delete_matrix_rowsA

Delete rows from Knowledge Matrix with confirmation requirement. First call shows preview, second call with confirm=true executes deletion. Cannot delete header rows (1-2).

Inputs: startRow (required), endRow (required), confirm.

edit_fileA

Surgically edit a file by finding and replacing exact text. 50% more efficient than read+write. Use after read_file to ensure exact match. Errors if text not found or appears multiple times. Creates backup automatically.

Inputs: path (required), find (required), replace_with (required).

get_dashboardB

Get current revenue dashboard with all key metrics

Inputs: no named parameters.

get_email_contentA

Get full content of an email thread by ID. Returns complete email body, attachments info, and all messages in the thread.

Inputs: threadId (required).

get_matrix_rowC

Get all topics for a specific date. Returns complete row from Matrix.

Inputs: date.

get_metricsB

Get recent daily metrics (last 7 days)

Inputs: no named parameters.

get_pipelineA

Get all leads in the pipeline

Inputs: no named parameters.

get_tasksC

Get all tasks

Inputs: no named parameters.

get_templatesB

Get message templates with performance metrics

Inputs: no named parameters.

get_upcoming_meetingsB

Get upcoming meetings from Google Calendar (next 7 days)

Inputs: no named parameters.

log_daily_metricsC

Log daily activity metrics

Inputs: date, outreachAttempts, responses, callsBooked, +3 more.

log_outreachC

Log an outreach activity

Inputs: companyName (required), channel (required), leadId, templateUsed, +4 more.

matrix_daily_summaryC

Generate formatted summary of Matrix entries for a specific date. Automatically parses timestamps, bug UIDs, time spent, and generates human-readable output.

Inputs: date, format.

matrix_time_analysisB

Analyze time spent across Matrix entries. Tracks total time by topic, bug UID, or week. Parses time markers like [30m], [2h] from entries.

Inputs: startDate, endDate, groupBy.

query_matrixC

Search Matrix for keyword across topics and dates

Inputs: keyword (required), topics, limit.

read_fileA

Read contents of a file. Only works in allowed directories: revenue-engine-mcp, apps-script folders

Inputs: path (required).

read_matrix_snapshotC

Read Matrix entries for a date range. Returns all entries for specified topics and dates.

Inputs: startDate, endDate, topics.

run_commandB

Execute allowed shell commands (clasp, npm, git, dir). For clasp commands, run from apps-script folder.

Inputs: command (required), workingDirectory.

search_gmailB

Search Gmail inbox. Use Gmail search syntax like 'from:email@example.com' or 'is:unread' or 'subject:proposal'

Inputs: query, maxResults.

send_emailA

Send an email via Gmail. ALWAYS get user approval before calling this.

Inputs: to (required), subject (required), body (required).

setup_matrix_sheetA

Auto-create Knowledge Matrix sheet with proper structure and headers. Run this once before using other Matrix tools.

Inputs: no named parameters.

update_leadC

Update an existing lead

Inputs: leadId (required), status, estimatedValue, notes, +2 more.

update_taskD

Update a task

Inputs: taskId (required), status, actualHours, notes.

write_fileA

Write or update entire file. Creates backup automatically. Use for complex multi-location edits or new files. Only works in allowed directories.

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

write_matrix_entryC

Write or append entry to Knowledge Matrix. Topics: Bugs & Fixes, Features Added, Testing Results, Decisions & Direction, Documentation Updates, Next Session Goals

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

Tool Schema Changelog

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

Loading tool schema changelog…

    TDQS

    C2.7/5.0

    Scored across 29 tools

    Disambiguation3/5

    Most tools have distinct purposes, but there is some overlap that could cause confusion. For example, 'get_matrix_row' and 'read_matrix_snapshot' both retrieve matrix data with subtle differences in scope, and 'edit_file' vs 'write_file' have overlapping file modification functions. The descriptions help clarify, but agents might misselect between similar tools.

    Naming Consistency4/5

    Naming is mostly consistent with a verb_noun pattern (e.g., 'add_lead', 'get_dashboard', 'update_task'), but there are minor deviations like 'check_new_leads' (verb_adjective_noun) and 'matrix_daily_summary' (noun_adjective_noun). These inconsistencies are minor and do not severely impact readability, as the overall pattern remains clear.

    Tool Count3/5

    With 29 tools, the count is borderline high for a revenue engine server, which typically handles sales, tasks, and metrics. While many tools are justified for diverse operations (e.g., matrix management, file editing, email handling), the set feels heavy and could be streamlined, potentially overwhelming agents with too many options.

    Completeness4/5

    The tool set covers a broad domain including lead management, task tracking, metrics logging, email operations, file handling, and matrix knowledge management. There are minor gaps, such as no tool for deleting leads or tasks, and limited meeting management beyond retrieval. However, core workflows are well-supported, and agents can work around these omissions.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers