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.

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?

Pricing fits team size, sources, and agent use. Request a quote on the pricing page or book a demo and we will match you with the right plan. There is no public fixed dollar price list because every workspace footprint differs.

What ScopeDocs includes

Living, source-linked documentation for engineering teams, readable by people and queryable by agents over MCP.

Source-linked documentation

Every generated claim links back to a PR, Slack thread, ticket, call note, or doc so teams can verify answers instead of trusting a black box.

Living knowledge base

As work happens in connected tools, the record updates. Documentation is generated from the workflow, not maintained as a separate chore.

MCP for agents

Cursor, Claude Code, ChatGPT, and custom agents pull the same cited decisions over MCP that humans read in ScopeDocs. Discovery: /.well-known/mcp.json.

Read-only OAuth integrations

Connect GitHub, Linear, Slack, Notion, Jira, Drive, Fathom, Datadog, Confluence, and more without handing over write access by default.

Human-in-the-loop control

AI drafts; humans approve, edit, or reject. Agents should only treat confirmed knowledge as settled.

Workspace permissions

What people and agents can see follows the permissions in the tools you already use. Private channels and repos stay private.