Hackathon [Feature]: Add Mixpanel data-source connector

Problem Statement

cognee has five data-source connectors today (confluence, gmail, google-drive, notion, slack) against roughly 120 planned. Data sources are the thinnest surface in the project.

Mixpanel is on the roadmap and has no connector.

Proposed Solution

Add a mixpanel connector under packages/connector/mixpanel/ in cognee-community, following the shape of the five existing connectors.

• Auth: Service account / API secret
• Ingest: saved reports, cohorts, and the event schema
• Incremental sync: date-window export
• Forget-on-delete: deleting upstream must remove the record from the graph on the next sync

Watch out for

Same warning as Amplitude: definitions are knowledge, raw events are noise.

Package layout to follow

packages/connector/mixpanel/
├── README.md
├── cognee_community_connector_mixpanel/
│   ├── __init__.py
│   └── mixpanel.py
├── examples/
├── tests/
└── pyproject.toml

Read packages/connector/notion/ first — it is the closest working reference.

Acceptance Criteria

• A user connects via Service account / API secret and selects what to ingest
• Selected content is ingested and searchable in cognee
• Incremental sync picks up only what changed since the last run
• Deleting the source upstream removes it from the graph on the next sync
• README with setup steps and a runnable example under examples/
• Tests covering the ingest path and the incremental cursor

Context

Part of the cognee hackathon connector push. Difficulty: Beginner friendly (E) — auth is an API key or token; no OAuth dance, no account gatekeeping