Letmediff MCP

it.letmediffPublished by letmediff.itv0.0.11Updated Oct 24, 2026

The official Letmediff MCP server helping you review your code with an agent first workflow

VerifiedSTDIODesktop onlyDeveloper ToolsCommunication & Collaboration

Overview

AI-generated overview

Local MCP server that snapshots a repository's code diff, uploads checkpoints to the letmediff web app, and returns reviewer feedback to the agent.

What you can do
  • Create named checkpoints that store the diff since the previous snapshot
  • Reset the review, clearing all checkpoints and restarting from the current working tree
  • Upload collected checkpoints and get a shareable diff review URL
  • Wait for feedback submitted in the web app and hand it back to the agent
When to use it
Use it when you want a human to review an agent's code changes inside the same coding session: the agent groups changes into checkpoints, shares a review link, and continues once feedback arrives.
Requirements
Runs as a local process via npx from the npm package, started in the repository to be reviewed. Needs Git for snapshotting and network access to the letmediff web app; the URL environment variable can point at a different base URL and defaults to the hosted service.
Before you install
Checkpoint diffs are uploaded to the letmediff web app, so code leaves your machine and anyone with the returned link can view the diff. The reset_review tool is destructive and clears all checkpoints. Checkpoints live only in memory for the life of the process.

Installation

In SourceWeft

  1. Open Letmediff MCP in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

letmediff CLI

letmediff is an MCP server that lets an agent share its current code diff for review and receive feedback from the reviewer without leaving the coding session.

It snapshots the repository where it is started, tracks named checkpoints, uploads the checkpoint diffs to the letmediff web app, and waits for feedback over server-sent events.

Install

From the published package:

sh
pnpm dlx letmediff

From this workspace:

sh
pnpm --filter letmediff exec letmediff

MCP Usage

Configure your MCP client to run letmediff in the repository you want reviewed.

Example command:

sh
letmediff

For local app development, point the CLI at the local SvelteKit server:

sh
URL=http://localhost:5173 letmediff

If URL is not set, the CLI posts diffs to https://letmediff.com.

Tools

The server exposes four MCP tools.

  • create_checkpoint: stores the diff since the previous snapshot under a reviewer-friendly name.
  • reset_review: clears all checkpoints and restarts the review from the current working tree. Destructive.
  • get_url: uploads the collected checkpoints and returns the shareable /diff/[id] URL.
  • wait_for_feedback: waits for feedback submitted from the web app and returns it to the agent.

Review Flow

  1. Start the MCP server from the repository being edited.
  2. Ask the agent to create checkpoints when a change should appear as a separate review section.
  3. Ask the agent for the review URL.
  4. Open the URL, review the rendered diff, and submit feedback.
  5. The agent receives the feedback through wait_for_feedback and can continue working.

Development

Install dependencies from the repo root:

sh
pnpm install

Run tests:

sh
pnpm --filter letmediff test

The CLI entry point is src/index.js. Git snapshotting and checkpoint diff generation live in src/git.js.

Environment

  • URL: base URL of the letmediff app. Defaults to https://letmediff.com.

Notes

  • The server uses stdio transport, so normal stdout is reserved for MCP communication.
  • It snapshots the current working directory at startup, excluding .git.
  • Checkpoints are kept in memory for the life of the MCP process.

Source: packages/letmediff/README.md at commit 8f80bb3

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.0.11LatestSep 16, 2026

Score

40% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.