mcp-node-omnibus

The Node Omnibus MCP Server offers a centralized toolset for Node.js development automation via the Model Context Protocol (MCP). It includes capabilities for creating projects across React, Next.js, Express, Fastify, and plain Node environments; automatic TypeScript setup; smart package management; component generation with typings and documentation; and built-in AI-assisted guidance for project setup, code improvements, and debugging. Once the server is running, connect an MCP client to the server using the standard MCP transport (stdio as specified). From there you can invoke the available tools to scaffold projects, install dependencies, generate components, create TypeScript definitions, and update configuration files. The server is designed to be integrated into editor workflows or CI pipelines, enabling repeatable project scaffolding and documentation tasks through a consistent API.

With the available tools, you can:

• Create projects of various types (react, node, next, express, fastify) with optional TypeScript support.
• Install packages and manage dev dependencies across project workspaces.
• Generate components (functional or class-based) with optional prop typings and documentation artifacts.
• Create TypeScript definitions and update tsconfig or package.json configurations.
• Add npm scripts, and generate project documentation and API docs. The server also supports AI-assisted prompts for project guidance, code analysis, and debugging, making it useful for rapid prototyping and onboarding.

Prerequisites:

• Node.js v14+ (or as specified in the repo requirements)
• npm v6+ (or use your preferred package manager)

Install steps:

1. Clone the repository: git clone https://github.com/bsmi021/mcp-node-omnibus-server.git cd mcp-node-omnibus-server

2. Install dependencies: npm install

3. Build (if applicable): npm run build

4. Start the server: npm start

5. Optional: Integrate with Smithery for automatic installation: npx -y @smithery/cli install @bsmi021/mcp-node-omnibus-server --client claude

Notes:

• The server exposes its MCP endpoint over stdio by default when run in client contexts. Ensure your MCP client is configured to connect via the expected transport (stdio).
• If you customize paths, adjust the mcp_config accordingly to point to the built dist index file.

Environment and configuration tips:

• Ensure Node.js version compatibility as listed in the project requirements.
• When using TypeScript features, keep tsconfig.json aligned with generated or updated configurations via update_tsconfig.
• The server can generate documentation (readme/api/component) and TypeScript definitions; ensure your project structure matches the expected paths for generated assets.
• For editor integrations, map the command and dist path in your editor’s MCP client configuration (e.g., VSCode settings) to the server’s startup script.
• If you encounter issues with package installation, verify network access and npm proxy settings; check for compatible package versions in package.json.
• Use the AI-assisted prompts to aid in project setup and debugging by leveraging the server’s guidance features.