logicstamp

LogicStamp MCP server provides AI-assisted access to your codebase through the LogicStamp Context analysis engine. It acts as a thin wrapper around the stamp CLI, offering snapshot-based analysis, component contracts extraction (props, state, hooks), style metadata, dependency graphs, drift detection, and token optimization. The server exposes seven tools that enable you to generate and compare component bundles, read documentation, and monitor watch-mode activity to ensure context stays fresh for AI workflows. You can use these tools in sequence to analyze a project, discover relevant bundles, read detailed contracts and graphs, and verify changes after edits.

To use the MCP server, configure your MCP client to point at the logicstamp-mcp server via npx in your mcp.json (as shown in the Quick Start). Once configured, you can prompt your AI assistant to perform tasks such as refreshing snapshots, listing available bundles, reading a specific bundle’s contract, comparing snapshots, and evaluating token costs across modes. The tools are designed to be used in order: refresh_snapshot, list_bundles, read_bundle, and then any comparison or doc tools as needed. If watch mode is active in your project, the server will skip regeneration to keep context fresh, ensuring safe and efficient interactions with AI agents.

Prerequisites

• Node.js >= 20
• npm (comes with Node.js)
• LogicStamp Context CLI installed and available in PATH (stamp command)

Step-by-step installation

1. Install the LogicStamp CLI globally (required for the MCP tools):

npm install -g logicstamp-context

2. Install the MCP server globally (as documented by LogicStamp):

npm install -g logicstamp-mcp

3. Verify installations:

stamp --version
logicstamp-mcp --version

4. Configure your MCP client with the logicstamp MCP server configuration (see mcp_config):

• Create or edit your MCP config (e.g., Cursor, Claude CLI, or Claude Desktop) to include:

{
  "mcpServers": {
    "logicstamp": {
      "command": "npx",
      "args": ["logicstamp-mcp"]
    }
  }
}

5. Start using LogicStamp:

# Start your CLI or integration that consumes MCP tools, e.g.:
claude  # or open Cursor

Tips and considerations:

• Ensure the stamp CLI (LogicStamp Context) is installed and accessible in PATH to enable MCP functionality.
• The MCP config uses npx to invoke logicstamp-mcp on demand; replace with your preferred launcher if needed but keep the same command/args structure.
• If you encounter issues with client integrations, try adding "type": "stdio" to your MCP config as suggested in the integration docs.
• For large codebases, use logicstamp_refresh_snapshot with appropriate depth and includeStyle options to manage token usage and performance.
• Watch mode optimizations: when using stamp context --watch, set skipIfWatchActive to true in your tool parameters to skip unnecessary regenerations.
• Regularly update LogicStamp CLI and MCP to benefit from improvements and new tools.