Skip to content

Add Node/TypeScript pre-fill button and improve repo setup UX#12

Merged
BillJr99 merged 1 commit into
mainfrom
claude/admiring-newton-FuK5K-recommend-build-commands
May 25, 2026
Merged

Add Node/TypeScript pre-fill button and improve repo setup UX#12
BillJr99 merged 1 commit into
mainfrom
claude/admiring-newton-FuK5K-recommend-build-commands

Conversation

@BillJr99
Copy link
Copy Markdown
Owner

Summary

Improves the repository provider setup wizard with a one-click pre-fill feature for Node/TypeScript MCP servers and enhanced documentation to guide users through the common setup pattern.

Key Changes

  • Added "⚡ Pre-fill Node/TS" button in the Build commands section that automatically populates:

    • Build commands: npm install and npm run build
    • Spawn command: node build/index.js
    • This covers the most common pattern for TypeScript MCP repos (e.g., linkedin-mcpserver, fastmcp-style projects)
  • Updated UI layout for the Build commands label to accommodate the new button using flexbox (d-flex justify-content-between align-items-center)

  • Improved placeholder and helper text:

    • Changed spawn command placeholder from node dist/main.js to node build/index.js
    • Enhanced helper text with concrete examples: compiled TS, un-compiled TS, and Python patterns
    • Clarified that build commands must terminate and cannot contain long-running server starts
  • Updated README documentation:

    • Added recommended Node/TypeScript setup table showing the standard pattern
    • Documented the pre-fill button functionality
    • Added warning about not putting long-running commands in build steps
    • Updated YAML example to reflect the node build/index.js pattern
    • Updated example env keys to match linkedin-mcpserver's actual requirements

Implementation Details

The wzPrefillRepoNodeTs() function:

  • Clears existing build commands
  • Adds two new command entries via _wzListAdd()
  • Explicitly sets input values to ensure they're populated correctly
  • Sets the spawn command input to node build/index.js

This provides a frictionless onboarding experience for the most common MCP server setup pattern while maintaining flexibility for other configurations.

https://claude.ai/code/session_01R2Vi6NE4wGxwv6rZ2HEXji

Most stdio Node/TS MCP repos (linkedin-mcpserver, typical fastmcp
projects, etc.) follow the same pattern: tsc compiles src/*.ts to
build/*.js and the executable entry is build/index.js.  Surface that
as the recommended setup so users don't paste `npm run start:dev` (a
long-running server command) into Build commands and break startup.

- Wizard repository step: spawn-command placeholder is now
  `node build/index.js`; the Build commands help text recommends
  `npm install` + `npm run build`; one-click "⚡ Pre-fill Node/TS"
  button populates all three at once.
- README "Part 3.5" walkthrough: new "Recommended for Node/TypeScript
  repos" callout with the field/value table, and an explicit warning
  not to put long-running server commands in Build commands.
- README YAML example: switched to `node build/index.js` and the
  real LINKEDIN_CLIENT_ID / LINKEDIN_CLIENT_SECRET keys from the repo.
@BillJr99 BillJr99 merged commit af39709 into main May 25, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants