# Product

ScopeDocs is the context base for engineering teams: connect the tools you already use, stamp decisions with sources, and ask, humans in the product, agents over MCP.

Slack, tickets, docs, calls, and code become one source-linked record. People read it. Agents query it over MCP so onboarding, on-call, and coding assistants share the same cited truth.

## Connect

Link GitHub, Linear, Slack, 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 project 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, ChatGPT, and ScopeDocs via MCP. Permissions mirror your workspace.

## What you connect

- **Code and reviews**: GitHub pull requests and repository context
- **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](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)
- [MCP markdown](https://scopedocs.ai/docs/mcp.md)
- [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

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

## Who it is for

Engineering and product teams that lose context in Slack archaeology, stale wikis, and handoffs. ScopeDocs is for teams that want living documentation for onboarding, on-call, and deep technical dives, without asking humans to maintain a second system of record.

## Product FAQ

### 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, 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.

## Related

- [Product (HTML)](https://scopedocs.ai/product)
- [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)