Your team made 15 decisions last week.Can you name them?
Most team decisions live in Slack threads, PR comments, and meeting transcripts no one re-reads. undoc finds them and connects the dots, cited to a person, source, and date.
/undoc-ask
Reuses MCPs you already have.
How it Works
Most of what makes a team work was never written down.
The reason engineering picked Postgres. The thread where pricing exceptions got decided. The on-call playbook that lives in three people's heads. This is tacit knowledge: the unwritten layer of how a team actually works. undoc captures it in five steps.
01 · Ingest
Connect your tools.
undoc reads from the tools your team already uses: Slack, GitHub, Linear, Notion, Gmail, Calendar, and meeting transcripts. No new logins, no duplicate setup.
02 · Connect
Build your team brain.
Scattered conversations become one connected map of decisions, risks, blockers, and rationale. Every fact links back to where it came from.
03 · Query
Ask. Get cited answers.
Your AI chat queries the brain in plain English. Every answer comes back with a named person, source, and date. No unsourced summaries.
04 · Enrich
Smarter than your data alone.
undoc draws on proven operating and engineering practices on top of your team's data, so risks are graded clearly and decisions are framed the way well-run teams do it.
05 · Learn
Smarter with every use.
Up-vote, down-vote, or correct any answer in Claude. undoc folds your feedback back into the brain, so it knows more tomorrow than today.
A flywheel: the more your team uses it, the sharper it gets. Now here's how to call it ↓
How to Use
Install MCP. One team brain. Multiple skills.
undoc installs as an MCP server in one terminal command. Then call four skills in plain English from any MCP-aware AI chat. Every answer comes back cited to a named person, source, and date.
/undoc-sync
Pull recent content from every source into the brain.
- “Sync my sources to undoc”
- “Update from Slack since yesterday”
- “Pull GitHub PRs this week”
/undoc-ask
Query the brain for decisions, rationale, blockers, tacit knowledge.
- “What did we decide about auth this week?”
- “Why did we move off Clerk?”
- “Who owns the billing migration?”
/undoc-signals
Surface contradictions, unmitigated risks, what changed.
- “Show contradictions in our recent decisions”
- “Open blockers across the team”
- “Unmitigated risks this sprint”
/undoc-ops
Inspect the ingestion pipeline, reprocess batches, diagnose extraction.
- “Why did batch 248 produce nothing?”
- “Reprocess the last batch”
- “List my last 10 ingests”
Questions