Connecting Gemini to Lead Recorder (MCP server)

Who's eligible today, the exact setup steps in Gemini Spark's Connected Apps, and exactly what account data Gemini can read once it's connected.

Lead Recorder runs a remote MCP (Model Context Protocol) server at mcp.leadrecorder.com so you can ask Gemini for lead reports directly, without logging into the dashboard, once it's added as a custom app under Gemini Spark's Connected Apps: "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 Gemini 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

1. 1Go to gemini.google.com on a desktop browser, then open Settings and help.
2. 2Go to Connected Apps and find the "Custom apps for Spark" section.
3. 3Click Add a custom app and paste https://mcp.leadrecorder.com. If the server doesn't complete Dynamic Client Registration automatically, expand Advanced features and enter the connection details manually.

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.

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 custom app from Gemini's Connected Apps settings at any time, or revoke the key from Account → API access. Disconnecting Gemini doesn't affect a Claude or Grok connection, since each is issued its own credential.