A direct LGM connector shows your agent the sequence. Pathbound shows your agent the customer — LGM lead alongside the same person in HubSpot, the same email thread in Gmail, the same pageviews in your tracker — through one unified profile served over the Model Context Protocol.
LGM identifies leads by pro email, personal email, LinkedIn URL, and phone. Pathbound resolves any of those to the same Contact you already have in HubSpot, Gmail, your tracker, and Apollo. Stop reconciling four IDs by hand.
Audience membership and campaign status sit on the same timeline as their pricing-page visits, replies, and meetings. The agent sees what you sent, what they did, and what the CRM thinks — all in one read.
Token-efficient response shapes (count_only, fields=summary), server-side aggregation, batch tools. Agents get the answer, not raw JSON dumps. Stays inside the context window.
LGM data is pulled on a 60-minute schedule into the unified profile. No webhooks to configure, no per-tenant URLs to paste back into LGM. Connect once with an API key and it shows up.
Connect LGM once. Your agent gets identity-resolved profiles with audience and campaign context, joined to the rest of your stack — through one MCP server.
{
"mcpServers": {
"pathbound": {
"url": "https://mcp.pathbound.ai/mcp"
}
}
}…plus 20 more — 26 MCP tools total, across contacts, companies, events, and conversations.
One API key. Drop a snippet into your MCP client. Ask a question.
Create an account at pathbound.ai. Free during public alpha.
In LGM, go to Settings → API and copy your API key. In the Pathbound dashboard, go to Integrations → La Growth Machine → Connect, paste the key. Sync runs every 60 minutes and pulls audiences, leads (pro/perso email, LinkedIn URL, phone, company), and campaign membership.
Drop the snippet below into your Claude Desktop config (or in Claude.ai web: Settings → Connected Apps → Add custom MCP → enter https://mcp.pathbound.ai/mcp). The same URL works for ChatGPT, Cursor, Cline, and any MCP client that supports OAuth.
{
"mcpServers": {
"pathbound": {
"url": "https://mcp.pathbound.ai/mcp"
}
}
}Ask the agent: “Which LGM leads from my newest audience also showed up in tracker this week?” The agent calls list_contacts and list_events via MCP and joins the answer for you.
Pathbound is an independent platform. We connect to La Growth Machine via their REST API using an API key you generate in LGM, and expose your data through one Model Context Protocol server alongside your other sources. Not affiliated with La Growth Machine.
No. This integration is pull-only — LGM data is read into the unified profile on a 60-minute schedule. The agent reads, you act in LGM. Write-back is on the roadmap.
Audiences, leads (firstName, lastName, proEmail, persoEmail, phone, linkedinUrl, companyName, companyDomain, jobTitle, status, custom variables), and campaign metadata. Stale leads — those removed from an audience between syncs — are reflected on the next pull.
Identity resolution: pro email → personal email → LinkedIn URL → phone. If the same person already exists in HubSpot, Gmail, or your tracker, the LGM lead joins that profile instead of creating a duplicate. Sales-Navigator-style LinkedIn URLs aren’t accepted by LGM, so Pathbound uses the canonical /in/ form.
LGM gates API access behind their higher tiers. Check your LGM plan or contact LGM sales if you’re not sure. Pathbound itself is free during public alpha.
Tenant-isolated and OAuth-scoped per user, with encryption at rest via our infrastructure provider's default configuration. GDPR-aligned; SOC 2 readiness in progress. Pathbound does not sell customer data, and we don't call AI providers on your behalf — your MCP client does, under your account and the AI provider's terms.
Same MCP server, same tools — just connect a different source. See the integrations directory.
Sign up. Drop in the tracker snippet. Connect one CRM. Point your MCP client at
mcp.pathbound.ai/mcp.