La Growth Machine MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LGM_API_KEY | Yes | Your La Growth Machine API key from Settings > API |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_membersA | List all members (users) associated with your LGM workspace |
| list_identitiesB | List all connected identities in your LGM account. An identity is the profile (LinkedIn, email, etc.) used to send messages. |
| list_audiencesB | List all audiences in your LGM account. Audiences are groups of leads targeted in campaigns. |
| create_audience_from_linkedinB | Import leads into an audience from a LinkedIn URL (regular search, Sales Navigator, or post URL) |
| get_audience_detailC | Get detailed information about a specific audience |
| get_audience_leadsB | List leads in a specific audience with pagination |
| create_or_update_leadB | Create a new lead or update an existing lead in a specified audience |
| search_leadB | Search for a lead by email, LinkedIn URL, lead ID, name, or company |
| update_lead_statusB | Update the status of a lead within specific campaigns. Identify the lead by at least one identifier. |
| remove_lead_from_audiencesA | Remove a lead from one or more audiences. Identify the lead by at least one identifier. |
| get_lead_logsB | Get activity logs for a specific lead (messages sent, enrichments, status changes, etc.) |
| get_lead_conversationsB | Get all conversations for a specific lead across channels |
| get_campaignsB | Retrieve all campaigns with pagination support (max 25 per page) |
| get_campaignB | Get a single campaign by ID with full details |
| get_campaign_statsB | Get engagement statistics for a campaign (replies, conversions, channel breakdowns) |
| get_campaign_leads_statsA | Get per-lead statistics for a campaign. Supports cursor-based pagination (getLeadsAfter/getLeadsBefore) for simple page-by-page access, OR offset-based pagination (skip/limit) and status filtering — when skip>0 or status is provided, all pages are fetched client-side and then filtered/sliced. |
| get_campaign_messagesC | Get messages sent in a campaign |
| list_inbox_webhooksA | List all inbox webhooks configured in your workspace |
| create_inbox_webhookA | Create an inbox webhook for real-time notifications on inbox events (LinkedIn and Email messages) |
| delete_inbox_webhookA | Delete an inbox webhook by its ID |
| send_linkedin_messageA | Send a LinkedIn text or voice message to a lead. Requires either leadId or linkedinUrl, and either message or audioUrl. |
| send_email_messageA | Reply to an existing email thread with a lead. Cannot initiate new email conversations — use replyToMessageId (get it from get_conversation_messages) or replyInLastThread. Requires either leadId or leadEmail (not both). |
| edit_conversation_noteB | Add or replace a note on an inbox conversation. Identify the conversation by conversationId, or by lead identifiers. |
| rb2b_native_webhookB | Webhook endpoint for RB2B website visitor tracking. Each visitor is pushed into the specified audience. |
| warmly_native_webhookB | Webhook endpoint for Warmly website visitor tracking. Each visitor is pushed into the specified audience. |
| vector_native_webhookB | Webhook endpoint for Vector website visitor tracking. Each visitor is pushed into the specified audience. |
| get_conversation_messagesC | Get messages from a specific conversation with pagination |
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 27 tools
Each tool targets a distinct resource or action: members, audiences, leads, identities, campaigns, webhooks, and messaging. Even overlapping areas like lead search vs. audience leads are clearly differentiated by the scope. The three webhook tools are for different external services, avoiding confusion.
Most tools follow a consistent verb_noun pattern in snake_case (e.g., list_members, get_audience_detail, create_or_update_lead). The only deviation is the three native webhook tools (rb2b_native_webhook, etc.) which lack a verb prefix, but this is a minor inconsistency given their endpoint nature.
With 27 tools, the server is comprehensive and covers multiple domains (audiences, leads, campaigns, messaging, webhooks). While the count is on the higher side, each tool has a clear purpose and the scope justifies the number. It is slightly above ideal but still well-scoped.
The server has significant lifecycle gaps: there is no way to create or delete campaigns, no delete audience or delete lead, and no update audience. The focus is heavily on reading and sending messages, but full CRUD operations are missing for key resources, which will cause agent failures in workflows requiring deletion or creation of campaigns.