# Product

> Turn scattered context into the next clear move. ScopeDocs is one knowledge base that people and agents use.

**What ScopeDocs is:** connects the tools you already use and turns scattered client context into the next clear move, with sources attached.

**How it helps:** a knowledge source that also helps teams act. Humans confirm what is settled. Agents pull the same cited record over MCP for Cursor, Claude Code, Codex, ChatGPT, and custom stacks.

HTML: [https://scopedocs.ai/product](https://scopedocs.ai/product)

## How ScopeDocs works

1. **Connect**. Link the tools your team already uses with read-only OAuth.
2. **Stamp**. Decisions become a durable, cited record. Humans approve what agents may trust.
3. **Ask**. People search and chat in ScopeDocs. Agents help take the next step from the same answers over MCP.

| Step | What happens | Outcome |
| --- | --- | --- |
| Connect | Read-only OAuth into GitHub, GitLab, Linear, Slack, Google Chat, Notion, Jira, Drive, Fathom, Datadog, Confluence, and more | Context starts flowing without a migration project |
| Stamp | Claims link back to a PR, thread, ticket, or doc; humans confirm drafts | A verifiable living record |
| Ask | Search/chat for humans; MCP for agents | One cited truth so people and agents can take the next clear move |

## Connect

Link GitHub, GitLab, Linear, Slack, Google Chat, Notion, Jira, Google Drive, Fathom, Datadog, Confluence, Microsoft Teams, monday.com, Supabase Database, and related systems with read-only OAuth. Setup is measured in minutes. You control which integrations are enabled.

## Stamp

Decisions become a durable, cited record. Every claim points back to a PR, thread, ticket, or doc so answers stay honest as the work changes. If the source is not there, ScopeDocs does not invent it. Humans approve what agents can trust.

## Ask

Search and chat over project knowledge. Agents reach the same cited decisions for Cursor, Claude Code, Codex, ChatGPT, and ScopeDocs via MCP. That is knowledge you can act on, not a black box.

## ScopeDocs vs a traditional wiki

| Need | Traditional wiki | ScopeDocs |
| --- | --- | --- |
| Keep docs current | People remember to edit pages | Docs stay tied to merges, tickets, and decisions |
| Verify a claim | Hope the page is right | Every material claim links to a source |
| Feed coding agents | Paste stale exports into prompts | Agents query the same governed record over MCP |
| Hand off work | Tribal knowledge and outdated pages | Shared living context with citations |

## What you connect

- **Code and reviews**: GitHub and GitLab pull requests, merge requests, and repository context
- **Tickets and specs**: Linear, Jira, and related trackers
- **Decisions in chat**: Slack and Google Chat 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](https://scopedocs.ai/blog/engineering-documentation-integrations-what-to-connect-first).

## MCP for agents

Workspace MCP host pattern (shown in-product): `yourcompany.mcp.scopedocs.ai`

- [MCP discovery JSON](https://scopedocs.ai/.well-known/mcp.json)
- [AI agents over MCP](https://scopedocs.ai/product#ai-agents)
- [Homepage agents](https://scopedocs.ai/#agents)

## Trust

- Read-only OAuth access to connected tools
- Does not train public foundation models on connected workspace data
- Does not sell workspace data
- Permissions follow the tools your team already uses
- Works with private GitHub repositories and GitHub Enterprise

See [Privacy](https://scopedocs.ai/privacy) and [Trust](https://scopedocs.ai/#trust).

## Who it is for

- [Onboarding](https://scopedocs.ai/solutions#onboarding)
- [On-call / incidents](https://scopedocs.ai/solutions#incidents)
- [Delivery handoffs](https://scopedocs.ai/solutions#product-delivery)
- [Agents over MCP](https://scopedocs.ai/solutions#agents)

## Product FAQ

### What problem does ScopeDocs solve?

Important context gets trapped across chat, tickets, docs, and calls. ScopeDocs turns that work into one living, source-linked knowledge base people can trust and agents can use to take the next clear move.

### Is ScopeDocs only for answering questions?

No. Answers matter, but the product is built so people and agents can act on cited context: handoffs, steering questions, change requests, and delivery work.

### How is ScopeDocs different from a wiki?

Wikis depend on people remembering to update pages. ScopeDocs generates source-linked documentation from work already happening in your tools, with citations so the record stays verifiable.

### Can agents use the same knowledge as humans?

Yes. People ask inside ScopeDocs; agents pull the same cited decisions over MCP for Cursor, Claude Code, Codex, ChatGPT, and custom stacks.

### Is access write-capable by default?

No. Integrations use read-only OAuth (or credentials you supply). You choose what to connect.

### How do we get started?

[Quickstart](https://scopedocs.ai/docs/quickstart), [contact us for pricing](https://scopedocs.ai/pricing), or email [hello@scopedocs.ai](mailto:hello@scopedocs.ai).

## Related

- [Product (HTML)](https://scopedocs.ai/product)
- [Features](https://scopedocs.ai/features)
- [Solutions](https://scopedocs.ai/solutions)
- [Pricing](https://scopedocs.ai/pricing)
- [About](https://scopedocs.ai/about)
- [Privacy](https://scopedocs.ai/privacy)
- [llms.txt](https://scopedocs.ai/llms.txt)
- [Quickstart markdown](https://scopedocs.ai/docs/quickstart.md)
- [Keep CRM change decisions findable](https://scopedocs.ai/blog/how-crm-implementation-teams-keep-salesforce-and-dynamics-change-decisions-findable)
- [Why CRM and ERP firms abandon client wikis](https://scopedocs.ai/blog/why-crm-and-erp-firms-abandon-client-wikis-documentation-fatigue-in-delivery)