Prism

io.github.Shailesh200Published by GitHub account Shailesh200v1.1.1Updated Nov 3, 2026

Local-first repo intelligence for agents: DNA, health, blast radius, and Dispatch jobs.

VerifiedSTDIODesktop onlyKnowledge & Memory Developer Tools

Server details

Identifier: io.github.Shailesh200/prism
Transport: STDIO
Runtime: Desktop only
Trust: Verified
Published: Sep 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified the GitHub account Shailesh200 for this listing. That does not show the account is the product's maker.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.github.Shailesh200%2Fprism.svg)](https://sourceweft.com/mcp/io.github.Shailesh200%2Fprism?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

Local-first repo intelligence for coding agents: repository overview, change preparation, blast radius, test impact and review receipts.

What you can do: Inspect a repository and get an overview of its structure and conventions
Prepare a change by finding the files, tests and helpers that matter for a task
Analyze impact: what depends on a file or symbol, and which tests reach it
Locate symbols and their callers through a code graph
Review changes with Dev, Architect and QA lenses, plus saved routines and stop receipts
When to use it: Useful when a coding agent edits an unfamiliar or large repository and you want it to find the right files first, catch callers it left behind, and get a ship or no-ship verdict on a change.
Requirements: Runs locally over stdio, typically via npx with the published npm package; a global CLI install and an install step inside the repository are described. The first run builds an index under the user's home directory. No account is required.

Before you install

The optional CURSOR_API_KEY secret can spawn local Cursor SDK workers; the README advises against putting it in the MCP client config for normal use. The server reads and indexes your repository locally and writes index and install records to the home directory; a once-a-day npm update check can be disabled with PRISM_SKIP_SELF_UPDATE.

Installation

In SourceWeft

Open Prism in the dashboard and add it to a workspace.
Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

[Prism: your agent’s second pair of eyes. Know before you ship.]

Prism

[Website] [npm @prismapp/cli] [License: MIT]

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: [email protected]

Get started

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:

json

{ "mcpServers": { "prism": { "command": "npx", "args": ["-y", "@prismapp/mcp-server"], "env": { "PRISM_EXTRA_TOOLS": "receipt" } } } }

{ "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) 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:

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

bash

git clone https://github.com/Shailesh200/prismcd prismnvm use          # the version in .nvmrcbun installbun run buildbun run verify:milestone

git clone https://github.com/Shailesh200/prismcd prismnvm use          # the version in .nvmrcbun installbun run buildbun run verify:milestone

See CONTRIBUTING.md and the changelog.

License

MIT

Source: README.md at commit 9f67df5

Tools

SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

v1.1.1LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
License10 pts