mcp-inflight 0.3.0 → 0.3.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -83,9 +83,9 @@ The server automatically patches configuration files for CodeSandbox compatibili
83
83
 
84
84
  Projects over 3MB are automatically chunked into smaller uploads to handle Vercel's serverless function body size limits.
85
85
 
86
- ## Slash Commands (Optional)
86
+ ## Slash Commands (Recommended)
87
87
 
88
- For a better experience, install the included slash commands. These provide `/share` and `/inflight` commands in Claude Code.
88
+ For the best experience, install the included slash commands. The `/share` command enables **automated AI feedback guide generation** - Claude analyzes your git changes and generates product-focused review questions that appear on your InFlight version.
89
89
 
90
90
  ### Installation
91
91
 
@@ -109,7 +109,7 @@ cp packages/mcp-inflight/commands/*.md ~/.claude/commands/
109
109
 
110
110
  | Command | Description |
111
111
  |---------|-------------|
112
- | `/share` | Share a project to InFlight (shortcut for the share tool) |
112
+ | `/share` | Share a project to InFlight with AI-generated feedback guide |
113
113
  | `/inflight` | Menu for managing prototypes: list, sync, delete, login, logout |
114
114
 
115
115
  ## Troubleshooting
@@ -0,0 +1,70 @@
1
+ # InFlight
2
+
3
+ Manage InFlight prototypes and authentication.
4
+
5
+ ## Arguments
6
+
7
+ $ARGUMENTS - Optional action: `login`, `logout`, `list`, `sync`, `delete`. If not provided, shows menu.
8
+
9
+ ## Instructions
10
+
11
+ ### If no argument provided, show menu
12
+
13
+ Ask the user what they'd like to do using the AskUserQuestion tool with these options:
14
+ - **Check login status** - See who's logged in
15
+ - **List prototypes** - Show all shared prototypes
16
+ - **Sync prototype** - Update files in an existing prototype
17
+ - **Delete prototype** - Remove a prototype
18
+ - **Logout** - Log out of InFlight
19
+
20
+ Then execute the selected action below.
21
+
22
+ ### Action: login (or "Check login status")
23
+
24
+ Call the `login` MCP tool. It will either:
25
+ - Show current user info if already logged in
26
+ - Open browser for authentication if not logged in
27
+
28
+ Display the result to the user.
29
+
30
+ ### Action: logout
31
+
32
+ Call the `logout` MCP tool to clear stored credentials.
33
+ Confirm to the user they've been logged out.
34
+
35
+ ### Action: list (or "List prototypes")
36
+
37
+ Call the `prototype_list` MCP tool.
38
+
39
+ Display results in a table:
40
+ - Prototype ID
41
+ - Project Name
42
+ - Type
43
+ - Status
44
+ - InFlight URL
45
+ - Created
46
+
47
+ If no prototypes found, inform the user.
48
+
49
+ ### Action: sync (or "Sync prototype")
50
+
51
+ 1. If a prototype ID is provided in arguments, use that
52
+ 2. Otherwise, call `prototype_list` and ask user which prototype to sync
53
+ 3. Ask for the project path (or use current directory)
54
+ 4. Check for .env files - only ask about including them if they exist
55
+ 5. Call `prototype_sync` with:
56
+ - `prototypeId`: The selected ID
57
+ - `path`: The project path
58
+ - `includeEnvFiles`: Based on user response (default: false)
59
+
60
+ ### Action: delete (or "Delete prototype")
61
+
62
+ 1. If a prototype ID is provided in arguments, use that
63
+ 2. Otherwise, call `prototype_list` and ask user which prototype to delete
64
+ 3. Confirm: "Delete prototype [ID]? This will stop it and make it unavailable."
65
+ 4. Call `prototype_delete` with the prototype ID
66
+ 5. Confirm deletion to user
67
+
68
+ ## Related Commands
69
+
70
+ - `/share` - Share a project to InFlight
@@ -0,0 +1,75 @@
1
+ # Share Project
2
+
3
+ Share a local project to InFlight for feedback and collaboration.
4
+
5
+ ## Arguments
6
+
7
+ $ARGUMENTS - Optional path to the project directory. If not provided, uses current working directory.
8
+
9
+ ## Instructions
10
+
11
+ ### 1. Determine project path
12
+
13
+ Use the provided path argument or current working directory.
14
+
15
+ ### 2. Check for .env files (STOP only if found)
16
+
17
+ Look for `.env`, `.env.local`, `.env.development`, `.env.production` in the project directory.
18
+
19
+ **Only if .env files exist, ASK:** "Found .env files. Include them in deployment? (May contain sensitive API keys)"
20
+ - Yes: set `includeEnvFiles: true`
21
+ - No: set `includeEnvFiles: false` (default)
22
+
23
+ If no .env files found, skip this step entirely.
24
+
25
+ ### 3. Analyze git changes (if on feature branch)
26
+
27
+ Check if there are git changes to generate review questions:
28
+
29
+ 1. **Check for commits on branch:** Run `git log main..HEAD --oneline 2>/dev/null || git log master..HEAD --oneline 2>/dev/null`
30
+ 2. **If commits exist**, analyze the changes:
31
+ - Run `git diff main...HEAD 2>/dev/null || git diff master...HEAD 2>/dev/null` to see what changed
32
+ - **Generate a product-focused summary:** Write 2-3 sentences about user-visible changes (not internal code details)
33
+ - **List key changes:** Identify main user-facing changes (e.g., "Added dark mode toggle", "Redesigned checkout flow")
34
+ - **List affected areas:** Identify UI/feature areas (e.g., "Settings page", "Navigation", "Forms")
35
+
36
+ **Skip this step if:**
37
+ - On main/master branch
38
+ - No commits found on the branch
39
+ - Git commands fail (not a git repo)
40
+
41
+ ### 4. Call the `share` MCP tool
42
+
43
+ Call the `share` tool with:
44
+ - `path`: the project path
45
+ - `includeEnvFiles`: based on user response (default: false)
46
+ - `diffSummary` (only if git changes were analyzed in step 3):
47
+ - `summary`: your product-focused summary
48
+ - `keyChanges`: array of key user-visible changes
49
+ - `affectedAreas`: array of affected UI areas
50
+
51
+ The MCP tool handles everything:
52
+ - Project analysis and type detection
53
+ - Package manager detection
54
+ - VM tier selection
55
+ - Creating prototype and InFlight version
56
+ - Generating review questions from your summary (automatic)
57
+ - Opening InFlight in browser
58
+
59
+ ### 5. Display the result
60
+
61
+ Show the InFlight URL to the user:
62
+
63
+ ```
64
+ Shared!
65
+
66
+ InFlight: https://www.inflight.co/v/[version-id]
67
+ ```
68
+
69
+ ## Error Handling
70
+
71
+ If the tool returns an error, display it to the user.
72
+
73
+ ## Related Commands
74
+
75
+ - `/inflight` - Manage prototypes, login/logout
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "mcp-inflight",
3
- "version": "0.3.0",
3
+ "version": "0.3.1",
4
4
  "description": "MCP server for sharing prototypes via InFlight",
5
5
  "author": "InFlight <hello@inflight.co>",
6
6
  "homepage": "https://github.com/inflight/mcp-inflight",
@@ -22,7 +22,8 @@
22
22
  "typescript": "^5.0.0"
23
23
  },
24
24
  "files": [
25
- "dist"
25
+ "dist",
26
+ "commands"
26
27
  ],
27
28
  "keywords": [
28
29
  "mcp",