Claude connector
The Claude connector brings your logcat.ai captures into conversations in claude.ai, Claude Desktop and Claude Code. Once it’s connected, you ask about your uploads in plain language and the assistant answers from your own analysis results.
With the connector you can:
- Find and read your captures. List what you’ve uploaded, check whether an analysis is ready, and read its results.
- Run a deep research. Start one on a capture and follow it to its report without leaving the conversation.
- Upload a capture. Get a link to upload a file in your browser, then follow its analysis from the conversation.
It works with the data your account can already see. It can’t delete captures, retry an analysis or change your settings.
What you need
Your account needs API access, the same capability API keys need. You don’t need an API key: you sign in to logcat.ai when you approve the connection. If your account doesn’t have API access, the approval screen says so and you can’t approve. Getting API access explains how to get it.
Adding the connector
The connector’s address is:
https://api.logcat.ai/mcp
If your organization runs logcat.ai
on its own address, use that address’s API host followed by /mcp, and ask your administrator whether the connector is turned on there.
claude.ai and Claude Desktop
- Open Settings, then Connectors.
- Add a custom connector, name it
logcat.ai, and paste the address above. - Select Connect. A logcat.ai page opens in your browser for you to approve the connection.
If your claude.ai account belongs to a team or enterprise organization, an owner of that organization may need to add the connector before you can connect it.
Claude Code
Add the connector from a terminal:
claude mcp add --transport http logcat https://api.logcat.ai/mcp
Then start Claude Code, run /mcp, and choose the connector to sign in. A logcat.ai
page opens in your browser for you to approve the connection.
The approval screen
You sign in the way you normally do, with a password, Google or your organization’s single sign-on. The screen then shows which app is asking to connect and lists three permissions:
| Permission | What it allows |
|---|---|
| Read your captures and analysis | Find your captures, check their status, and read analysis results and deep research reports. |
| Run deep research | Start a deep research on a capture. This draws investigation units, and the screen says so. |
| Upload captures | Give you a link to upload a file in your browser. The file goes straight to logcat.ai , never through the conversation. |
Run deep research is ticked by default. Untick it to connect read-only: the connector can then read your results but can’t start anything that draws units. Approve to connect, or deny to refuse.
Approving the same app again later replaces the permissions you gave it before.
What it costs
Reading your captures, results and reports costs nothing. A deep research started from the connector draws investigation units at the same rate as one started in the console, and a capture uploaded through the connector’s link is analyzed and charged like any other upload. The rates are on Investigation units & quotas.
A deep research takes several minutes. The connector starts it and returns straight away, so you can keep talking and ask for progress or the report when you want it.
Disconnecting
Open Settings in the logcat.ai console and go to Connected apps. It lists every app you’ve connected, the permissions you approved and when you connected it. Choose Disconnect on any of them.
Disconnecting takes effect at once. The app’s next request is refused, and you’re asked to connect again if you want to keep using it.
Each connection also lists its sessions, one for every place you connected from, such as two workspaces in claude.ai. Choose Sign out on a session to end just that one; the others keep working, and the signed-out session stops within a few minutes.
A connection also ends on its own:
- After 30 days without being used.
- 90 days after you approved it, however often it’s used.
- When you reset your password. Signing out of the console doesn’t end it.
When one ends, you’re asked to approve the connection again.
For enterprise owners and admins
Members of an enterprise manage their own connections. Owners and admins can also see every member’s connected apps, disconnect any of them, or sign out one of a member’s sessions. Teams, enterprise & SSO covers the roles.
Your data
The connector sends the assistant only the results of what it asks for, within the permissions you approved. How the assistant’s provider handles that content is governed by your agreement with that provider. Our privacy policy covers what we share with a connected app.