repo-interview
What it does
Interview questions about your own repo or PR, each verified to cite real code.
- Connects Runs on your computer
- Account or key No key needed
- Category Developer tools
Use together with
Skills that teach the AI this kind of work; they work alongside this one
archify
Turn any idea, plan, or codebase into a beautiful interactive diagram. An agent skill for Claude Code, Codex, and more.
Why it ranks here
Lists are ordered by a usage score (out of 100) built from these parts
| Popularity | 0/80 | GitHub stars or weekly downloads: the larger counts 60, the smaller 20 |
|---|---|---|
| Freshness | 12/12 | Full marks for a release or code change within 30 days |
| Still answering | 0/8 | The cloud endpoint answered at the last check |
| Usage score | 12/100 |
Quality: Passed 3/3 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)
Install
Pick the AI app you use, then copy the settings.
Passed 3/3 checks · Runs on your computer · ✓ Commands checked Nov 15, 2026
First: which AI do you use?
Pick your app and the steps appear below.
Works with Claude, with some setup first
Install Node.js on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone
Let AI install it
Copy this message into a Claude chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server repo-interview for Claude on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "repo-interview": { "command": "npx", "args": [ "-y", "repo-interview", "mcp" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the repo-interview tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Install Node.js (if you don’t have it)
Already installed? Check first · Open Terminal, type this command and press Enter
node -v- A version number such as v26.13.1 = installed, skip this step
- "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
How to open Terminal
Mac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number:
node -vInstall once; it works for everything that needs Node.js
Open the Claude desktop app’s settings file
SettingsDeveloperEdit Config
Paste these settings and save the file
{ "mcpServers": { "repo-interview": { "command": "npx", "args": [ "-y", "repo-interview", "mcp" ] } } }Quit Claude and open it again
Try it
Use repo-interview and tell me what you can do for me, then show me one thing✓ If Claude says it is using repo-interview or shows a repo-interview tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
ChatGPT cannot connect repo-interview yet
repo-interview runs on your computer, but ChatGPT can only connect servers that run on the web
What you can do instead
A · Use an app that can connect repo-interview
- Install Node.js on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone
- Install Node.js on your computer first (one time)
- Install Node.js on your computer first (one time)
- Install Node.js on your computer first (one time)
B · Others in Developer tools that work with ChatGPT
Picked from the most used in the same category, only ones that connect by address with no key
- Sentry✓ ChatGPT
- Compiler Explorer✓ ChatGPT
- GitDiagram✓ ChatGPT
Works with Claude Code, with some setup first
Install Node.js on your computer first (one time)
Let AI install it
Copy this message into a Claude Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server repo-interview for Claude Code on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): claude mcp add --scope user repo-interview -- npx -y repo-interview mcp 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the repo-interview tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Install Node.js (if you don’t have it)
Already installed? Check first · Open Terminal, type this command and press Enter
node -v- A version number such as v26.13.1 = installed, skip this step
- "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
How to open Terminal
Mac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number:
node -vInstall once; it works for everything that needs Node.js
Open Terminal
Mac: press Command+Space and type Terminal · Windows: open PowerShell
Paste this command and press Enter
claude mcp add --scope user repo-interview -- npx -y repo-interview mcpType /mcp in Claude Code
You should see repo-interview listed as connected
Try it
Use repo-interview and tell me what you can do for me, then show me one thing✓ If Claude Code says it is using repo-interview or shows a repo-interview tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with Cursor, with some setup first
Install Node.js on your computer first (one time)
Let AI install it
Copy this message into a Cursor chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server repo-interview for Cursor on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "repo-interview": { "command": "npx", "args": [ "-y", "repo-interview", "mcp" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the repo-interview tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Install Node.js (if you don’t have it)
Already installed? Check first · Open Terminal, type this command and press Enter
node -v- A version number such as v26.13.1 = installed, skip this step
- "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
How to open Terminal
Mac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number:
node -vInstall once; it works for everything that needs Node.js
Open the AI chat in Cursor in Agent mode
Try it
Use repo-interview and tell me what you can do for me, then show me one thing✓ If Cursor says it is using repo-interview or shows a repo-interview tool in the answer, you are connected
Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with VS Code, with some setup first
Install Node.js on your computer first (one time)
Let AI install it
Copy this message into a VS Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server repo-interview for VS Code on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "servers": { "repo-interview": { "type": "stdio", "command": "npx", "args": [ "-y", "repo-interview", "mcp" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the repo-interview tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Install Node.js (if you don’t have it)
Already installed? Check first · Open Terminal, type this command and press Enter
node -v- A version number such as v26.13.1 = installed, skip this step
- "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
How to open Terminal
Mac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number:
node -vInstall once; it works for everything that needs Node.js
Open the AI chat in VS Code in Agent mode
Try it
Use repo-interview and tell me what you can do for me, then show me one thing✓ If VS Code says it is using repo-interview or shows a repo-interview tool in the answer, you are connected
Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version
For developers: Terminal commands and JSON settings
Installed on your computer
Claude Code
claude mcp add --scope user repo-interview -- npx -y repo-interview mcpClaude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"repo-interview": {
"command": "npx",
"args": [
"-y",
"repo-interview",
"mcp"
]
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"repo-interview": {
"command": "npx",
"args": [
"-y",
"repo-interview",
"mcp"
]
}
}
}VS Code (mcp.json)
{
"servers": {
"repo-interview": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"repo-interview",
"mcp"
]
}
}
}These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
At a glance
- Downloads per weeki
- 53/wk
- Connection
- Runs on your computer
- Latest versioni
- 0.3.1
- Categoryi
- Developer tools
- Published to registryi
- Nov 15, 2026
- Code last changedi
- Nov 15, 2026
- Maker
- Blhasn-Sehli
- Packages
npm: repo-interview- Website
- blhasn-sehli.github.io
- Registry status
- Active
Which apps can use it
Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.
Run on your computer in
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
Related guides
What it can do
Runs on your computer; the tool list appears in your AI app after you install it.
Basic checksi
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 16, 2026
- ✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account Blhasn-Sehli, which owns the repo
- ✓ Pass
Still maintained
Code last changed yesterday
- ✓ Pass
Has a licence
Uses MIT
- – Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
- – Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
- … Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints
Published vulnerabilities (OSV.dev)
No entries on OSV.dev for repo-interview@0.3.1
Checks only this package version, not every dependency · checked Nov 16, 2026
Makers: ask for a re-check or report wrong info
For makers: add a badge to your README
If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/servers/blhasn-sehli-repo-interview)Discussion
Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
User reviews
No reviews yet
Compared with others in Developer toolsi
- More stars than 0% of the other 5964 servers in this category
- Published to the registry more recently than 97% of the other 5964 servers in this category
- Basic checks equal to or better than 100% of the other 5964 servers in this category
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
Common questions
Is repo-interview safe?
It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
What keys or codes does it need?
The registry does not list a required key, though some servers ask you to sign in on first use.
Does it run on my computer or in the cloud?
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
Is it still maintained?
The GitHub repo last changed yesterday, and the latest version (0.3.1) reached the registry yesterday.
Which apps can use it?
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
What can I use instead?
In the same category: GitDiagram, Appllama, Cloudflare MCP, Omnara, Repowise
Similar alternatives
Same category, other makers, commands already checked. Official ones first, then by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
GitDiagram
Architecture diagrams, explanations and Mermaid source for public GitHub repositories.
Appllama
Study screens, flows and paywalls from top-earning iOS apps, then build from what wins.
Cloudflare MCP
Cloudflare MCP servers
Omnara
Deploy durable AI agents with Omnara, an open-source managed-agent platform.
Repowise
Codebase intelligence for AI coding agents: graph, git history, docs, decisions, code health.
| This one repo-interview | GitDiagram | Appllama | Cloudflare MCP | Omnara | Repowise | |
|---|---|---|---|---|---|---|
| Runs where | Installs on your computer | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Cloud or install on your computer |
| Needs a key | No | No | No | No | No | No |
| Add with + in Claude | No | No | No | Yes | No | No |
| Basic checks | 3/3 | 4/4 | 4/4 | 4/4 | 4/4 | 5/5 |
| License | MIT | MIT | MIT | Apache-2.0 | Apache-2.0 | AGPL-3.0 |
| Price | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry |
README from the maker
Open the README
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
repo-interview
[Website and demo](https://blhasn-sehli.github.io/repo-interview/) · npm
Can you explain your own code? repo-interview reads your repository or pull request and asks you the questions an interviewer or reviewer would: what it does, why it is built this way, and how specific code works. Then it grades your answers and tells you what to study.
Every question cites a real file and symbol. A verifier checks each citation and drops any question about code that does not exist, so the model cannot quiz you on something it made up. It runs on a free local model, so your code stays on your machine.
Who it is for
- Students and job seekers preparing to explain a portfolio project, especially one built with AI help.
- Developers who want to check they really understand a codebase before they own it.
- Teams who want authors to explain their own pull requests (advisory, never blocking).
Quick start (terminal)
ollama pull qwen2.5-coder:3b
npx repo-interview interview . --provider ollama --model qwen2.5-coder:3b
You get 8 questions (3 big-picture, 3 about specific code, 2 asking you to predict what a function does). Answer each on one line; a weak answer gets one follow-up. At the end interview-report.md shows your score and links to the files to study.
Needs Node.js 22+ and Ollama. Package: repo-interview on npm.
Three kinds of questions
- Big picture: what the project does, its main parts, and why it is built this way.
- Code: how and why a specific function works: control flow, error handling, trade-offs.
- Predict: what a specific function returns, throws or does for a given input. These come from your own tests first:
t.is(getBodySize('hello'), 5)becomes "getBodySizeis called with'hello'. What will the output be?", and the answer is the test's assertion, not a model's guess. When too few tests fit, the rest become code questions. With--predict-from tests+modelthe model also writes predictions from the code, quoting the lines its answer relies on; use that only with a large model, because a small local model got most of them wrong in testing.
Choose with --kinds overview,code,predict (default all three).
Inside Claude (MCP): no Ollama needed
Let Claude (or any MCP client) run the interview with its own model, while repo-interview keeps it honest:
claude mcp add repo-interview -- npx -y repo-interview mcp
Then, in your project, ask Claude to "interview me about this repo", or use the interview prompt (pr_interview for the current branch). Claude reads the code and writes and grades the questions; repo-interview's tools list what exists (scan_repo), show the cited code (read_code), list a branch's changes (pr_changes), offer predict questions taken from your tests (test_cases) and drop any question about code that does not exist (check_questions). The tools only read files, never run them, and refuse paths outside the project.
On pull requests (GitHub Action)
Posts one comment with 3 questions about the PR's own change: what it adds, how the changed code works, and what it will do for a given input. It runs a small model with Ollama on the GitHub runner: free, no API key, and the code stays on the runner. It is advisory and never fails the PR.
name: PR questions
on: pull_request permissions: contents: read pull-requests: write jobs: questions: runs-on: ubuntu-latest steps:
- uses: actions/checkout@v7 with: fetch-depth: 2
- uses: Blhasn-Sehli/repo-interview@main
On this repo's first run the whole step, including installing Ollama and downloading the model, took 86 seconds, of which the model took 45. Pull requests from forks get a read-only token, so their questions go to the job summary instead of a comment.
To score the author's answers, add a second workflow. When the PR's author replies with numbered answers (1., 2., 3.), it grades each one 0-3 against the cited code and posts one scores comment, edited again if they reply again. The PR's code is fetched into a separate folder and only read, never run.
name: PR answers
on: issue_comment: types: [created] permissions: contents: read pull-requests: write jobs: score: if: github.event.issue.pull_request && github.event.comment.user.login == github.event.issue.user.login runs-on: ubuntu-latest steps:
- uses: actions/checkout@v7
- uses: Blhasn-Sehli/repo-interview@main
Commands
| Command | What it does |
|---|---|
interview | Questions in your terminal, each answer graded 0-3, one follow-up after a weak answer, then a report |
questions | Just the questions; --kinds, --overview and --predict set the mix |
pr --base main | 3 questions about only the code changed since main (1 about what it adds, 1 about code, 1 predict) |
scan | The files and symbols questions can cite |
mcp | Run as an MCP server for Claude and other MCP clients |
Providers: --provider ollama (local, free), anthropic (ANTHROPIC_API_KEY) or openai (any OpenAI-compatible server, OPENAI_API_KEY). --record and --replay save and replay model replies, so runs can be checked offline.
How well it works (measured)
On 10 public repositories in 10 languages, with the small local model qwen2.5-coder:3b, big-picture and code questions only, an average of 3 runs has 90.7% of generated questions citing real code under the strict check (runs ranged 86.3-95.8%) and 92.8% under the fair check. The verifier removes the rest before you see them. Every number comes with its recorded model replies, so you can recheck it offline: see the test corpus.
Not measured yet: how well grading agrees with a human, how useful testers find the questions, and how often a model-written prediction's expected answer is right (predictions taken from tests use the test's own answer). All are in progress.
How it is different
Other tools also ask authors about their code or pull requests, for example comprehension-gate, PR Guard, CCG, Gater, churn interview and PathFinder. repo-interview's focus:
- Checked citations. A question reaches you only if the file and symbol it cites exist (and, for a PR, were changed by it), and the rate is measured and published.
- Local and free by default. Ollama on your machine or on the GitHub runner; no account, no API key, no code sent anywhere.
- For learning, not only gating. The terminal interview ends with a report of what to study, which suits students and job interview practice.
Status
Early: expect rough edges. Symbols come from tree-sitter for TypeScript, JavaScript and Python and from patterns for Go, Rust, Java, Kotlin, C#, C/C++, Ruby and PHP. Answers in the terminal are one line each. See SECURITY.md for how it handles untrusted code, and CONTRIBUTING.md to help.
Thanks
Prediction questions, including generating them from your existing tests, were suggested by Jason Gorman (Codemanship).
License
MIT