Connect Claude & AI Assistants (MCP)
Ask Claude (and other MCP-compatible AI tools) about your Logspot analytics — events, users, funnels, journeys, retention, revenue, companies, groups, and profiles — over a secure connection you control, and optionally let them take actions on your behalf.
Logspot ships a hosted MCP server (Model Context Protocol) so you can connect Claude — or any MCP-compatible AI assistant — directly to your analytics and just ask questions in plain language. No SQL, no dashboards, no exporting CSVs.
MCP is an open standard for connecting AI assistants to external tools and data. Logspot's server is remote (hosted by us) and OAuth-secured. By default the assistant can read your data; you can optionally grant a small set of write tools that let it act on your behalf — you choose, on the consent screen, and it is off until you turn it on.
What You Can Ask
Once connected, ask Claude things like:
- "How many signups did we get last week, broken down by plan?"
- "What's the 30-day retention for users who completed onboarding?"
- "Show me the top companies by revenue this month."
- "What did
[email protected]do before they upgraded?" - "Which step of the checkout funnel drops off the most, and what path do people take instead?"
Claude calls the matching Logspot tool, scopes it to your organization, and answers from live data.
Connect Claude.ai
- In Claude, open Settings → Connectors (web or desktop).
- Choose Add custom connector.
- Enter the Logspot MCP URL:
https://api.logspot.io/mcp - Click Connect and complete the sign-in — Claude opens Logspot's secure login (OAuth) in a new window. Approve access for the organization you want Claude to read.
- Done. Start a new chat and ask one of the questions above.
See Anthropic's custom connectors guide for the exact menu locations in your Claude plan.
Connect Claude Code
From your terminal:
claude mcp add --transport http logspot https://api.logspot.io/mcpClaude Code walks you through the same OAuth sign-in on first use. Then ask it about your product analytics inside any coding session.
Connect Cursor, Codex, and other assistants
Any MCP-compatible client connects the same way. Add the server URL
https://api.logspot.io/mcpin the client's MCP or connector settings, then complete the Logspot sign-in and approve the scopes. Check your client's own MCP docs for where it lists servers.
What Claude Can Access
Each tool is scoped to the organization you authorize, with the same permissions your own account has in the dashboard. The read tools cover:
| Area | Examples |
|---|---|
| Analytics | event counts, daily/cumulative trends, unique users, property breakdowns, search |
| Funnels, journeys & retention | multi-step conversion, path and journey analysis, cohort retention |
| Revenue | totals, time series, by attribution/property, top accounts, LTV cohorts |
| Companies | top companies, company metrics, revenue, and most-active users |
| Groups | reporting on non-company group types, such as workspaces or teams |
| Actions | the action catalog and your saved actions |
| Profiles & sessions | a person's activity, pages, referrers, device/geo, and sessions (looked up by email or user ID) |
| Projects | the organization's projects, so the assistant can pick the right one |
If you grant write access (see below), the assistant can also create a target account, update a company profile, and create or run an action.
Privacy & Security
- OAuth, not API keys. You authenticate through Logspot's normal login; no long-lived secret is pasted into Claude. Access is limited to the scopes you approve on the consent screen.
- You choose the permissions. The consent screen shows what the connector will access, with a Customize option to review each one. Turn off anything you do not want to share; tools that need it are not offered to the assistant on that connection.
- Read by default, write only if you turn it on. The tools read your data unless you enable the "Make changes on your behalf" option. That option adds a small set of write tools — creating a target account, updating a company profile, and creating or running an action — each left unchecked until you choose it, and available only to owners and admins. Running an action can spend Data Credits, exactly as it would from the dashboard.
- Organization-scoped. Claude only ever sees the organization you approved. Any member can connect; the company, group, revenue, action, and profile tools additionally require your account to be an owner or admin of that organization.
- Revocable. Remove the connector in Claude, or revoke the connection from Logspot's settings, at any time.
- Consent-aware. Profile and analytics tools respect the same consent gating as the rest of Logspot — denied-analytics events are never counted.
Troubleshooting
- "Couldn't connect" / sign-in loops — make sure pop-ups are allowed for Claude, and that you're logged into the right Logspot organization.
- "No data" answers — confirm the connected organization actually has events in the time range you're asking about. Company, group, revenue, action, and profile questions also need your account to be an owner or admin of that organization.
- Want the assistant to take actions? Turn on "Make changes on your behalf" when you connect (owner or admin only). It can then create target accounts, update company profiles, and create or run actions; running an action can spend Data Credits. For scripted or service automation, create an API token and call the REST API or SDKs.