Prism
Local-first repo intelligence for agents: DNA, health, blast radius, and Dispatch jobs.
Que pouvez-vous faire avec Prism ?
- Prepare, before the agent edits. The files and tests that matter for
- Match the code, during the edit. Prism points at a file from your repo
- Lens review, after. Dev, Architect and QA lenses flag the callers the
- The receipt, when the agent stops. Prism runs the checks the change
Installation
Ajoutez ceci à la configuration MCP de votre client (Claude Desktop : claude_desktop_config.json ; Cursor : .cursor/mcp.json ; VS Code et les autres utilisent la même forme « mcpServers »).
@repo-prism/mcp-serverclaude mcp add prism -e 'PRISM_WORKSPACE=<PRISM_WORKSPACE>' -e 'CURSOR_API_KEY=<your cursor_api_key>' -e 'PRISM_DISPATCH_ROLE=<PRISM_DISPATCH_ROLE>' -- npx -y @repo-prism/mcp-server@1.1.1 '<workspace>'{
"mcpServers": {
"prism": {
"command": "npx",
"args": [
"-y",
"@repo-prism/mcp-server@1.1.1",
"<workspace>"
],
"env": {
"PRISM_WORKSPACE": "<PRISM_WORKSPACE>",
"CURSOR_API_KEY": "<your cursor_api_key>",
"PRISM_DISPATCH_ROLE": "<PRISM_DISPATCH_ROLE>"
}
}
}
}Variables d'environnement
PRISM_WORKSPACEOptional override when the MCP client starts from a directory outside the project.CURSOR_API_KEYsecret Optional override to spawn local Cursor SDK workers. Prefer prism init / first start_job (Cursor.auth.login). Do not put this in mcp.json for normal use.PRISM_DISPATCH_ROLESet to worker to skip Intelligence tools and hide start_job / start_my_day / init. Dispatch job agents do not attach Prism MCP.
Documentation
Tirée du README du projet sur GitHub, actualisée chaque semaine. Les liens ouvrent GitHub.
Prism
Your agent's second pair of eyes. Know before you ship.
Local software intelligence that catches what the agent missed. Prism gives your coding agent the right files before it edits, then flags the code it skipped and the code no test covers. Free, MIT, and it runs on your machine: no account, and your code never leaves it.
Website: prismhq.in · Docs: prismhq.in/docs · Contact: hello@shaileshjha.in
Get started
npm install -g @prismapp/cli && prism install allRun the second command inside your repository. prism install all connects
every agent it finds. Quit the agent and open it again. The first use builds
the index under ~/.prism/. One agent only: pass its name to prism install.
The install records what it wrote in ~/.prism/install.json, and
prism uninstall removes exactly that. A new version is
npm install -g @prismapp/cli then prism upgrade. Memories, receipts, and
habits stay.
Wiring another MCP host by hand? Use this server entry:
{ "mcpServers": { "prism": { "command": "npx", "args": ["-y", "@prismapp/mcp-server"], "env": { "PRISM_EXTRA_TOOLS": "receipt" } } } }Then ask your agent in plain language, for example "what breaks if I change
src/index.ts?" or "review my changes". You never type tool names.
What it does
- Prepare, before the agent edits. The files and tests that matter for the task, and the helpers to reuse instead of rewriting.
- Match the code, during the edit. Prism points at a file from your repo to copy, so the new code looks like the rest.
- Lens review, after. Dev, Architect and QA lenses flag the callers the
change left behind and the code no test covers. Add your own with
prism lens. - The receipt, when the agent stops. Prism runs the checks the change
reaches and gives one verdict:
SHIP,NOT PROVEN(with the cheapest check to prove it) orNO-SHIP.
Nine default MCP tools; more are opt-in through extraTools in
~/.prism/config.json. Full list: MCP tools.
| You say | The agent calls |
|---|---|
| "What is this repo?" | repository_overview |
| "I want to change X" | prepare_change |
| "What breaks if I edit this file?" | blast_radius, test_impact |
| "Where is this symbol, who uses it?" | graph |
| "Review my changes" | guard_session (review: true) |
| "Start my day" (a saved routine) | habits |
| "Did I break anything?" | the stop receipt, run by the hook |
CLI
Every command answers from the same local index. Highlights:
| Command | What it answers |
|---|---|
prism prepare <task> | The files to open and the helpers to reuse |
prism review [paths] --lens qa | A lens review of a change |
prism blast <target> | What depends on a file or symbol |
prism test-impact <target> | Which tests reach a file |
prism receipts | The last stop receipts |
prism lens, prism habit | Your review lenses and saved routines |
prism doctor | What is wired, and whether it works |
Full list: CLI reference.
Privacy
Analysis makes no network requests; a trap test suite fails the build if
one appears. The only request Prism makes is a once-a-day update check against
the npm registry, which never relaunches anything and is off with
PRISM_SKIP_SELF_UPDATE=1. → PRIVACY.md · SECURITY.md
Build from source
git clone https://github.com/Shailesh200/prism
cd prism
nvm use # the version in .nvmrc
bun install
bun run build
bun run verify:milestoneSee CONTRIBUTING.md and the changelog.
License
Questions fréquentes
Qu'est-ce que Prism ?
Local-first repo intelligence for agents: DNA, health, blast radius, and Dispatch jobs.
Comment installer Prism ?
Il s'exécute sur votre machine. Dans Claude Code : claude mcp add prism -e 'PRISM_WORKSPACE=<PRISM_WORKSPACE>' -e 'CURSOR_API_KEY=<your cursor_api_key>' -e 'PRISM_DISPATCH_ROLE=<PRISM_DISPATCH_ROLE>' -- npx -y @repo-prism/mcp-server@1.1.1 '<workspace>'. Pour les autres clients, collez la configuration JSON de cette page dans leurs réglages MCP.
Faut-il une clé API pour Prism ?
Oui. Il attend CURSOR_API_KEY, à renseigner dans sa configuration.
Prism est-il open source ?
Oui. Son code est sur GitHub sous licence MIT.
Qui maintient Prism ?
Il est publié par Shailesh200. AI.tn le référence sans le maintenir ni le recommander.
Issu du registre MCP officiel. Être listé n'est pas une recommandation : vérifiez le code et les permissions d'un serveur avant de lui donner accès à vos données.