# MCP for agents

ScopeDocs exposes the same source-linked project record to agents through the Model Context Protocol (MCP).

People and agents share one governed record: answers come with citations back to PRs, Slack threads, tickets, and docs, not a stale paste.

## Who this is for

- Cursor
- Claude Code
- ChatGPT (MCP-capable clients)
- Custom agents and internal tools that speak MCP

## Discovery

Machine-readable discovery document:

- [https://scopedocs.ai/.well-known/mcp.json](https://scopedocs.ai/.well-known/mcp.json)

Demo / product host pattern:

```text
yourcompany.mcp.scopedocs.ai
```

Replace `yourcompany` with your ScopeDocs workspace host when provisioned in-product.

## Auth and permissions

- Connect integrations with **read-only OAuth** in the ScopeDocs app: [https://app.scopedocs.ai](https://app.scopedocs.ai)
- Agents only receive what your workspace permissions already allow
- ScopeDocs does not train public foundation models on connected workspace data

There is no public anonymous MCP endpoint for customer workspaces. Authenticate through your ScopeDocs workspace, then connect your MCP client to the workspace MCP URL shown in the product.

## Example: what agents should expect

```text
User: Why did we change the billing retry policy?
Agent (via MCP): Returns the stamped decision with links to the Slack thread and Linear ticket.
```

## Related

- [Quickstart](https://scopedocs.ai/docs/quickstart.md)
- [Product](https://scopedocs.ai/product.md)
- [Privacy](https://scopedocs.ai/privacy.md)
- [llms.txt](https://scopedocs.ai/llms.txt)