MCP Getting Started

Install LogicStamp Context MCP server to give Claude Desktop, Claude Code, or Cursor direct access to your codebase.

Prerequisites

•Node.js >= 20
•LogicStamp CLI — stamp on your PATH (the MCP server shells out to it)
•MCP-capable assistant — Claude Desktop, Cursor, Claude Code, or another MCP client
•TypeScript project — LogicStamp analyzes .ts / .tsx only

npm install -g logicstamp-context

Installation

Install the MCP server globally:

npm install -g logicstamp-mcp

Prepare your project

Before tools return useful data, initialize LogicStamp and generate context (same as the MCP guide):

cd /path/to/your/project
stamp init
stamp context

Details: CLI getting started.

Configuration

npx and -y

Include -y in "args" before the package name so npx does not wait for interactive confirmation (for example when it needs to install or fetch the package). MCP clients usually start the server without a terminal, so a prompt can hang or fail. If logicstamp-mcp is already installed globally, npx often works without -y, but keeping -y in config files is recommended. Some clients may require "type": "stdio"—see the MCP docs and integration guides if the minimal config does not connect.

Claude Desktop

Edit claude_desktop_config.json: macOS ~/Library/Application Support/Claude/claude_desktop_config.json, Windows %APPDATA%\Claude\claude_desktop_config.json. Merge the block below into mcpServers, then restart Claude Desktop.

{
  "mcpServers": {
    "logicstamp": {
      "command": "npx",
      "args": [
        "-y",
        "logicstamp-mcp"
      ],
      "env": {
        "PROJECT_PATH": "/absolute/path/to/your/project"
      }
    }
  }
}

Replace PROJECT_PATH with your project root. Most tool calls pass projectPath explicitly, so this env var is optional fallback (e.g. compare tools).

Cursor

Add to your Cursor MCP config (~/.cursor/mcp.json on macOS/Linux or %USERPROFILE%\.cursor\mcp.json on Windows). Use the same JSON as Claude Desktop below.

{
  "mcpServers": {
    "logicstamp": {
      "command": "npx",
      "args": [
        "-y",
        "logicstamp-mcp"
      ],
      "env": {
        "PROJECT_PATH": "/absolute/path/to/your/project"
      }
    }
  }
}

Fully quit and restart Cursor (not just close the window) after saving.

Claude Code

Optional: register the server with Claude Code MCP CLI or ~/.claude.json using the same npx / -y pattern as in the callout above.

claude mcp add --scope user --transport stdio logicstamp -- npx -y logicstamp-mcp

Per-project: claude mcp add --scope project writes .mcp.json in the repo.

Environment (from the MCP guide)

PROJECT_PATH is optional fallback when a tool omits projectPath (especially logicstamp_compare_snapshot and logicstamp_compare_modes). The server expects stamp on PATH.

Verify installation

which logicstamp-mcp

In Claude Code you should see LogicStamp listed as connected (exact wording varies by client version).

Using the tools

Call logicstamp_watch_status first. If watch mode is already active, skip refresh and go straight to list/read bundles; otherwise refresh snapshot before reading context.

Seven tools (names match the MCP getting started doc):

1.logicstamp_watch_status — Is stamp context --watch running?
2.logicstamp_list_bundles — Catalog available bundles
3.logicstamp_read_bundle — Read a bundle / contract
4.logicstamp_refresh_snapshot — Regenerate context on demand
5.logicstamp_compare_snapshot — Diff architectural snapshots
6.logicstamp_compare_modes — Compare include-code / token modes
7.logicstamp_read_logicstamp_docs — Fetch LogicStamp documentation snippets

Full behavior and schemas: MCP reference.

Learn More

MCP Reference →

Complete tool documentation

MCP Overview →

How MCP works

Next Steps

Explore the complete MCP reference or learn about usage examples and workflows.

MCP Reference Usage Examples