@alucify/mcp

Lightweight MCP server that gives Claude Code read-only access to your project's Alucify appgraph — a structured model tracing requirements through implementations to validations.

Quick Start

Add to your project's .mcp.json:

{
  "mcpServers": {
    "alucify": {
      "command": "npx",
      "args": ["@alucify/mcp"]
    }
  }
}

Requires a .alucify/ directory with an appgraph (generated by alucify analyze-code or committed by a teammate).

Tools

| Tool | Description | |------|-------------| | query_context | Search nodes by type, name, subtype, or status | | get_context | Full node detail with DSL definitions and connected nodes | | trace_dependencies | Blast radius analysis for file changes | | get_remaining_work | Unimplemented requirements, untested validations | | diff_context | Compare two versions | | get_analysis | Congruency, coverage, and quality report summaries | | link_context | Link a node to its implementation file for progress tracking |

How It Works

The MCP server starts as a subprocess when Claude Code connects. It reads .alucify/appgraph-project.json on each tool call (cached for 5 seconds). All operations are read-only.

For the full tool reference and CLAUDE.md setup, see the MCP Server documentation.

Related

• @alucify/cli — CLI with analysis, commit tracking, and Claude Code integration (npx @alucify/cli)
• Alucify VS Code Extension — Full UI with dashboard, visualizer, and chat
• alucify mcp-install — CLI command that vendors the MCP server into .alucify/ for zero-install team sharing