> ## Documentation Index
> Fetch the complete documentation index at: https://docs.cogniscape.app/llms.txt
> Use this file to discover all available pages before exploring further.

# Integrations

> Connect your development tools to the Cogniscape knowledge graph.

Cogniscape ingests data from multiple sources. The CLI captures AI coding activity from Claude Code and Cursor locally; GitHub, GitLab, Linear, Jira, and Monday.com webhooks capture code changes and project management activity remotely.

<CardGroup cols={2}>
  <Card title="CLI (Claude Code + Cursor)" icon="terminal" href="/quickstart">
    Sessions, tasks, plans, and token usage — installed per developer machine. Automatically detects and hooks into both Claude Code and Cursor.
  </Card>

  <Card title="GitHub" icon="github" href="/integrations/github">
    Pushes, pull requests, and code reviews — one webhook per repository.
  </Card>

  <Card title="GitLab" icon="gitlab" href="/integrations/gitlab">
    Pushes, merge requests, pipelines, and deployments — one webhook per project, or one per group.
  </Card>

  <Card title="Linear" icon="chart-bar" href="/integrations/linear">
    Issues, comments, projects, and cycles — one webhook per workspace.
  </Card>

  <Card title="Jira" icon="ticket" href="/integrations/jira">
    Issues, comments, worklogs, sprints, projects, and versions — one webhook per Jira site.
  </Card>

  <Card title="Monday.com" icon="table-columns" href="/integrations/monday">
    Board items, updates, and column changes — one webhook per board.
  </Card>
</CardGroup>

<Note>
  GitHub, GitLab, Linear, Jira, and Monday.com integrations are configured entirely through webhook settings in those platforms. No additional software is needed on your machine — just the webhook URL containing your customer key. Jira also requires a signing secret (Cloud) or the `X-Cogniscape-Token` header (Data Center / Server).
</Note>

## Claude Code vs Cursor: what's captured

Both AI coding tools feed into the same knowledge graph, but they provide different levels of detail:

| Capability                             | Claude Code           | Cursor                                      |
| -------------------------------------- | --------------------- | ------------------------------------------- |
| Session lifecycle (start/stop)         | Yes                   | Yes                                         |
| Session summary (conversation content) | Yes                   | Yes                                         |
| Files modified/read                    | Yes (from transcript) | Not yet (transcript format limitation)      |
| Commands executed                      | Yes (from transcript) | Not yet                                     |
| Tool usage counts                      | Yes (from transcript) | Not yet                                     |
| Token usage per model                  | Yes (from transcript) | Not available (upstream limitation)         |
| Developer identity                     | git config            | git config, falls back to Cursor user email |
| Repository + branch                    | Yes                   | Yes                                         |
| Source discrimination                  | `source="agent"`      | `source="cursor"`                           |

Events from both tools are distinguishable in the knowledge graph and can be filtered independently in MCP queries.

## Where to find your customer key

Your customer key is available in the [Cogniscape Customer Portal](https://customer.cogniscape.app/) under your account settings. It is used to route events to your knowledge graph.

## Data privacy

Cogniscape only processes event metadata. **We never store source code.** GitHub and GitLab webhook payloads contain commit metadata, PR/MR titles, and review comments — not file contents. Linear, Jira, and Monday.com payloads contain issue/item titles, descriptions, and status updates.

For more details, see [Data Privacy](/security/data-privacy).