MCP Compatibility

@runablejs/mcp loads runable/inspector from the inspected project's own node_modules. Compatibility therefore depends on the runable version installed in that project, not on a globally installed CLI.

Compatibility levels

For the 0.1.x MCP line:

Runable is currently in prerelease. Treat the published compatibility table as authoritative instead of assuming that every numerically newer prerelease works.

Runtime capability checks

At startup, the server verifies the Inspector factory and the methods required by its base tool set. If a required capability is absent, startup fails and names the missing method.

resolveRoute() is checked when resolve_route is called. This targeted check lets an older base-compatible project keep the other seven tools.

Keep project dependencies aligned

Install both packages in the project rather than relying on global resolution:

pnpm add runable
pnpm add -D @runablejs/mcp

After upgrading either package:

1. restart the MCP client connection;
2. call get_project and verify runableVersion;
3. list the eight tools;
4. call resolve_route if full compatibility is expected.

Both packages require Node.js ^22.18.0 or >=24.12.0.

See Troubleshooting for startup and capability errors.