
Agents in your IDE, shipping to your stack
Skene doesn't run a separate service. Three MCP-based agents live in your IDE and write directly to your Supabase and Resend accounts. Open source core, your infrastructure.
Where things run
Everything stays in your environment. Agents run in your IDE and write to your accounts.
Your IDE
Skene runs as an MCP inside Claude, Cursor, Codex, or any terminal with MCP support. Agents execute in your local environment alongside your code.
Your Supabase
Agents write growth features — notifications, event triggers, database schemas — directly into your Supabase project. You own the data and infrastructure.
Resend
The Go-to-market Agent connects to your Resend account to automate transactional and lifecycle emails triggered by Supabase events.
From codebase to customer engagement
The agents form a pipeline: understand → generate → automate. Each step builds on the previous one.
You install Skene as an MCP in your IDE (Claude, Cursor, Codex, Terminal).
Product Manager Agent reads your codebase and Supabase database to understand the product, usage, and growth opportunities.
It generates a prioritised growth plan — what features to build, what activation moments to optimise, what your ICP looks like.
Growth Agent takes that plan and ships notifications, emails, and PLG features directly into your Supabase as database schemas, edge functions, and triggers.
Go-to-market Agent connects to Resend and your Notification Center to automate customer engagement based on realtime Supabase events.
Why it's built this way
Agent-native
Not a dashboard with AI bolted on. Three specialised agents that run where you code, doing the work a growth team would do.
Code-first delivery
Agents don't generate slides or reports. They generate code, schemas, and configurations that ship to your Supabase.
Event-driven
The Go-to-market Agent reacts to real events in your Supabase — not cron jobs or manual triggers. Notifications and emails fire when they should.
Open source core
The analysis engine is open source on GitHub. You can audit, fork, or contribute. The core runs locally in your environment.
What agents connect to
MCP protocol
Standard Model Context Protocol that works with any compatible IDE. No proprietary plugins.
Supabase
Postgres database, Auth, Edge Functions, Realtime. Agents write to your existing project.
Notification Center
In-app notifications triggered by Supabase events, orchestrated by the Go-to-market Agent.
Resend
Email delivery for transactional and lifecycle messages, automated from Supabase events.
See the architecture in action
Install Skene and watch agents analyse your code and generate growth features in real time.