Skene reads your codebase and produces a **user journey** for your product: the lifecycle stages a user moves through, the milestones inside each
If you already use Skene, the skene mcp server is the piece that lets your assistant work with it directly. Skene reads your codebase and produces a user journey for your product: the lifecycle stages a user moves through, the milestones inside each stage, and the code or database evidence that proves each milestone is real.
The server ships on PyPI as skene, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
Seven — stage user journey** — every product maps to the same canonical stages (*discovery, onboarding, activation, engagement, retention, expansionEvidence — backed milestones** — each milestone carries a tracked_event, a confidence score, and one or more evidence chips pointing back to the exact codeCode — only, schema-only, or both** — run against just a codebase, just a directory of *.sql files, or both for richer evidenceDefault — ** ./skene-context/journey.yaml — the analysed user journey for your productOverride — ** set output_dir in .skene.config or pass -o/--output to write elsewhereDirectory — DescriptionThis sits in the database access group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Skene's toolset — Seven, Evidence, Code and 3 more — is a fair guide to whether it matches your workflow. It is maintained by skenetechnologies; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Skene's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| Seven | stage user journey** — every product maps to the same canonical stages (*discovery, onboarding, activation, engagement, retention, expansion, virality*) so journeys are comparable across products. Stage names are special |
| Evidence | backed milestones** — each milestone carries a tracked_event, a confidence score, and one or more evidence chips pointing back to the exact code path, database table, or config file that justifies it. |
| Code | only, schema-only, or both** — run against just a codebase, just a directory of *.sql files, or both for richer evidence. |
| Default | ** ./skene-context/journey.yaml — the analysed user journey for your product. |
| Override | ** set output_dir in .skene.config or pass -o/--output to write elsewhere. |
| Directory | Description |
{
"mcpServers": {
"skene": {
"command": "uvx",
"args": ["skene"]
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
Read-only SQL access to Postgres — let your assistant inspect schemas and answer questions from real data.
Manage your whole Supabase project in conversation — database, auth, storage, Edge Functions and branches.
Query, modify and analyse local SQLite databases in conversation — the fastest way to chat with a data file.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Official MongoDB server covering data, schemas and Atlas management — from find queries to spinning up clusters.
Serverless Postgres with database branching — point your assistant at Neon and let it work on disposable copies.