tiger-js-mcp

An MCP server for Tiger projects. Exposes tiger_check and tiger_map as tools any MCP-compatible AI agent can call directly, mid conversation, no shell required. Same engine as tiger-js-cli, a different door into the same, already-tested logic.

Status: verified. Connected to Claude Code over stdio and confirmed working, both tools return real results against a real project.

If you edit tiger-js-cli, re-sync and restart the MCP server (reload your editor window, or whatever restarts the client's stdio process) before trusting new output, Node caches lib/ in memory for the life of the process, a re-sync on disk alone will not reach a server already running.

Install

npm install -g tiger-js-mcp

Connect it to Claude Desktop or Claude Code

Add it to your MCP client's config (for Claude Desktop, claude_desktop_config.json; Claude Code has an equivalent .mcp.json at your workspace root, picked up on a fresh session):

{
  "mcpServers": {
    "tiger": {
      "type": "stdio",
      "command": "tiger-mcp"
    }
  }
}

(A global install puts tiger-mcp on your PATH; if you'd rather run it straight from a clone without installing globally, point command at node and args at the absolute path to this folder's server.js instead.)

Once connected, an agent can call tiger_check or tiger_map on any Tiger project directly, the same way it would call any other tool, no terminal needed.

Tools

tiger_check(dir?) diagnostics for a Tiger project: every "no cell named X", every derived-cell reassignment, as structured JSON. dir defaults to the server's working directory.

tiger_map(dir?) the whole shape of the project: every route, every component, every cell with its shape, every action, every machine.

Keeping it in sync

server.js reuses tiger-js-cli's logic via a synced copy in lib/ (it cannot depend on a sibling folder once installed elsewhere). After editing tiger-js-cli/lib/*.js:

node sync-lib.js