Technical surface

The technical surface should be explicit, scoped, and governed.

The live ProSe instance exposes MCP metadata and OAuth-oriented scope names for controlled tool access while keeping private data behind authorization boundaries.

SurfaceMCP metadata and OAuth path
Example scopescases, evidence, timelines, documents, review, exports
BoundaryAuthorized access only

Public technical metadata

The MCP endpoint is a technical signal for integrations and tool-aware workflows. Public documentation should explain the surface without exposing private records or suggesting open access.

Integration posture

Scoped access

Tool access should be separated by capabilities such as cases, evidence, timelines, documents, review, and exports.

OAuth path

Authorization should be explicit and auditable.

Human review

Write-capable workflows should preserve review and approval boundaries.

Traceability

Actions and outputs should leave enough context for later review.

Public-safe explanation

Technical pages should describe the integration model, not private customer data, private cases, sealed records, or confidential materials.