Connecting Grok to Lead Recorder (MCP server)
The exact setup steps for adding Lead Recorder as a custom connector in grok.com/connectors, and exactly what account data Grok can read once it's connected.
Lead Recorder runs a remote MCP (Model Context Protocol) server at mcp.leadrecorder.com so you can ask Grok for lead reports directly, without logging into the dashboard, once it's added as a custom connector: "write me this month's report for Bob's Plumbing" or "which of my sites have gone quiet this week."
What data it can access
The server is read-only — none of its tools create, modify, or delete anything in a Lead Recorder account. Access is scoped by the same role-based permissions as the dashboard: an account admin or team member can see every site on that account; a client role only sees the sites they've explicitly been given access to. Connecting Grok never grants access beyond what the connecting user could already see by logging in.
None of the three tools return an individual lead's name, email address, or phone number. They return site metadata (name, domain) and aggregated counts and breakdowns (totals, percentages, top sources), a materially narrower scope of data than the Zapier/Make integration, which does expose per-lead contact details for its New Lead trigger.
Connecting
- 1Go to grok.com/connectors.
- 2Click New Connector, then choose Custom.
- 3Paste https://mcp.leadrecorder.com as the MCP server URL and complete the authentication prompt that follows. Lead Recorder's server registers itself automatically, so no manual client setup should be needed.
xAI doesn't publicly document which Grok plan tiers include custom connector support. If the option isn't there at grok.com/connectors, check your account's plan.
Endpoints
- https://mcp.leadrecorder.com — the MCP endpoint itself (Streamable HTTP transport)
- https://mcp.leadrecorder.com/.well-known/oauth-protected-resource — RFC 9728 protected resource metadata
- https://mcp.leadrecorder.com/.well-known/oauth-authorization-server — RFC 8414 authorization server metadata
- https://www.leadrecorder.com/oauth/authorize — the interactive login/consent screen
- https://www.leadrecorder.com/api/oauth/token — token exchange (authorization_code grant, PKCE required)
- https://www.leadrecorder.com/api/oauth/register — Dynamic Client Registration (RFC 7591), for clients that support registering themselves automatically
The three tools
list_sites
No parameters. Lists the sites (client websites) the connected account can see reports for — id, name, and domain only.
get_monthly_report
Parameters: siteId (required, from list_sites) and month (optional, YYYY-MM, defaults to the current month). Returns total leads, new vs. returning visitor counts, a phone/form/email/booking split, a paid/organic/direct channel breakdown, the top individual sources and campaigns by count, and the percentage of leads that arrived outside business hours. All figures are aggregated — no individual lead's contact details are included.
get_quiet_sites
Parameters: days (optional, defaults to 7). Lists sites on the account with zero leads in that window, along with how many days it's been since each one's last lead, useful for an agency spotting a client site that's gone quiet.
All three tools are read-only, idempotent, and only ever touch the connected account's own data (declared via the standard MCP tool annotations readOnlyHint, idempotentHint, and openWorldHint: false), nothing they do depends on or reaches outside Lead Recorder's own systems.
Rate limiting
Requests are rate-limited per account to 60 per minute, the same limit applied to the Zapier/Make integration and the Claude connector. Returns a JSON-RPC error if exceeded, expected only under misconfigured, unusually fast polling.
Revoking access
Remove the connector from grok.com/connectors at any time, or revoke the key from Account → API access. Disconnecting Grok doesn't affect a Claude or Gemini connection, since each is issued its own credential.