MergeSafe

● Active

ai.mergesafe/mergesafe

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

Connect this server

One click to install, or copy the config below. Suits: Cursor · HTTP clients.

Add to Cursor Add to VS CodeClaude Desktop / Claude Code: paste the config below.

Or add it manually — claude_desktop_config.json (Claude Desktop) or .cursor/mcp.json (Cursor):

{
  "mcpServers": {
    "mergesafe": {
      "url": "https://mcp.mergesafe.ai"
    }
  }
}
One line, from the terminal
Claude Code
claude mcp add --transport http mergesafe https://mcp.mergesafe.ai
VS Code
code --add-mcp '{"name":"mergesafe","type":"http","url":"https://mcp.mergesafe.ai"}'

Syntax from each client's docs (Claude Code: claude mcp add; Codex: codex mcp add; VS Code: code --add-mcp). Placeholders in angle brackets are values you fill in. Codex takes hosted servers in config.toml ([mcp_servers.<name>] url = …) rather than on the command line.

A starting point — check the repository for exact arguments and setup. Restart your client after editing the config.

Category
Developer Tools
Version
1.0.1
Registry
active
Published
11/20/2026
Listed in:Official MCP registry ↗how this is checked

Is it safe? Is it maintained?

Serverdex check: Nov 22, 2026

Looks healthy: MergeSafe is maintained, open source, hosted endpoint answering without a key.

Maintained
Active
Last commit 2 months ago (Oct 5, 2026), 2 open issues.
Official registry
Active
Published as ai.mergesafe/mergesafe in the official MCP registry, version 1.0.1.
Source
Open source, MIT
Public repository under the MIT licence, 0 stars, 0 forks.
Runs
Hosted by the publisher
Your client talks to mcp.mergesafe.ai: prompts and tool arguments leave your machine for that host.
Credentials
None needed to connect
The hosted endpoint completed the Serverdex initialize + tools/list handshake with no key (checked Nov 22, 2026); individual tools may still ask for one.
Owner
Unclaimed
Nobody has claimed this page yet; the data above comes from the registry, GitHub and the live check.

Facts only: last commit and licence from GitHub, the entry's status from the official registry, credentials from the live check. Not a code audit — run the security scan on the endpoint yourself and see the status history.

Live check

checked Nov 22, 2026, 07:07 UTCStatus history & uptime →
● Working241 msprotocol 2025-06-18v1tools

The endpoint answered the MCP handshake as "mergesafe" and listed 16 tools. Answering since Nov 21, 2026.

Context cost ≈ 4k tokens of tool definitions a client loads per conversation (estimate: characters ÷ 4) across 16 tools.

Tools (16)

  • get_findings2 params

    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 blocking finding, check the claim against the file as it stands now; if it holds, fix it and add a regression test; run the tests; commit and push; then call request_review. A finding of type question (needs_decision) asks whether a behavior is intended, with its severity_if_unintended; it does not block. It needs a decision, not just a fix, and it is likely a human one. Not intended: fix it (the fix answers it). Intended: say so on its thread; evidence helps (the PR's ticket, the PR description, a test, a doc or a file:line). Unsure: leave it open, or ask whoever owns the change.

    Show parameters
    • repostringrequiredThe repository as "owner/name".
    • pr_numberintegerrequiredThe pull request number.
  • request_review4 params

    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.

    Show parameters
    • repostringrequiredThe repository as "owner/name".
    • pr_numberintegerrequiredThe pull request number.
    • tierstringOptional review level: essential, strong or ultra (budget, the older name, still works and is what responses say). Leave it out to use the repository's own sett
    • addonsarrayOptional add-ons; leave out to use the repository's own setting.
  • get_settings2 params

    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. Give the org (its GitHub login); add repo for that repository's effective settings. Read-only. A Member sees no billing fields.

    Show parameters
    • orgstringrequiredThe organization's GitHub login.
    • repostringOptional repository name.
  • list_repositories1 param

    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 account can see.

    Show parameters
    • orgstringrequiredThe organization's GitHub login.
  • local_context_status1 param

    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.

    Show parameters
    • repostringrequiredThe repository as "owner/name".
  • request_review_with_context6 params

    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 another commit nothing is queued (head_moved). For each changed source file, up to 3 test files named after it (test_foo.py, foo_test.go, foo.test.ts, foo.spec.js, FooTest.java, or foo.* in a tests directory); each item is {path, start_line: 1, end_line, sha: head_sha, text}: the file's first lines exactly as committed, at most 200 lines an item, 2000 lines and 150000 bytes in all. Never send secrets or files that are not tests; MergeSafe checks every excerpt against the commit.

    Show parameters
    • repostringrequiredThe repository as "owner/name".
    • pr_numberintegerrequiredThe pull request number.
    • head_shastringrequiredThe commit read at (40 hex).
    • evidencearrayrequiredThe test excerpts, as the tool's description lists.
    • tierstringOptional review level: essential, strong or ultra (budget, the older name, still works and is what responses say). Leave it out to use the repository's own sett
    • addonsarrayOptional add-ons; leave out to use the repository's own setting.
  • 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 the session_id and how reviews are priced (level rate x review size).

    Show parameters
    • repostringrequiredThe repository as "owner/name".
    • limit_usdnumberrequiredThe cost limit the user chose, in US dollars.
    • basestringThe branch the change is against.
    • branchstringThe local branch, if any.
  • review_local7 params

    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 each changed file with its patch and full text (none for a removed file). Also send context_files: the files that call, or are called by, the changed code (its callers and the modules it imports), because the review sees only what you send and cannot check effects in files it was not given. (at most 250000 bytes in all). Never send secrets. In a follow-up, only files changed since the last review are counted.

    Show parameters
    • repostringrequiredThe session's repository, "owner/name".
    • session_idstringrequiredThe session_id start_session returned.
    • upload_idstringFrom an upload sent with prepare_upload's token. Use this for a review too large to pass inline in files.
    • filesarrayThe changed files, unless upload_id is given.
    • context_filesarrayUnchanged files that call, or are called by, the changes.
    • omittedarrayFiles the review could not be sent because of the upload caps. The quote names them, so nothing left out is taken for absent.
    • callers_not_followedarrayChanged files that were sent, whose callers the review could not follow because their name is too common. The quote names them.
  • review_branch4 params

    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 them to confirm before confirm_review. A branch MergeSafe cannot read is refused with a note, and nothing is charged for it.

    Show parameters
    • repostringrequiredThe session's repository, "owner/name".
    • session_idstringrequiredThe session_id start_session returned.
    • basestringrequiredThe branch the change is against.
    • headstringrequiredThe pushed branch to review.
  • confirm_review4 params

    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_session_findings.

    Show parameters
    • repostringrequiredThe session's repository, "owner/name".
    • session_idstringrequiredThe session_id start_session returned.
    • review_idintegerrequiredThe review_id of the quote the user confirmed.
    • levelstringrequiredThe level the user confirmed, one the quote priced.
  • approve_more3 params

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

    Show parameters
    • repostringrequiredThe session's repository, "owner/name".
    • session_idstringrequiredThe session_id start_session returned.
    • amount_usdnumberrequiredThe amount the user agreed to add, in US dollars.
  • get_session_findings2 params

    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, done with the price charged, or failed (never charged). Fix what holds, then review_local again; or answer a finding with answer_finding.

    Show parameters
    • repostringrequiredThe session's repository, "owner/name".
    • session_idstringrequiredThe session_id start_session returned.
  • answer_finding4 params

    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.

    Show parameters
    • repostringrequiredThe session's repository, "owner/name".
    • session_idstringrequiredThe session_id start_session returned.
    • finding_idstringrequiredThe finding's id, from get_session_findings.
    • replystringrequiredWhy it is intended, or why it will not be fixed here.
  • session_cost2 params

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

    Show parameters
    • repostringrequiredThe session's repository, "owner/name".
    • session_idstringrequiredThe session_id start_session returned.
  • prepare_upload2 params

    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.

    Show parameters
    • repostringrequiredThe session's repository, "owner/name".
    • session_idstringrequiredThe session_id start_session returned.
  • end_session2 params

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

    Show parameters
    • repostringrequiredThe session's repository, "owner/name".
    • session_idstringrequiredThe session_id start_session returned.

Checked by Serverdex with a plain initialize + tools/list call to mcp.mergesafe.ai, no credentials, about once a day. A failed check is never a removal.

On GitHub

read Nov 21, 2026
Stars
0
Forks
0
Last push
Oct 5, 2026
License
MIT

Python

From the README

mergesafe-mcp MergeSafe's findings for your own coding agent (Claude Code, Cursor, or anything else that speaks MCP over stdio). Your agent reads what MergeSafe found on a pull request, fixes it on your machine, replies on the thread, and asks for a new review. Install From source: uv tool install git+https://github.com/mergesafe-ai/mergesafe-mcp Configure Claude Code Cursor (~/.cursor/mcp.json or .cursor/mcp.json) Then ask your agent: "Fix MergeSafe's blocking findings on PR 42 in acme/widgets." What leaves your machine • To MergeSafe: your API key, the repo name and the PR number. MergeSafe's API returns the review's index (severity, title, file, line) and no code. • To GitHub: your own token, to read comments you can already see on github.com and to post your replies. • Your agent writes the fixes locally, with your tokens. MergeSafe never generates or applies a patch.

Read the full README on GitHub →

Remotes

  • streamable-httphttps://mcp.mergesafe.ai

The most-starred Developer Tools servers in the index, with their live-check result.

ServerStarsLast pushLive check
REA466,935Nov 2026Local / not checked
GitHub34,658Nov 2026Needs sign-in
Repomix29,280Nov 2026Local / not checked
Compiler Explorer19,201Nov 2026Working
XERJ19,135Nov 2026Local / not checked

MergeSafe: questions people ask

Is MergeSafe a remote or a local MCP server?
According to its entry in the official MCP registry, MergeSafe ships as a hosted endpoint (streamable-http) that your client connects to by URL.
Does MergeSafe need an API key?
Its hosted endpoint completed the Serverdex live check — an MCP initialize + tools/list call — with no credentials on Nov 22, 2026. Individual tools may still ask for a key when called.
Is MergeSafe safe to use?
Looks healthy: MergeSafe is maintained, open source, hosted endpoint answering without a key. In detail — maintained: Active; official registry: Active; source: Open source, MIT; runs: Hosted by the publisher; credentials: None needed to connect. Serverdex check of Nov 22, 2026. This is a reading of the repository, the registry entry and the live check, not a code audit; run the Serverdex security scan on the endpoint before trusting it with real data.
Is MergeSafe still maintained?
Active: the repository's last commit 2 months ago. Last push Oct 5, 2026, 0 GitHub stars, MIT licence. Read from GitHub on Nov 21, 2026.
What tools does MergeSafe expose?
16 tools as listed by the server itself during the live check, including get_findings, request_review, get_settings, list_repositories, local_context_status. The full list with parameters is in the Live check section above.
How do I add MergeSafe to Claude, Cursor or VS Code?
Copy the config in "Connect this server" into your client's MCP config file (claude_desktop_config.json, ~/.cursor/mcp.json or .vscode/mcp.json), or use the one-click Add to Cursor / Add to VS Code buttons and the one-line commands for Claude Code and Codex; then restart the client.
Browse all Developer Tools →

Add the badge to your site

Show visitors that MergeSafe is listed here — it’s also the link we check for a free listing.

MergeSafe — listed on Serverdex

HTML — for your website

<a href="https://serverdex.io/server/ai-mergesafe-mergesafe?utm_source=badge"><img src="https://serverdex.io/brand/badge.svg" alt="MergeSafe — listed on Serverdex" width="123" height="40" loading="lazy"></a>

Recommended. A dofollow link from your own domain is the one that counts for search engines, and it's the link we check for a free listing.

Markdown — for your README

[![MergeSafe — listed on Serverdex](https://serverdex.io/brand/badge.svg)](https://serverdex.io/server/ai-mergesafe-mergesafe?utm_source=badge)

Nice for visibility, but GitHub marks README links nofollow, so it doesn't pass authority. Use the HTML badge on your site as well.

Add to CursorAdd to VS CodeOpen in Claude Code

Install buttons — for your README

[![Add to Cursor](https://serverdex.io/brand/install-cursor.svg)](https://serverdex.io/install/cursor/ai-mergesafe-mergesafe) [![Add to VS Code](https://serverdex.io/brand/install-vscode.svg)](https://serverdex.io/install/vscode/ai-mergesafe-mergesafe) [![Open in Claude Code](https://serverdex.io/brand/install-claude-code.svg)](https://serverdex.io/install/claude-code/ai-mergesafe-mergesafe)

One click opens Cursor or VS Code with this server's config prefilled; the Claude Code button lands on the one-line command. The links point at Serverdex, so when your config changes the buttons keep working.

Install buttons — HTML for your docs

<a href="https://serverdex.io/install/cursor/ai-mergesafe-mergesafe"><img src="https://serverdex.io/brand/install-cursor.svg" alt="Add to Cursor — via Serverdex" width="140" height="28"></a>
<a href="https://serverdex.io/install/vscode/ai-mergesafe-mergesafe"><img src="https://serverdex.io/brand/install-vscode.svg" alt="Add to VS Code — via Serverdex" width="147" height="28"></a>
<a href="https://serverdex.io/install/claude-code/ai-mergesafe-mergesafe"><img src="https://serverdex.io/brand/install-claude-code.svg" alt="Open in Claude Code — via Serverdex" width="180" height="28"></a>

Same buttons as plain links for a docs page or website.

Prefer a live badge with the score, stars and live check? Score badge (links to a page that explains the number and back to this listing).