Direct answer

Connect directly to the Juror MCP endpoint, authenticate with Juror Cloud, list workspaces, and choose one before inspecting findings or runs. The endpoint runs hosted Juror Cloud, not arbitrary local repositories.

01Streamable HTTP endpoint

02OAuth workspace access

03Minimal data boundary

JUROR CLOUD MCP

Connect to the hosted service, then choose a workspace.

Add the direct Streamable HTTP endpoint in ChatGPT, Codex, or another MCP client. OAuth links your Juror Cloud account; it does not grant arbitrary GitHub or local-repository access.

{
  "mcpServers": {
    "juror": { "type": "http", "url": "https://app.juror.dev/mcp" }
  }
}

Supported review workflow

List your workspaces first. Inspect concise findings and hosted runs with a selected workspace ID. To run or rerun a review, Juror first preflights the open PR, current SHA, repository policy, GitHub Action conflict, and capacity. Show that result to the user and obtain an explicit confirmation before the write tool can start a hosted review.

Clear data boundaries

The integration returns minimal metadata and an explicitly requested retained finding body or claim. It never returns raw diffs, source checkouts, full reports, screenshots, artifacts, provider credentials, or prompt text. It runs hosted Juror Cloud—not an arbitrary repository on the agent machine.

Starter prompts

Show my Juror workspaces and review findings.
Summarize open P0 and P1 Juror findings in this workspace.
Prepare a hosted review for this PR and show the SHA and capacity warning before starting.

How it works

Start from a pinned, least-privilege workflow.

The action reference uses a released commit SHA. Store provider keys in GitHub secrets and inspect the first review before you require it.

name: Juror review
on:
  pull_request:
    types: [opened, synchronize, reopened]

permissions:
  contents: read
  pull-requests: write

jobs:
  review:
    if: github.event.pull_request.head.repo.fork == false
    runs-on: ubuntu-latest
    steps:
      - uses: Juror-AI/juror@3eb0c88ce1931dd6227d554b2d9707ee4bca123f
        with:
          github-token: ${{ github.token }}
          preset: balanced
          cost-target-usd: "4.00"

How it works

Connect directly to the Juror MCP endpoint, authenticate with Juror Cloud, list workspaces, and choose one before inspecting findings or runs. The endpoint runs hosted Juror Cloud, not arbitrary local repositories.

For connect juror through mcp., use the published configuration and source repository as the product record. Keep the workflow small enough to inspect, and record any exception in the pull request rather than assuming a model result is final.

Limits to keep in view

Models, providers, and benchmark conditions change. Juror does not replace code ownership, test suites, static analysis, or a human decision to merge. Treat unknown cost and unevaluated compatibility as explicit unknowns.

Next task

Integration

Connect Juror through MCP.

Direct answer

Connect to the hosted service, then choose a workspace.

Supported review workflow

Clear data boundaries

Starter prompts

Start from a pinned, least-privilege workflow.

How it works

Limits to keep in view

Next task

Use Juror in the GitHub review workflow.

Juror for GitHub pull requests.

A GitHub Action for multi-model review.