Revue
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
revue is a git change viewer in the user's browser. When the user asks to see, show or review code changes ("show me the changes", "what did you change?", "let me see the diff", "review this branch"), open them in revue with revue_open instead of printing a diff in the chat. Use revue_show to put a file and line range in front of the user (for example the code you just changed or want them to review), and revue_annotate to leave a note on specific lines that the user sees inline. revue_changes, revue_diff, revue_log and revue_definitions read the same views (uncommitted work, a commit, or a branch vs its base) as text for you; they show the user nothing. A folder that isn't in a git repo (or any folder with git: false) opens as a plain folder: revue_open, revue_show, revue_annotate and revue_definitions work on its files, and revue_changes, revue_diff and revue_log say it isn't a git repository.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| revue_openA | Open revue, the browser-based git change viewer, on the overview of all changed files. Use this when the user asks to see or review code changes, rather than printing a diff. Starts a revue server for the repo if needed and reuses an open revue tab when there is one. |
| revue_showA | Show the user a file in revue, optionally scrolled to a line or line range. Use this to point at specific code: "look at server.js lines 120-140". With a line it defaults to the whole-file view; without one, to the diff. view "preview" shows a markdown file rendered (with its mermaid diagrams drawn), an SVG drawn as an image, or a mermaid file's diagram. In a plain folder (not a git repo) it is the file or its preview. |
| revue_annotateA | Leave a note on a line or line range, shown inline in revue under those lines (in the diff and the file view), and show it to the user. Use it to explain a change, flag something to review, or ask a question about specific code. Notes belong to the current view (mode/ref/base/head) and are marked outdated if the lines change later. |
| revue_annotationsB | List or clear notes left with revue_annotate. By default this acts on the notes of one view (mode/ref/base/head); all=true covers every view. |
| revue_changesA | List the files changed in a view of the repo (uncommitted work, a commit, or a branch vs its base), with status and added/deleted line counts. Returns text to you; to show changes to the user, use revue_open or revue_show. |
| revue_diffA | Unified diff of one changed file, or of every changed file, in a view of the repo. Includes untracked files in the working tree view. Returns text to you; to show changes to the user, use revue_open or revue_show. |
| revue_logC | Recent commits on a branch (default: the checked-out one), or on all branches. |
| revue_definitionsA | Find where an identifier (function, class, type, variable...) is defined, at the revision a view shows (in a plain folder, in its files). A fast git-grep heuristic, not a compiler: JS/TS, Python, Go, Rust, C-family and shell, with a loose fallback for other languages. The best match comes first, marked with * when it is a clear winner. |
| revue_statusA | List running revue servers (all repos, or one), with their port, lifetime, note storage and open tabs. |
| revue_stopA | Stop the revue server for a repo, if this MCP server or an earlier one started it. Servers the user started by hand are left alone. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 10 tools
Each tool has a mostly distinct role: text-returning inspection (changes, diff, definitions, log), browser presentation (open, show), annotation lifecycle, and server lifecycle. The only mild overlap is revue_show vs revue_open and revue_changes vs revue_diff, but their descriptions clearly distinguish showing code in the viewer from opening the overview and listing changed files from producing a diff.
All tools use the same revue_ prefix and snake_case suffixes, making the namespace predictable. The suffixes mix verbs and nouns (revue_open, revue_stop, revue_annotate vs revue_status, revue_diff, revue_log), but this is a minor deviation rather than an inconsistent scheme.
Ten tools is a well-scoped set for a git change viewer with annotations and server management. Every tool maps to a clear operation: presentation, inspection, annotation, or lifecycle.
The surface covers the core workflows: opening and showing code, listing changes, diffing, finding definitions, viewing logs, creating/listing/clearing annotations, and managing the revue server. Minor gaps exist around editing or deleting individual annotations, but clear-all support and the overall lifecycle are adequate for the domain.