fix: CLI entry point starts MCP server by default, init becomes subcommand - #128
Open
TerminalGravity wants to merge 4 commits into
Open
fix: CLI entry point starts MCP server by default, init becomes subcommand#128TerminalGravity wants to merge 4 commits into
TerminalGravity wants to merge 4 commits into
Conversation
Covers LanceDB native binary failures, CLAUDE_PROJECT_DIR config, vector search not returning results, MCP handshake debugging, and performance tips. Links from README nav bar.
- examples/.preflight/config.yml: profile, related projects, thresholds, embeddings - examples/.preflight/triage.yml: strictness, always_check/skip/cross-service keywords - examples/.preflight/README.md: setup instructions and env var fallback reference - README.md: link to examples from Configuration Reference section
…ommand Previously, `preflight-dev` (the bin entry) ran the init wizard, making `claude mcp add preflight -- preflight-dev` broken — it would launch the interactive setup instead of the MCP server. Now: - `preflight-dev` → starts MCP server (correct for claude mcp add) - `preflight-dev init` → runs interactive setup wizard - `preflight-dev help` → shows usage info Also fixes init generating a broken .mcp.json (was overwriting the config with a wrong path to node_modules/preflight/src/index.ts).
TerminalGravity
commented
Mar 6, 2026
TerminalGravity
left a comment
TerminalGravity
left a comment
Collaborator
Author
There was a problem hiding this comment.
Critical fix — the CLI entry point breaking claude mcp add was a real onboarding blocker. Good call making MCP server the default and moving init to a subcommand. The corrected .mcp.json generation using npx -y preflight-dev@latest is the right approach. Ready to merge.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
preflight-dev(the npm bin entry) ran the interactive init wizard, which meantclaude mcp add preflight -- preflight-devwas broken — it launched the setup wizard instead of the MCP server.The init script also generated a broken
.mcp.json, overwriting the correct config with a wrong path (node_modules/preflight/src/index.ts).Fix
preflight-dev(no args) → starts MCP server ✅preflight-dev init→ interactive setup wizardpreflight-dev help→ usage info.mcp.jsonusingnpx -y preflight-dev@latestpreflight-dev initdocs to README Option C