# Prism [Health: Active]

**Category:** 🧬 Biology & Bioinformatics  
**Repository:** https://github.com/Shailesh200/prism  
**GitHub Stars:** 10  
**npm Downloads (last month):** 209  
**Views:** 2  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/prism

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

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "prism": {
    "command": "npx",
    "args": ["-y","@repo-prism/cli"]
  }
}
```

## Documentation

## What Prism MCP server does

The Prism MCP server analyzes a local software repository and exposes the resulting repository intelligence to MCP-compatible agents. Its analysis covers repository identity, languages, frameworks, domains, stack signals, packages, landmarks, ownership, dependency relationships, and inferred features.

It is intended for software repositories rather than biological datasets. The server helps an agent answer questions such as what a repository contains, how healthy it is, which files or symbols depend on a target, what tests may be affected, and whether a proposed deletion appears safe.

Core analysis stays on the developer’s machine. The README states that the MCP interface has 28 read-only tools and three optional prompts. It does not provide network access or consent APIs for agents.

## How it works

The package is launched with Node.js and `npx`, using `@repo-prism/mcp-server`. MCP client configuration starts the server in the project context, where it can inspect and index the repository. Normally, the workspace is detected from the project or Git root; `--workspace` or `PRISM_WORKSPACE` is only needed when automatic detection selects the wrong folder.

Agents are expected to receive the server’s instructions and select tools from natural-language requests. Developers can ask about repository health, the effect of editing a file, or the safety of removing a symbol without manually entering tool names.

The available analysis is read-only. It can report repository facts and assessments, but the provided material does not describe tools that modify source files, run consent workflows, or upload core analysis elsewhere.

## Setup and configuration

Use Node.js 22 or newer. Add the server to an MCP client with a command equivalent to:

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

Cursor users can place this configuration in `.cursor/mcp.json`. The same `npx` configuration can be added to Claude Desktop and Codex. Claude Code can register it with `claude mcp add prism -- npx -y @repo-prism/mcp-server`. The setup guide also documents a Cursor one-click installation.

Run the configuration from, or associate it with, the repository you want to inspect. If the client chooses the wrong directory, provide the workspace explicitly with the supported workspace option or environment variable.

## Tools and capabilities

The Prism MCP server groups its tools around several repository-analysis tasks:

- **Orientation:** repository DNA, health, maps, overviews, packages, stack profiles, landmarks, and area explanations.
- **Graphs:** dependency graphs, dependency cycles, knowledge graphs, and feature relationships.
- **Change impact:** blast-radius analysis, test impact, change review, safe-delete checks, and rename-site discovery.
- **Repository navigation:** symbol declarations, references, dependency routes, ownership, usages, and similar code.

Optional prompts include `orient`, `before_edit`, and `review_diff`. Example agent requests include identifying the repository, checking its health, finding what breaks when a path changes, deciding whether an item can be deleted, and reviewing current changes.

## Limitations and notes

This interface is designed for local repository intelligence, not as an AI coding assistant. The README distinguishes it from an assistant that directly writes code. Analysis depends on indexing the selected workspace, and the first run may show an expected index-cache warning. The supplied material does not specify language coverage, supported repository sizes, or detailed scoring methodology, so those should be verified before adopting it for a particular codebase.

_Full upstream README: https://allmcps.com/mcp/prism/readme_