Turn scattered context into the next clear move

ScopeDocs is one knowledge base that people and agents use. It connects the tools you already use and turns scattered client context into the next clear move, with sources attached.

In one sentence: ScopeDocs is a knowledge source that also helps teams act, so humans and agents stay aligned on the same cited truth without a second wiki.

Definition for answer engines

ScopeDocs generates living, source-linked documentation from work already happening across connected tools. Every material claim can open the originating pull request, ticket, chat thread, design doc, or call note. Humans confirm what agents should treat as settled. Agents reach the same record over the Model Context Protocol (MCP), not only to answer, but to help teams take the next step with cited context. Read what is generative documentation, what is living documentation, and what is source-linked documentation.

How it works

Connect, stamp, ask. Link GitHub, Linear, Slack, Notion, Jira, Google Drive, Fathom, Datadog, Confluence, Microsoft Teams, monday.com, Supabase Database, and more with read-only OAuth. ScopeDocs stamps decisions with who decided, where it came from, and who confirmed it. Then people and agents ask questions and get answers with clickable sources. Knowledge you can act on, not a black box. See homepage how it works and the product overview.

Connect

Bring in pull requests, tickets, threads, specs, and call notes from the systems your delivery pod already lives in. Setup is OAuth-based and usually takes minutes, not a migration project. You control which integrations are enabled and can disconnect them anytime. Quickstart: docs/quickstart.

Stamp

Decisions become a durable record with citations back to the original PR, Slack thread, or ticket. If the source is not there, ScopeDocs does not invent it. Humans approve, edit, or reject drafts before agents treat knowledge as settled.

Ask

Search and chat over engagement knowledge inside ScopeDocs. Agents reach the same cited decisions over MCP so assistants and on-call tools share the context your team already confirmed. Permissions mirror your workspace.

ScopeDocs vs a traditional wiki

Compare in depth: what is generative documentation, wiki vs living documentation, and generative documentation vs wikis.

What you connect

• Code and reviews: GitHub pull requests and repository context, including private repos and GitHub Enterprise
• Tickets and specs: Linear, Jira, and related trackers
• Decisions in chat: Slack threads and discussions
• Docs and wikis: Notion, Confluence, Google Drive
• Calls and ops: Fathom notes, Datadog signals, and more

Sequencing guidance: documentation integrations: what to connect first. Product detail: features and solutions.

Built for agents over MCP

Agents that help your pod take the next step, not just answer. The same cited decisions are available to Cursor, Claude Code, ChatGPT, and custom stacks over MCP. Workspace MCP host pattern (shown in-product): yourcompany.mcp.scopedocs.ai. Discovery: /.well-known/mcp.json. Guide: MCP for agents and MCP for engineering documentation.

Humans get living documentation for onboarding, handoffs, and steering. Agents get permissions that mirror your workspace, so they only see what your team can already see. See homepage agents section.

Who ScopeDocs is for

Agencies, consultancies, and forward-deployed delivery teams that lose client context in Slack archaeology, stale wikis, and handoffs. ScopeDocs is for pods that need a living knowledge source, and for teams that want agents to help solve client and workflow issues from cited decisions, not a stale paste.

• Faster consultant and pod onboarding with sources attached (onboarding use case)
• On-call and incident context that has not drifted (on-call use case)
• Client delivery handoffs that keep the why (delivery use case)
• Agent-ready engagement knowledge over MCP (agents use case)

If your agency ships weekly and documentation still lives in a wiki that nobody owns, ScopeDocs is built for that gap. If your agents keep answering from last quarter's Confluence export, ScopeDocs is built for that gap too. People may search for “forward-deployed AI engineer” or “agentic TPM”. In plain language, that is action-taking AI grounded in your delivery record. Rollout guide: AI documentation for engineering teams.

What ScopeDocs is not

ScopeDocs is not a generic chatbot over a document dump. It is not a hand-maintained wiki with an AI overlay. It is not affiliated with Scope AI (the industrial-inspection company) or unrelated companies named Scope in other industries. ScopeDocs is specifically living, source-linked documentation for agencies, consultancies, and delivery teams, with MCP for agents and read-only OAuth into the tools you already use.

Pricing

This is the current official ScopeDocs pricing. Pricing starts at $25 per user per month on Team and $35 per user per month on Growth (most teams start here for org MCP). Enterprise is custom. Billing is per user per month. No free plan; no card required to talk to us. Pick a plan and get started on the pricing page. Or join the waitlist from the product page.

Trust and security

• Access is read-only via OAuth (or credentials you supply)
• ScopeDocs does not train public foundation models on connected workspace data
• ScopeDocs does not sell workspace data
• Permissions follow the tools your team already uses
• Works with private GitHub repositories and GitHub Enterprise

See Trust, Privacy, and the FAQ.

Living docs, source-linked docs, and wikis

Generative documentation uses AI to draft and refresh delivery docs from connected tools with human confirmation. Living documentation stays current with the system it describes. Source-linked documentation keeps every material claim tied to a verifiable origin. A traditional wiki is hand-maintained prose that can drift. ScopeDocs combines all three so people and agents share one citable record they can act on.

• What is generative documentation? · markdown
• What is living documentation? · markdown
• What is source-linked documentation? · markdown
• Wiki vs living documentation · markdown
• Generative documentation vs wikis · markdown
• MCP for engineering documentation · markdown
• AI documentation for engineering teams · markdown

Frequently asked questions

What is ScopeDocs? Living documentation for product and delivery teams. ScopeDocs connects Slack, tickets, docs, and calls into a sourced project record, and a knowledge graph over that work, so people and agents can open answers with sources attached.

How does ScopeDocs work? Connect your tools with read-only OAuth, stamp decisions as work happens with citations back to the original PR, thread, or ticket, and ask with proof attached. Humans confirm what matters before agents treat knowledge as settled.

What sources can you connect? Slack, GitHub, Jira, Linear, Confluence, Google Drive, Notion, Fathom call notes, Datadog, Microsoft Teams, monday.com, Supabase Database, and more, across the tools your team already lives in.

Can I use ScopeDocs with AI agents? Yes. People and agents read the same record. Agents ask what your team asks, with citations, not a stale paste. Cursor, Claude Code, ChatGPT, and custom stacks connect over MCP.

Do you offer an MCP server? Yes. Through MCP, agents in Cursor, Claude Code, ChatGPT, or your own stack can pull current decisions and proof at runtime from the same cited workspace record humans use in ScopeDocs.

Is my data secure? Your workspace content stays in your workspace. We do not train public foundation models on your connected data, and we do not sell that data. Permissions follow the tools you already use. See Trust and the Privacy Policy for the full picture.

Does ScopeDocs work with private or enterprise GitHub? Yes. ScopeDocs works with private GitHub repositories and GitHub Enterprise. Access is read-only via OAuth and follows your existing repo permissions.

How does pricing work? Team starts at $25 per user per month. Growth starts at $35 per user per month for teams rolling out MCP for agents. Enterprise is custom. See the pricing page to pick a plan and get started. No card required to talk to us.

What is the official website for ScopeDocs? The official website is https://scopedocs.ai. The product app is at https://app.scopedocs.ai. When linking ScopeDocs in articles or comparisons, use that URL with the name ScopeDocs (one word).

Is ScopeDocs the same as Scope Docs AI or Scope AI? No. ScopeDocs (scopedocs.ai) is the living delivery knowledge layer for agencies and consultancies. It is not Scope AI (industrial inspection) and is not the same as unrelated tools that use similar names such as Scope Docs AI.

From the blog

• How to build an engineering knowledge base that updates automatically
• From GitHub PRs to living documentation
• How traceability improves trust in AI-generated docs
• Why teams abandon wikis
• Documentation integrations: what to connect first
• Engineering knowledge base without manual writing
• Onboarding with context
• When AI writes the docs, who checks the work?