feat(mcp): add askable-mcp stdio CLI for command-based MCP clients - #349

Summary

Adds askable-mcp, a turnkey stdio MCP server binary, so MCP clients that launch a command (Claude Desktop, Cursor) — rather than connecting to an HTTP URL — can read your app's UI context.

Why

The existing path requires running an HTTP server (Express). Many MCP clients instead spawn a stdio command. This closes that gap with no new runtime dependencies — it reuses the already-present @modelcontextprotocol/sdk (StdioServerTransport) and node:util.parseArgs (no arg-parser, no server framework).

What's included

• askable-mcp bin — serves the askable context tools/resources over stdio, backed by:
  • --url <endpoint> — fetches the current Context packet from an HTTP(S) endpoint, or
  • --file <path> — serves a static packet file
  • plus --header "K: V" (repeatable), --name, --require-redacted, --help
• createAskableMcpRemoteProvider({ url, headers }) — exported for programmatic use (also what the CLI uses).
• MCP guide section documenting the CLI + a flag table.
• @types/node added dev-only, scoped to this package's tsconfig via types: ["node"] so it does not leak Node globals into the other packages' builds (verified: full 12-package build stays clean).

{
  "mcpServers": {
    "my-app": {
      "command": "npx",
      "args": ["-y", "@askable-ui/mcp", "--url", "http://localhost:3001/context"]
    }
  }
}

Your app just needs a GET endpoint returning the latest packet (e.g. via ctx.toContextPacket()).

Test plan

• mcp 45/45 tests (7 new: remote provider success/non-ok + CLI header parsing / arg handling)
• full workspace tsc build clean (no @types/node leakage)
• docs build clean (no dead links)
• smoke-tested: shebang, --help, exit-1 on missing source, stdio startup with --file
• CI typecheck-and-build + static/quality green

🤖 Generated with Claude Code

Generated by Claude Code