NestDaddy

MergeSafe

ai.mergesafe/mergesafe · v1.0.1

The GitHub gatekeeper for builders: read review findings, fix them, ask for a re-review.

Connect Remote server

Terminal
claude mcp add --transport http mergesafe https://mcp.mergesafe.ai
~/.cursor/mcp.json
{
  "mcpServers": {
    "mergesafe": {
      "url": "https://mcp.mergesafe.ai"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "mergesafe": {
      "type": "http",
      "url": "https://mcp.mergesafe.ai"
    }
  }
}
Claude Desktop
Settings > Connectors > Add custom connector
URL: https://mcp.mergesafe.ai

Tools 16 found in our last check

  • get_findings

    List MergeSafe's findings on the latest review of a pull request. Each has severity (P0 most severe .. P3), title, problem, file, line, status, blocking and comment_url, the inline comment on GitHub that holds the full explanation and a prompt for fixing it. Loop: for each block…

  • request_review

    Ask MergeSafe to review the current head of a pull request; MergeSafe posts the review on the pull request. A head that was already reviewed is refused, not charged twice. Call it after pushing fixes.

  • get_settings

    Read how this organization's MergeSafe is set up: for each setting its effective value, where the value comes from (repo_override, org, mixed with field_sources, mergesafe_default, or unchecked when it could not be read) and the values it may take, plus the settings version. Giv…

  • list_repositories

    List the repositories MergeSafe reviews for an organization, each with its effective level, plus the org's trigger mode and the GitHub link where the repository selection is changed (GitHub decides which repos are reviewed). Read-only. A Member sees only the repos their GitHub a…

  • local_context_status

    Whether the repository's organization accepts local context (request_review_with_context). Ask before reading anything to send: when it is off, send nothing and use request_review.

  • request_review_with_context

    Like request_review, but also sends excerpts of the tests of the files the pull request changes, read from your local checkout, so the review sees them. Only when local_context_status says enabled. Push first: head_sha is the commit you read at, and if the pull request's head is…

  • start_session

    Start a MergeSafe review session for local changes, before or without a pull request; nothing is posted to GitHub. FIRST ask the user for a cost limit for the session in US dollars and pass it as limit_usd: reviews stop when it is reached until the user approves more. Returns th…

  • review_local

    Send the local diff for review and get its quote. Nothing runs yet: the answer says 'This review will cost you up to $X (Strong)' with the other levels' prices. Always show the user the price and ask them to confirm before you call confirm_review; never confirm on your own. Send…

  • review_branch

    Review a branch already pushed to GitHub, with no upload: MergeSafe reads the branch's changes from GitHub itself. Returns review_id with status 'fetching' (queued). Poll get_session_findings until this review is 'quoted', then show the user its price as for review_local and ask…

  • confirm_review

    Run a quoted review at the level the user chose, ONLY after the user confirmed its price. The price is held; what is charged afterwards is never more. If the session's limit would be passed, nothing runs: ask the user, and use approve_more only if they agree. Then poll get_sessi…

  • approve_more

    Raise the session's cost limit by amount_usd. Only after the user explicitly agreed to that amount; never on your own.

  • get_session_findings

    The session's findings (severity P0 most severe .. P3, file, lines, problem, suggestion, status: open, withdrawn or kept_at_p3, and any answer's verdict; a finding whose answer could not be judged is open again and may be answered) and the state of its latest review: running, do…

  • answer_finding

    Answer a finding once per review (free): 'won't fix here' or why it is intended. MergeSafe judges the reply and withdraws the finding, keeps it at P3, or notes it; get_session_findings shows the verdict. For a fix, just review_local again: the next review re-checks the file.

  • session_cost

    The session's total so far, its limit and what is left.

  • prepare_upload

    Get a short-lived upload token for this open session (10 minutes, one upload). The local process POSTs the review's files to upload_path with it, so the file contents never pass through you. Then call review_local with the upload_id it returns. Spends nothing.

  • end_session

    Close the session; the uploaded code is deleted. Findings are kept.

Details

Endpointhttps://mcp.mergesafe.ai (Streamable HTTP)
First published20 Nov 2026
Last updated20 Nov 2026
Registry nameai.mergesafe/mergesafe

More developer tools servers See all

Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.