repo-interview
● Activeio.github.Blhasn-Sehli/repo-interview
Interview questions about your own repo or PR, each verified to cite real code.
Connect this server
One click to install, or copy the config below. Suits: Claude Desktop · Cursor.
Or add it manually — claude_desktop_config.json (Claude Desktop) or .cursor/mcp.json (Cursor):
{
"mcpServers": {
"repo-interview": {
"command": "npx",
"args": [
"-y",
"repo-interview@0.3.1",
"mcp"
]
}
}
}claude mcp add repo-interview -- npx -y repo-interview@0.3.1 mcpcodex mcp add repo-interview -- npx -y repo-interview@0.3.1 mcpcode --add-mcp '{"name":"repo-interview","type":"stdio","command":"npx","args":["-y","repo-interview@0.3.1","mcp"]}'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.
A starting point — check the repository for exact arguments and setup. Restart your client after editing the config.
- Category
- Developer Tools
- Version
- 0.3.1
- Registry
- active
- Published
- 11/15/2026
Is it safe? Is it maintained?
Serverdex check: Nov 22, 2026Looks healthy: repo-interview is maintained, open source.
- Maintained
- Active
- Last commit 7 days ago (Nov 15, 2026), 4 open issues.
- Official registry
- Active
- Published as io.github.Blhasn-Sehli/repo-interview in the official MCP registry, version 0.3.1.
- Source
- Open source, MIT
- Public repository under the MIT licence, 0 stars, 0 forks.
- Runs
- On your machine
- A local npm package started by your client; it can reach whatever your user account can.
- Credentials
- None declared
- The registry entry declares no required environment variables.
- 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.
On GitHub
read Nov 22, 2026- Stars
- 0
- Forks
- 0
- Last push
- Nov 15, 2026
- License
- MIT
Shellclicode-reviewdeveloper-toolseducationgithub-actionsllmmcpollama
From the README
repo-interview Website and demo · 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) 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.…
Read the full README on GitHub →Alternatives to repo-interview
All repo-interview alternatives →Best Developer Tools servers →The most-starred Developer Tools servers in the index, with their live-check result.
| Server | Stars | Last push | Live check |
|---|---|---|---|
| REA | 466,935 | Nov 2026 | Local / not checked |
| GitHub | 34,658 | Nov 2026 | Needs sign-in |
| Repomix | 29,280 | Nov 2026 | Local / not checked |
| Compiler Explorer | 19,201 | Nov 2026 | Working |
| XERJ | 19,135 | Nov 2026 | Local / not checked |
repo-interview: questions people ask
- Is repo-interview a remote or a local MCP server?
- According to its entry in the official MCP registry, repo-interview ships as a local package (npm) that your client starts on your machine.
- Is repo-interview safe to use?
- Looks healthy: repo-interview is maintained, open source. In detail — maintained: Active; official registry: Active; source: Open source, MIT; runs: On your machine; credentials: None declared. 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 repo-interview still maintained?
- Active: the repository's last commit 7 days ago. Last push Nov 15, 2026, 0 GitHub stars, MIT licence. Read from GitHub on Nov 22, 2026.
- How do I add repo-interview 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.
More Developer Tools servers
Browse all Developer Tools →Blinkbox
blinkboxhq
Open-source Zapier/n8n alternative as an MCP server: agents build, run and debug your workflows.
Blitz
blitzdotdev
Give AI agents full control over iOS/macOS development via a native macOS app with 30+ MCP tools.
Memnest
Blue-B
Local memory for coding AIs: search past conversations and decisions from the original text.
Blueprint Studio
Blueprint-Studio-AI
Your brand's Styles, logos and asset library in your AI app, for on-brand assets that match.
Aura UI
BlueStarSystem
Discover and install Aura UI Blade components for Laravel, Livewire and Tailwind CSS 4.
Evidrift
bm1016bm-svg
Catch TypeScript API and OpenAPI contract drift in AI-generated code, then revalidate it in CI.
Add the badge to your site
Show visitors that repo-interview is listed here — it’s also the link we check for a free listing.
HTML — for your website
<a href="https://serverdex.io/server/io-github-blhasn-sehli-repo-interview?utm_source=badge"><img src="https://serverdex.io/brand/badge.svg" alt="repo-interview — 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
[](https://serverdex.io/server/io-github-blhasn-sehli-repo-interview?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.
Install buttons — for your README
[](https://serverdex.io/install/cursor/io-github-blhasn-sehli-repo-interview) [](https://serverdex.io/install/vscode/io-github-blhasn-sehli-repo-interview) [](https://serverdex.io/install/claude-code/io-github-blhasn-sehli-repo-interview)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/io-github-blhasn-sehli-repo-interview"><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/io-github-blhasn-sehli-repo-interview"><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/io-github-blhasn-sehli-repo-interview"><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).