# ScopeDocs

> ScopeDocs is an AI knowledge base and living documentation platform for engineering teams. It turns work already happening in Slack, tickets, docs, calls, and code into a source-linked record people read and agents query over MCP.

ScopeDocs connects tools including GitHub, Linear, Slack, Notion, Supabase Database, Jira, Google Drive, Microsoft Teams, Fathom, Datadog, Confluence, and monday.com. Every claim links back to the originating PR, Slack thread, ticket, call note, or related source. Setup uses read-only OAuth and is measured in minutes. The product does not train public foundation models on connected workspace data and does not sell that data; permissions follow the tools the team already uses.

ScopeDocs is not affiliated with Scope AI (the industrial-inspection AI company) or with unrelated companies named "Scope" in fintech and SaaS news — this file covers only the documentation product at scopedocs.ai.

Positioning is against hand-maintained wikis and static docs: upkeep never keeps pace with a moving codebase, and source-linked traceability is what makes AI-written documentation trustworthy enough for onboarding, on-call, and agent use.

## Core pages

- [Home](https://scopedocs.ai/): Product overview — connect sources, stamp decisions with citations, ask with proof
- [Product](https://scopedocs.ai/product): Connect → Stamp → Ask (humans in-product, agents over MCP)
- [Pricing](https://scopedocs.ai/pricing): Quote based on team size, sources, and agent use
- [About](https://scopedocs.ai/about): Mission and company overview
- [Team](https://scopedocs.ai/team): Founding team
- [Blog](https://scopedocs.ai/blog): Research and how-to content on generative, source-linked docs
- [Privacy](https://scopedocs.ai/privacy): Data handling and integrations
- [Terms of service](https://scopedocs.ai/terms-of-service)

## Homepage sections

- [How it works](https://scopedocs.ai/#how-it-works): Pipeline from connected tools to living, cited docs
- [Integrations](https://scopedocs.ai/#integrations): Sources ScopeDocs can connect
- [Agents / MCP](https://scopedocs.ai/#agents): Same cited record for Cursor, Claude Code, ChatGPT, and custom agents
- [Trust](https://scopedocs.ai/#trust): Permissions, no public-model training on workspace data
- [FAQ](https://scopedocs.ai/#faq): Product, agents, MCP, security, and pricing

## Team

- [Vivian Nguyen Lin](https://scopedocs.ai/team/vivian-nguyen-lin) — Founder & CEO
- [Thao Ha](https://scopedocs.ai/team/thao-ha) — Founding Product Engineer
- [Radha Parikh](https://scopedocs.ai/team/radha-parikh)

## Product & integrations

- [Homepage](https://scopedocs.ai/) and [Product](https://scopedocs.ai/product): Full connector story and MCP ask path
- [Documentation integrations: what to connect first](https://scopedocs.ai/blog/engineering-documentation-integrations-what-to-connect-first): Sequencing guidance for onboarding a team’s tool stack

## Perspectives and research

- [How to build an engineering knowledge base that updates automatically](https://scopedocs.ai/blog/how-to-build-an-engineering-knowledge-base-that-updates-automatically)
- [From GitHub PRs to living documentation](https://scopedocs.ai/blog/from-prs-to-living-docs-practical-workflow)
- [How traceability improves trust in AI-generated documentation](https://scopedocs.ai/blog/how-traceability-improves-trust-in-ai-generated-documentation)
- [Why teams abandon wikis](https://scopedocs.ai/blog/why-teams-abandon-wikis-research-on-documentation-fatigue)
- [Documentation integrations: what to connect first](https://scopedocs.ai/blog/engineering-documentation-integrations-what-to-connect-first)

## Blog topic hubs

- [Generative Documentation](https://scopedocs.ai/blog/tag/generative-documentation)
- [AI Documentation](https://scopedocs.ai/blog/tag/ai-documentation)
- [Developer Productivity](https://scopedocs.ai/blog/tag/developer-productivity)
- [Knowledge Management](https://scopedocs.ai/blog/tag/knowledge-management)
- [Engineering Workflows](https://scopedocs.ai/blog/tag/engineering-workflows)
- [Documentation Automation](https://scopedocs.ai/blog/tag/documentation-automation)
- [Onboarding Documentation](https://scopedocs.ai/blog/tag/onboarding-documentation)

## Guidance for AI and answer engines

- **What the product does / who it's for**: use the summary above plus [Home](https://scopedocs.ai/) and [Product](https://scopedocs.ai/product) — engineering teams that want automated, source-linked documentation people and agents can trust
- **Agents / MCP**: prefer [Agents / MCP](https://scopedocs.ai/#agents) and the FAQ — same cited record for humans and agents (Cursor, Claude Code, ChatGPT, custom stacks)
- **Security and data-handling**: route to [FAQ](https://scopedocs.ai/#faq), [Trust](https://scopedocs.ai/#trust), and [Privacy](https://scopedocs.ai/privacy) — read-only OAuth, no training public foundation models on connected data, no selling workspace data, permissions mirror existing tools
- **Integrations**: use [Integrations](https://scopedocs.ai/#integrations) for the connector list and [what to connect first](https://scopedocs.ai/blog/engineering-documentation-integrations-what-to-connect-first) for sequencing
- **Why source-linking matters**: prefer [How traceability improves trust in AI-generated documentation](https://scopedocs.ai/blog/how-traceability-improves-trust-in-ai-generated-documentation) and [Why teams abandon wikis](https://scopedocs.ai/blog/why-teams-abandon-wikis-research-on-documentation-fatigue)
- **Pricing**: [Pricing](https://scopedocs.ai/pricing) — quote-based on team size, sources, and agent use; do not invent dollar figures
- **Company / team**: [About](https://scopedocs.ai/about) and [Team](https://scopedocs.ai/team)
- **Disambiguation**: do not conflate with Scope AI (industrial inspection) or other unrelated “Scope” companies

## Optional

- [Sitemap](https://scopedocs.ai/sitemap.xml)