---
title: "Integrations | Skene"
description: "Four connections: GitHub on the repositories you select, Supabase over OAuth with the access mode set at connect time, eleven MCP tools for coding agents, and PostHog or Mixpanel read as sources. GitHub only."
url: https://www.skene.ai/product/integrations
doc_version: "0a166494b421"
last_updated: 2026-08-29
---

Integrations

# What Skene connects to.

Skene watches the code that records the events your analytics tools read, and leaves those tools alone. It finds the tracking calls by pattern, across 16 analytics platforms, with no model in the loop.

[Connect a source](https://www.skene.ai/signup) [See how it works](https://www.skene.ai/product/how-it-works)

Each connection is scoped when you make it.

GitHub / acme/webapp connected

Never pushes to your default branch. Everything it proposes is a pull request you review.

- **The repositories you select**
  GitHub App installed on the repositories you pick, never all of them.

- **Access mode set at connect time**
  Supabase read-only and read-write are separately registered OAuth applications.

- **Eleven tools over MCP**
  Hosted by Skene, for coding agents.

Supabase PostHog Mixpanel BigQuery Resend

Four connections

## Each connection is scoped when you make it.

The repositories you select, the access mode you pick, the API key you issue.

[See how it works](https://www.skene.ai/product/how-it-works)

GitHub

The repositories you select.

Database

Supabase over OAuth. Access set at connect time.

MCP

Eleven tools, hosted by Skene.

Analytics

PostHog or Mixpanel, read as sources.

GitHub

`acme/webapp`

It never pushes to your default branch. Everything it proposes is a pull request you review.

Analytics

## Two providers, read as sources.

Exactly two analytics providers connect. PostHog, over its HogQL query API, and Mixpanel, over its service account query API. Skene reads the counts on demand behind a five minute cache.

Not a destination Sources

- **PostHog**: HogQL query API

- **Mixpanel**: Service account query API

- **Cache**: Five minutes

Your events keep going where they already go. Skene reads what is there.

## What the installation reaches.

The installation token does three things.

- Lists the repositories you picked

- Fetches the skene-context/ files the engine reads

- Posts pull request reviews

GitHub is the only repository host. GitLab and Bitbucket are not supported.

Webhook events

- push

- pull_request

- issue_comment

## Two connections, and one you can leave unassigned.

Development and production databases are assigned independently. If you have not assigned an environment, its checks report as not linked instead of passing.

- Deploys, triggers and every other write go to the production row only

**Integrations**/skene-dashboard

2 connected

- Supabase
  connected

- Production database acme-production
  assigned

- Development database
  not assigned

- GitHub acme/webapp main
  connected

## Connect one Supabase project.

Read-only and read-write are two separately registered OAuth applications, not a scope on one. Changing it later means reconnecting, not widening a grant you already gave.

[Start free](https://www.skene.ai/signup)

## Sitemap

- [Markdown sitemap](https://www.skene.ai/sitemap.md): every page on this site, with its markdown counterpart.
- [Index for language models](https://www.skene.ai/llms.txt): the same set as a link-dense index.
- [Full corpus](https://www.skene.ai/llms-full.txt): reference content concatenated as plain text.