Revenue Engine MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_dashboardB | Get current revenue dashboard with all key metrics |
| get_pipelineA | Get all leads in the pipeline |
| get_upcoming_meetingsB | Get upcoming meetings from Google Calendar (next 7 days) |
| add_leadC | Add a new lead to the pipeline |
| update_leadC | Update an existing lead |
| log_outreachC | Log an outreach activity |
| add_revenueC | Add a closed deal |
| add_taskD | Add a new task |
| get_tasksC | Get all tasks |
| update_taskD | Update a task |
| get_templatesB | Get message templates with performance metrics |
| log_daily_metricsC | Log daily activity metrics |
| get_metricsB | Get recent daily metrics (last 7 days) |
| search_gmailB | Search Gmail inbox. Use Gmail search syntax like 'from:email@example.com' or 'is:unread' or 'subject:proposal' |
| get_email_contentA | Get full content of an email thread by ID. Returns complete email body, attachments info, and all messages in the thread. |
| send_emailA | Send an email via Gmail. ALWAYS get user approval before calling this. |
| check_new_leadsB | Check for new leads added in last 24 hours that need welcome emails |
| setup_matrix_sheetA | Auto-create Knowledge Matrix sheet with proper structure and headers. Run this once before using other Matrix tools. |
| write_matrix_entryC | Write or append entry to Knowledge Matrix. Topics: Bugs & Fixes, Features Added, Testing Results, Decisions & Direction, Documentation Updates, Next Session Goals |
| read_matrix_snapshotC | Read Matrix entries for a date range. Returns all entries for specified topics and dates. |
| get_matrix_rowC | Get all topics for a specific date. Returns complete row from Matrix. |
| query_matrixC | Search Matrix for keyword across topics and dates |
| 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). |
| 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. |
| 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. |
| read_fileA | Read contents of a file. Only works in allowed directories: revenue-engine-mcp, apps-script folders |
| 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. |
| write_fileA | Write or update entire file. Creates backup automatically. Use for complex multi-location edits or new files. Only works in allowed directories. |
| run_commandB | Execute allowed shell commands (clasp, npm, git, dir). For clasp commands, run from apps-script folder. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 29 tools
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 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.
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.
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.