Local-first repo intelligence for agents: DNA, health, blast radius, and Dispatch jobs.
io.github.Shailesh200/prism MCP Server
The Model Context Protocol (MCP) server io.github.Shailesh200/prism provides local-first repository intelligence for agents. Its description highlights analysis focused on “DNA, health, blast radius, and Dispatch jobs,” using a Prism-based approach for gathering and interpreting repo-related signals.
🛠️ Key Features
Local-first repository intelligence
Repository analysis focused on: DNA
Repository analysis focused on: health
Repository analysis focused on: blast radius
Repository analysis focused on: Dispatch jobs
🚀 Use Cases
Agent workflows that need repository DNA signals
Detecting repository health indicators for automated decisions
Assessing blast radius for changes in a repo
Running or coordinating “Dispatch jobs” from within agent tooling
⚡ Developer Benefits
Structured repo intelligence tailored for agent consumption
MCP integration surfaced via the @repo-prism/mcp-server package
⚠️ Limitations
The available description does not specify supported platforms, configuration options, authentication, or output schema beyond the listed analysis categories.
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.
Run 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:
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) or NO-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:
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
bash
git clone https://github.com/Shailesh200/prism
cd prism
nvm use # the version in .nvmrc
bun install
bun run build
bun run verify:milestone
Optional 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_ROLE
Set to worker to skip Intelligence tools and hide start_job / start_my_day / init. Dispatch job agents do not attach Prism MCP.