Commentary
Open appTry Commentary
MCP & HTTP API

Give agents structured review context without scraping the UI.

Commentary’s MCP and API surfaces expose explicit review IDs, files, comments, permissions, answers, selected targets, and status so agents can participate in a human-owned revision loop.

  • Scoped authentication
  • Stable review IDs
  • Unresolved comments
  • Human approval state
Read developer documentationExplore the developer platform
MCP & HTTP API workflow
Connected
Implementation plan review
## Rollout and rollback

Deploy progressively, monitor the acceptance signal, and stop when the agreed threshold is crossed.

Structured revision context ready
Reference workflow

Connect the agent to a human-owned review loop.

The artifact, feedback, revision, and approval state stay explicit from start to finish.

  1. 01

    Authenticate with the narrowest supported Commentary credential.

    Start from an explicit artifact and named owner.

  2. 02

    Create or resolve the review and retain its stable identifier.

    Keep the current state and unresolved context visible.

  3. 03

    Retrieve unresolved feedback and the permitted selected context.

    Keep the current state and unresolved context visible.

  4. 04

    Revise the source artifact through its owning system.

    Keep the current state and unresolved context visible.

  5. 05

    Inspect revision state and wait for human verification.

    The next stage begins only after verification.

Current setup

Install from the Commentary repository marketplace.

These commands are sourced from the current public commentary-dev/commentary-skills repository. They describe repository marketplace availability, not vendor marketplace approval.

Discover the current API contract
GET /openapi.json
GET /mcp

Explicit contracts for every review surface.

Review identifiers, comments, Forms answers, Knowledge Brain context, and Live Preview targets are exposed through purpose-built contracts instead of DOM scraping.

  • Authentication and scope boundaries
  • Review and revision identifiers
  • Comment retrieval and status
  • Forms answer permissions
  • Knowledge and preview context

Automation can revise. Humans still approve.

The API exposes enough state for an agent to wait, revise, and verify. It does not collapse a human approval decision into a successful network request.

Continue the workflow

Use the next page that matches the artifact or boundary you need to review.

Authentication boundaries

Review token, provider, and preview constraints.

Read next

Reference workflow

Put the API into a human-owned loop.

Read next

Security and access

Understand provider, preview, token, and human approval boundaries.

Review boundaries
Human review, made explicit

Connect the agent. Keep approval human-owned.

Create reviews, retrieve unresolved comments, inspect revision state, and connect human approval to agents through Commentary MCP tools and HTTP APIs.

Read developer documentationExplore the developer platform