Connect Claude and AI Assistants (MCP)

Logspot ships a hosted MCP server (Model Context Protocol) so you can connect Claude, ChatGPT, Cursor, 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.

You can set all of this up in the app too, at Integrations → AI & API Access → AI Assistants (MCP), where each client below has its own tab.

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 jane@acme.com 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

Claude and Claude Desktop. In Claude, open Settings → Connectors (web or desktop), choose Add custom connector, and 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, then 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.

Claude Code. From your terminal:

claude mcp add --transport http logspot https://api.logspot.io/mcp

Then run /mcp in Claude Code and approve the browser sign-in.

Connect ChatGPT

ChatGPT connects to a remote MCP server through developer mode. Turn on developer mode in ChatGPT's settings, add a connector for the Logspot server URL, and sign in when prompted:

https://api.logspot.io/mcp

Developer mode connectors are available on paid ChatGPT plans (Plus, Pro, Business, Enterprise, and Education) on the web. See OpenAI's developer mode guide for the current steps and plan availability.

For OpenAI Codex:

codex mcp add logspot --url https://api.logspot.io/mcp

Then run codex mcp login logspot and approve the browser sign-in.

Connect Cursor

Use Cursor's one-click install, then approve the Logspot sign-in. If you prefer to edit config by hand, add the server to ~/.cursor/mcp.json (or .cursor/mcp.json in a single project):

{
  "mcpServers": {
    "logspot": {
      "url": "https://api.logspot.io/mcp"
    }
  }
}

Connect Other Assistants

Any MCP client that supports remote servers over HTTP, such as VS Code, Windsurf, and Gemini CLI, connects the same way. Add the server URL

https://api.logspot.io/mcp

in 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.

New to Logspot?

You can connect the MCP server before you finish signing up. Approving the connection sends you to onboarding to create your organization on the Free plan, then back to your assistant. You can build your first Company Profile there, and the first build is free.

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:

If you grant write access (see below), the assistant can also create a target account, update or build 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 or building 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 in Logspot go to Integrations → AI & API Access → AI Assistants (MCP) → Connected Applications and choose Revoke Access, at any time.
• Consent-aware. Profile and analytics tools respect the same consent gating as the rest of Logspot, so denied-analytics events are never counted.

Troubleshooting

• "Couldn't connect" or 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 or build 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.

Related

• Integrations
• API Authentication