Skip to content
Agentmart
Submit a tool

Prism

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

Connector by Shailesh200 · GitHub account verified by the MCP Registry

IndexedMITLocal (stdio)★ 10
Write a review

Chalk Labs

Need help deploying Prism?

Chalk Labs sets up agents like this inside real teams: connected to your tools, tested on your data, with a human in the loop where it matters.

Book a call

Install

Works with Claude Code, Codex, VS Code, Cursor, Windsurf, Claude Desktop. Read the repository before you give any tool access to your data.

npx agentmarket install connector/shailesh200-prism

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

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

Use cases: code-review, refactoring, testing

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this server can do and what it asks for, from its tool list, install config and code. Checked Oct 25, 2026.

Runs code on install

Its package runs an install script (such as npm postinstall or setup.py code) as soon as you install it, before any tool is called. Read the script first.

Tools
8 read · 2 write · 1 delete · 10 not yet classified
Secrets
1 (API keys, tokens or passwords)
Install scripts
Runs code on install
Runs as
Node.js package

Tools by what they do 21

Read from the source code; the running server may list different tools.

Read 8 · Look things up without changing anything.

  • capabilities
  • explain_area
  • explore_code
  • guard_session
  • list_findings
  • list_packages
  • review_with
  • workspace_status

Write 2 · Create, change, send or run things.

  • dependency_cycles
  • rename_impact

Delete 1 · Delete, drop, revoke or wipe things.

  • safe_delete

Not yet classified 10 · We could not tell from the name and description.

  • agents_md
  • blast_radius
  • dependency_graph
  • graph
  • habits
  • knowledge_graph
  • prepare_change
  • receipt
  • repository_overview
  • test_impact

Secrets and settings it asks for

Secrets: values you paste in that let it act as you.

  • CURSOR_API_KEY

Other settings (environment variables or headers).

  • PRISM_DISPATCH_ROLE
  • PRISM_WORKSPACE

Network hosts it talks to 11

  • api.github.com · found in code
  • github.com · found in code
  • json.schemastore.org · found in code
  • marketplace.visualstudio.com · found in code
  • moonrepo.dev · found in code
  • open-vsx.org · found in code
  • openapi.vercel.sh · found in code
  • prismhq.in · found in code
  • pulse.shaileshjha.in · found in code
  • raw.githubusercontent.com · found in code
  • shaileshjha.in · found in code

Files it touches

  • ~/.claude.json
  • ~/.claude/settings.json
  • ~/.claude/skills
  • /dev/null
  • /Library/Containers
  • /private/tmp
  • /private/tmp/claude-
  • /sys/class/power_supply
  • /tmp/prism-ab
  • /tmp/prism-bench
  • /tmp/prism2/hookbench
  • Your home directory (~)
  • ~/.codex/AGENTS.md
  • ~/.codex/config.toml
  • ~/.config/opencode/AGENTS.md
  • ~/.config/opencode/opencode.json
  • ~/.config/opencode/plugins/prism.js
  • ~/.cursor/mcp.json
  • ~/.prism/config.json
  • ~/northwind
  • ~/Prism
  • Any path the agent passes to its tools

Tools (21)

Read from the source code; the running server may differ. Descriptions are the server’s own words; hidden characters are shown as [U+…].

  • agents_mdLiving AGENTS.md

    Generate or verify the Living AGENTS.md: features, import cycles, test locations, and git ownership, composed straight from the index — no LLM prose. `generate` writes it to `~/.prism/workspaces/<key>/agents.md`, never into this repo, so it never needs its own commit. `check` re-verifies the claims it made against a fresh index and reports drift. Read `prism://agents-md` for the current content without regenerating.

  • blast_radiusBlast radius

    What depends on a file or symbol, and how risky changing it is: direct and transitive dependents, confidence lanes, evidence and a risk band. Results are import/soft-lane based — coverageLimitations lists classes it cannot see (DI containers, string-keyed registries, event buses, template/i18n refs, runtime-loaded config, generated-code consumers). Call this before editing or deleting code you did not write. Use intent 'delete' when removing rather than modifying. affectedFiles and testsLikelyAffected are bounded (default 50).

  • capabilitiesCapabilities

    List every Core analysis capability with availability and a reason when unavailable. Use this to tell 'not supported by this build' apart from a real failure.

  • dependency_cyclesDependency cycles

    Import and re-export cycles, each returned as the list of files forming the loop. Use when investigating build order, flaky module initialisation, or before extracting a package.

  • dependency_graphDependency graph

    The import/re-export dependency graph, at file level or aggregated to packages. Includes unresolvedImports { count, sample } for specs that did not resolve into the graph. Bounded by default (limit 50 nodes); use summaryOnly for counts + top-degree nodes. Prefer packageAggregation, or use blast_radius if your question is about one file rather than the whole graph.

  • explain_areaExplain area

    Explain what a module or folder does: domain overlap, dependency in/out degree and local ownership. Use before editing an unfamiliar directory. For a single file target prefer explore_code (richer usages/ownership/timeline). Deterministic — derived from the index and local git, never generated prose.

  • explore_codeExplore code

    Everything about one file or symbol in a single call: usages, ownership, related and similar code, and a change timeline. Usages are bounded (default 50) via a nested wrapper so large files do not drown the response. Use when asked to understand a specific thing rather than the repository as a whole.

  • graphRepository graph

    One structural question about the repository, answered from Prism's local graph. Modes: find, neighbors, path, explain, query, symbol (signature/body), map (compact cached repo map of signatures + callers/callees; default budget 4000). Every edge says measured, heuristic or inferred. Bounded by `budget` tokens; `truncated` says when it was cut.

  • guard_sessionGuard the current session

    Check my changes. With review:true, write the review from `review.reading` and do not print risk scores. Start with what the change does, then the finding count, with no Receipt on that line. Bold each group title: Critical, High, Low, and Nit. Number findings straight through. Bold each finding title. Under it, an unordered list: This code, Breaks when, Change, and Left as is. Keep `reading.notes`; a Critical stays Critical. Read `reading.targets` and only the callers and tests listed there, in the order correct, safe, load, tested, speed, then smaller code. A finding needs a concrete case. A…

  • habitsHabits

    The user's saved routines (e.g. 'start my day'). With no name: the list of habits. With a name: the ordered steps (source, action, filter) and output format. Prism fetches nothing: run each step yourself with your connected tools, then write the result in the given format. Each habit is a skill file in ~/.prism/skills; users manage them with `prism habit add|list|show|edit|remove`.

  • knowledge_graphKnowledge graph

    The symbol-level graph — declarations and the references between them — with summary stats. Requires path (scope to one file) or limit (bound nodes). Very large on a big repository. If you are looking for one symbol use graph (mode find), and for its callers graph (mode neighbors, direction in).

  • list_findingsList findings

    Queueable findings from the last index: unused exports, duplicate implementations (two files exporting the exact same name), and wrapper functions (a function whose whole body is one call to another export). Each row is structured: what, where, fix, riskIfSkipped, sources, plus its fingerprint. Excludes findings the user has muted, unless includeMuted is set.

  • list_packagesList packages

    List the packages in a monorepo with their roots. Call this first in a monorepo so later tools can be scoped with packageId instead of returning the whole workspace.

  • prepare_changePrepare a change

    One call before you edit: `prism`, a one-line summary to start your reply with, the lens to work by (its steps, e.g. the smallest complete change), the files to open for this task (pack with exported signatures and path:line anchors), existing helpers to reuse, one House Style pointer, notes (remembered facts and ADR rationale), and a work order. Bodies only for the top symbol when it is ≤ 40 lines; otherwise call graph {mode:"symbol", path, name, body:true}. The whole answer fits a token budget (default 2000); when it is cut, `trimmed` says what was dropped. Ambiguous names come back as candi…

  • receiptChange receipt

    What this session changed and whether it is proven: changed files, dependents, the tests that reach them, and a verdict — SHIP, NOT PROVEN (reason, with the cheapest check that would prove it) or NO-SHIP. Checks run in the background and each call waits up to 20 s for them; while they run, `next` says whether to call again. Call this before saying a coding task is done and quote the verdict in one line.

Show 6 more tools
  • rename_impactRename impact

    Every edit site a rename would touch, plus breaking-change hints for public surface. Use before renaming an exported symbol or moving a file. A report only — Prism never edits.

  • repository_overviewRepository overview

    What this repository is, in one bounded call: languages, frameworks, package manager, test runners and ranked domains (dna), the detected stack, and the landmarks a human would open first (entrypoints, package roots). Start here when you know nothing about a codebase. Local index only; no network.

  • review_withReview with lenses

    Review a task or the current change through a lens. Architect, QA, and Dev are the defaults; the owner can add their own. Omit lenses and Prism picks one from the task: a plan, a new feature, or a pull request uses Architect; finding bugs uses QA; a daily fix uses Dev. Naming a lens uses that one, including a custom lens. action=brief returns that lens's procedure, checklist, memory, and evidence for you to follow. action=record stores the verdict. Prism does not call a model.

  • safe_deleteSafe delete

    Whether a file or symbol can be deleted safely: blockers that still depend on it, and files that would be orphaned if it went. A report only — Prism never deletes anything. Prefer this over blast_radius when the question is specifically about removal.

  • test_impactTest impact

    Which tests import the changed symbol, or a symbol that reaches it — the tests worth running after touching a target. Each test carries reason and viaSymbol; `run` gives one ready command per package (cwd, command, argv) with its runner (vitest, jest, mocha, bun, node:test) and package manager — run it as given. Prism never runs it. The tests list is bounded (default 50).

  • workspace_statusWorkspace status

    Compact workspace readiness: path, whether an index is loaded, indexedAt, freshness, git availability, whether a Prism cache directory exists, and dependency-graph node/edge counts. Call this when a previous tool failed or to confirm the session is ready before a review.

Signals

Stars
10
Forks
0
Open issues
1
Last commit
Oct 19, 2026 (11 days ago)
Last release
Sep 7, 2026 (1 month ago)

From GitHub (fetched Oct 24, 2026).

Details

Registry name
io.github.Shailesh200/prism
Version
1.1.1
Auth
API key
License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

Done for you

Rather not set it up yourself?

Chalk Labs scopes, builds and runs agents for your team: the task audit, the eval harness, the integrations and the weekly ops report. Fixed scope, priced before we start.

See how we build AI agents →Read the case studies

Chalk Labs is a two-founder AI and growth studio. We build AI agents, CRMs and MVPs for Web3 and AI companies, and have shipped 50+ product and token launches.

launches shipped
50+
launches shipped
media placements
500+
media placements
founders on every account
2
founders on every account

Press we've placed: Forbes · CoinDesk · Decrypt · Cointelegraph · The Block

Rahil Jain, Co-founder, Chalk Labs. Ex-Goldman Sachs engineer. You talk to the person who builds it.

Get Prism running in your business

Tell us what you want to automate. A founder replies within one working day with a plan, not a pitch deck.

Goes to the Chalk Labs founders, not the newsletter. Privacy

Need help deploying Prism?

CallGet help
Cite this page

Prism MCP server. Agent Mart. https://agentmart.dev/connectors/shailesh200-prism (last updated 2026-10-24)