Prism

Official

by Shailesh200 · TypeScript

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.

README.md12 KBView on GitHub

Prism

Local-first Software Intelligence Engine for humans and AI agents.

Website: https://www.prismhq.in · Docs: https://www.prismhq.in/docs · Get started: https://www.prismhq.in/docs/start/get-started

Maps, graphs, blast radius, health — on your machine. No account. Nothing uploaded for core analysis.

Prism is not an AI coding assistant. It is the intelligence layer behind an IDE extension, a CLI, and an MCP server that agents can call.

Get started in 60 seconds
Install — step by step
CLI — commands
MCP — tools & how agents use them
Docs
Privacy
Build from source
License

Get started in 60 seconds

Needs Node.js 22+. No need to clone this repository.

bash

# 1) Go to your project
cd /path/to/your/project

# 2) CLI — no --workspace; uses git root from where you run
npx -y @repo-prism/cli doctor
npx -y @repo-prism/cli dna
npx -y @repo-prism/cli health

# 3) MCP once (Claude Code), then ask in plain English — no tool names:
#    claude mcp add prism -- npx -y @repo-prism/mcp-server
#    “How healthy is this repo?” / “What breaks if I change src/index.ts?”

You want…	Follow
Terminal / CI	A. CLI
Cursor / Claude / Codex agents	B. MCP
Visual map & dashboards	C. IDE extension
Embed in code	`@repo-prism/core`

All surfaces call the same Core SDK. None re-implements analysis.

Install — step by step

A. CLI — `@repo-prism/cli`

cd into your project.
Run doctor:
bash
```
npx -y @repo-prism/cli doctor
```
Confirm Workspace points at your repo (from git root is normal). A warn on Index cache on first run is expected.

Analyse:

bash

npx -y @repo-prism/cli dna
npx -y @repo-prism/cli health
npx -y @repo-prism/cli blast src/index.ts --fail-on high

Optional global install:

bash

npm install -g @repo-prism/cli
prism doctor
prism health --verbose   # shows workspace + index timing

Package: npmjs.com/package/@repo-prism/cli · Guide: CLI docs

B. MCP — `@repo-prism/mcp-server`

Set up once. Then ask the agent in plain language — never type tool names like repository_health. The server tells the agent which tools to call.

One-click (Cursor)

Add to Cursor · Install guide · Benchmarks

Copy-paste config (Cursor / Claude Desktop)

json

{
  "mcpServers": {
    "prism": {
      "command": "npx",
      "args": ["-y", "@repo-prism/mcp-server"]
    }
  }
}

Save as .cursor/mcp.json (project) or add to Claude Desktop config. Enable in Settings → MCP (~40 tools).

Claude Code

cd /path/to/your/project
claude mcp add prism -- npx -y @repo-prism/mcp-server
Restart Claude Code if it was already running.
Ask: “What is this repository?” or “How healthy is this codebase?”

Cursor (manual)

If the one-click link above does not work:

Open the project folder in Cursor.

Create .cursor/mcp.json:

json

{
  "mcpServers": {
    "prism": {
      "command": "npx",
      "args": ["-y", "@repo-prism/mcp-server"]
    }
  }
}

Settings → MCP → enable prism → wait for ~40 tools.
In Agent chat, ask normally (no tool names).

Claude Desktop / Codex

Same npx / @repo-prism/mcp-server config — no --workspace. Full numbered steps for every client: MCP install.

Only add --workspace / PRISM_WORKSPACE if auto-detection picks the wrong folder.

Package: npmjs.com/package/@repo-prism/mcp-server

C. IDE extension (Prism)

Install Prism (Marketplace / Open VSX id prismhq.repo-prism):
- VS Code — Marketplace or search Prism
- Cursor — Open VSX or Install from VSIX
Open Folder on your project.
Command Palette → Prism: Open Prism.
Wait for indexing; use the UI.
(Cursor) Also complete B. MCP so the agent shares the same analysis — IDE install.

CLI — commands

Global flags: -w/--workspace, --json, --no-color, -q/--quiet, --verbose, -y/--yes.

Exit codes: 0 ok · 1 gated finding (--fail-on) · 2 usage error · 3 Prism failed.

Diagnostics

Command	Purpose
`prism doctor`	Environment, workspace chosen, index
`prism index`	Build / refresh the index

Understand

Command	Purpose
`prism dna`	Languages, frameworks, domains, stack
`prism health`	Health score + factors
`prism map [--zoom repo\|package\|feature\|file\|symbol]`	Repository map
`prism explain <path>`	What a path is for / ownership
`prism explore <target>`	Usages, ownership, similar code
`prism stack`	Stack signals
`prism features`	Inferred features
`prism landmarks`	Entrypoints & anchors
`prism packages`	Workspace packages

Assess a change

Command	Purpose
`prism blast <target> [--fail-on low\|mid\|high]`	Blast radius
`prism review [paths…] [--base <ref>]`	Change review
`prism safe-delete <target>`	Safe to delete?
`prism rename <target> <newName>`	Rename edit sites
`prism test-impact <target>`	Related tests

Structure

Command	Purpose
`prism deps`	Graph size / hubs
`prism cycles [--fail-on any]`	Import cycles
`prism symbol <name>`	Find declaration
`prism refs <name>`	Find references
`prism route <from> <to>`	Dependency path

Reports

Command	Purpose
`prism engineering`	Entropy, drift, debt, hotspots
`prism testing`	Suites + on-disk coverage
`prism security`	Left-shift checklist
`prism backend`	Routes, data, env, jobs
`prism bundle`	Bundle weight (ingested stats)

CI sketch:

yaml

- uses: actions/setup-node@v4
  with:
    node-version: "26.5.0"
- run: npx -y @repo-prism/cli review --base origin/main --fail-on high
- run: npx -y @repo-prism/cli cycles --fail-on any

MCP — tools & how agents use them

28 read-only tools + 3 optional prompts (orient, before_edit, review_diff). No network. No consent APIs for agents.

You do not type tool names. After MCP is connected, ask in plain language — the server’s instructions tell the agent when to call which tool.

You say	Agent should call
“What is this repo?”	`repository_dna` / landmarks
“Is it healthy?”	`repository_health`
“What breaks if I edit `src/…`?”	`blast_radius`, `test_impact`
“Can I delete this?”	`safe_delete`
“Review my changes”	`review_changes`

Group	Tools
Orientation	`repository_dna`, `repository_health`, `repository_map`, `repository_overview`, `list_packages`, `stack_profile`, `landmarks`, `explain_area`
Graphs	`dependency_graph`, `dependency_cycles`, `knowledge_graph`, `feature_graph`, `list_features`, `find_symbol`, `find_references`, `dependency_route`
Impact	`blast_radius`, `safe_delete`, `rename_impact`, `test_impact`, `breaking_change_hints`, `review_changes`, `explore_code`
Reports	`engineering_health`, `health_history`, `backend_report`, `testing_report`, `security_report`

Setup steps: MCP install · Full tool list: MCP tools.

Demo — with vs without Prism

Side-by-side script: plans/notes/M-063-demo.md · measured savings: prismhq.in/benchmarks

Ask “What is this repository?” — Prism returns DNA + landmarks in 2–3 calls; a naive agent walks directories.
Ask “Is this edit safe?” on a file — blast_radius replaces scanning the tree for imports.

Reproduce numbers: bun run bench:orientation (after bun run build).

Docs

Site: https://www.prismhq.in/docs

Topic	Link
What Prism is	docs/what-is-prism
Install (CLI / IDE / MCP)	docs/start/install
Quickstart	docs/start/quickstart
Capabilities	docs/reference/capabilities
Task guides	docs/guides
Usage (CLI / IDE / MCP)	docs/usage
Dispatch	docs/guides/dispatch
CLI reference	docs/reference/cli-commands
MCP tools	docs/reference/mcp-tools
Known limitations	docs/help/known-limitations
FAQ	docs/help/faq
Changelog	`CHANGELOG.md`

Markdown sources also live in docs/ in this repo. Local preview: bun run docs:dev

Privacy

Core analysis makes no network requests (proven by a trap test suite). Optional features (GitHub, PageSpeed, Gravatar, …) are off by default and gated per purpose in ~/.prism/workspaces/<key>/consent.json. Agents cannot grant consent.

→ PRIVACY.md · SECURITY.md

Build from source

For contributors (not required to use CLI/MCP):

bash

git clone https://github.com/Shailesh200/prism
cd prism
nvm use          # Node 26.5.0
bun install
bun run build
bun run verify:milestone

See CONTRIBUTING.md.

Published npm packages under this org: @repo-prism (cli, mcp-server, core, and engine libraries).

License

MIT

Install

Configuration

Environment variables

PRISM_WORKSPACE

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.

Arguments

workspace

Add to VS Code Add to Cursor

claude_desktop_config.json

json

{
  "mcpServers": {
    "prism": {
      "command": "npx",
      "args": [
        "-y",
        "@repo-prism/mcp-server@1.1.1",
        "<YOUR_VALUE>"
      ],
      "env": {
        "PRISM_WORKSPACE": "<YOUR_PRISM_WORKSPACE>",
        "CURSOR_API_KEY": "<YOUR_CURSOR_API_KEY>",
        "PRISM_DISPATCH_ROLE": "<YOUR_PRISM_DISPATCH_ROLE>"
      }
    }
  }
}

Prism

io.github.Shailesh200/prism MCP Server

🛠️ Key Features

🚀 Use Cases

⚡ Developer Benefits

⚠️ Limitations

Prism

Table of contents

Get started in 60 seconds

Install — step by step

A. CLI — `@repo-prism/cli`

B. MCP — `@repo-prism/mcp-server`

One-click (Cursor)

Copy-paste config (Cursor / Claude Desktop)

Claude Code

Cursor (manual)

Claude Desktop / Codex

C. IDE extension (Prism)

CLI — commands

Diagnostics

Understand

Assess a change

Structure

Reports

MCP — tools & how agents use them

Demo — with vs without Prism

Docs

Privacy

Build from source

License

Install

Configuration

Related servers

io.github.Shailesh200/prism MCP Server

🛠️ Key Features

🚀 Use Cases

⚡ Developer Benefits

⚠️ Limitations

Prism

Table of contents

Get started in 60 seconds

Install — step by step

A. CLI — @repo-prism/cli

B. MCP — @repo-prism/mcp-server

One-click (Cursor)

Copy-paste config (Cursor / Claude Desktop)

Claude Code

Cursor (manual)

Claude Desktop / Codex

C. IDE extension (Prism)

CLI — commands

Diagnostics

Understand

Assess a change

Structure

Reports

MCP — tools & how agents use them

Demo — with vs without Prism

Docs

Privacy

Build from source

License

Install

Configuration

Related servers

A. CLI — `@repo-prism/cli`

B. MCP — `@repo-prism/mcp-server`