Skip to main content
Glama
Node Omnibus MCP Server

Node Omnibus MCP Server

by bsmi021

Node Omnibus MCP Server

A comprehensive Model Context Protocol (MCP) server that provides advanced Node.js development tooling and automation capabilities.

Features

Project Management

  • Project Creation: Scaffold new projects with built-in support for:

    • React

    • Next.js

    • Express

    • Fastify

    • Plain Node.js

  • TypeScript Integration: Automatic TypeScript configuration and setup

  • Package Management: Smart dependency installation and version management

Component Generation

  • Create React components (functional or class-based)

  • TypeScript interfaces generation

  • Automatic prop types definition

  • Component documentation generation

Configuration Management

  • TypeScript configuration management

  • NPM script management

  • Package.json updates

  • Environment setup

Documentation

  • Project README generation

  • API documentation

  • Component documentation

  • TypeScript type definitions documentation

AI-Powered Assistance

  • Project creation guidance

  • Code analysis and improvements

  • Component generation assistance

  • Git commit message suggestions

  • Error debugging assistance

Related MCP server: MOIDVK

Installation

Installing via Smithery

To install Node Omnibus Server for Claude Desktop automatically via Smithery:

npx -y @smithery/cli install @bsmi021/mcp-node-omnibus-server --client claude
  1. Clone the repository

  2. Install dependencies:

npm install

Usage

The server operates using the Model Context Protocol over stdio. It can be integrated with any MCP-compatible client.

Starting the Server

npm start

Available Tools

  1. create_project

    {
      name: string;
      type: 'react' | 'node' | 'next' | 'express' | 'fastify';
      path: string;
      typescript?: boolean;
    }
  2. install_packages

    {
      packages: string[];
      path: string;
      dev?: boolean;
    }
  3. generate_component

    {
      name: string;
      path: string;
      type: 'functional' | 'class';
      props?: Record<string, string>;
    }
  4. create_type_definition

    {
      name: string;
      path: string;
      properties: Record<string, string>;
    }
  5. add_script

    {
      path: string;
      name: string;
      command: string;
    }
  6. update_tsconfig

    {
      path: string;
      options: Record<string, unknown>;
    }
  7. create_documentation

    {
      path: string;
      type: 'readme' | 'api' | 'component';
      name?: string;
    }

Available Prompts

  1. create-project

    {
      projectType: string;  // react, node, next, express, fastify
      features?: string;    // comma-separated list of features
    }
  2. analyze-code

    {
      code: string;
      language: string;
    }
  3. generate-component

    {
      name: string;
      type: string;  // functional or class
    }
  4. git-commit

    {
      changes: string;  // Git diff or description of changes
    }
  5. debug-error

    {
      error: string;  // Error message or stack trace
    }

Project Structure

node-omnibus-server/
├── src/
│   └── index.ts        # Main server implementation
├── dist/               # Compiled JavaScript
├── node_modules/       # Dependencies
├── package.json        # Project configuration
└── tsconfig.json      # TypeScript configuration

Development

Building

npm run build

Running Tests

npm test

Development Mode

npm run dev

Integration

VSCode Configuration

Add to your VSCode settings:

{
  "mcpServers": {
    "node-omnibus": {
      "command": "node",
      "args": ["path/to/node-omnibus-server/dist/index.js"]
    }
  }
}

Client Usage Example

const client = new McpClient();
await client.connect(transport);

// Create a new React project
const result = await client.callTool('create_project', {
  name: 'my-app',
  type: 'react',
  path: './projects',
  typescript: true
});

// Use AI assistance for project setup
const guidance = await client.getPrompt('create-project', {
  projectType: 'react',
  features: 'typescript,testing,docker'
});

Contributing

  1. Fork the repository

  2. Create a feature branch

  3. Make your changes

  4. Submit a pull request

License

MIT License - See LICENSE file for details

Requirements

  • Node.js >= 14.x

  • npm >= 6.x

  • TypeScript >= 4.x

Dependencies

  • @modelcontextprotocol/sdk

  • axios

  • typescript (dev)

Available Tools

7 tools
add_scriptC

Add a new npm script to package.json

Inputs: path (required), name (required), command (required).

create_documentationC

Generate project documentation

Inputs: path (required), type (required), name.

create_projectC

Create a new Node.js project with enhanced configuration

Inputs: name (required), type (required), path (required), typescript.

create_type_definitionC

Create TypeScript type definitions or interfaces

Inputs: name (required), path (required), properties (required).

generate_componentC

Generate a new React component with TypeScript support

Inputs: name (required), path (required), type (required), props.

install_packagesC

Install npm packages with version management

Inputs: packages (required), path (required), dev.

update_tsconfigC

Update TypeScript configuration

Inputs: path (required), options (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.4/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose targeting different aspects of Node.js/TypeScript development workflows. There is no overlap between adding npm scripts, creating documentation, setting up projects, defining types, generating components, installing packages, and updating tsconfig.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern with clear, descriptive names. The naming convention is uniform throughout (e.g., add_script, create_documentation, install_packages), making the tool set predictable and easy to understand.

    Tool Count5/5

    With 7 tools, the server is well-scoped for Node.js/TypeScript project management. Each tool serves a specific, valuable function in the development lifecycle, and the count is neither too sparse nor overwhelming for the domain.

    Completeness4/5

    The tool set covers key areas like project setup, dependency management, configuration, and code generation, but there are minor gaps such as missing tools for testing, building, or deployment workflows that might be expected in a comprehensive Node.js server.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      B
      maintenance
      A Model Context Protocol server that enables AI-powered analysis of NPM packages through multiple tools for security vulnerability scanning, dependency analysis, package comparison, and quality assessment.
      19
      452 npm
      18
      TypeScript
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      A comprehensive Model Context Protocol (MCP) server that provides 37+ intelligent development tools across JavaScript/TypeScript, Rust, and Python with security-first design and high-performance features.
      7 npm
      1
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      An intelligent tool that automates the setup of new Model Context Protocol (MCP) server projects through a conversational interface. It generates project structures, technical specifications, and context-rich documentation to streamline AI-assisted development in TypeScript or Python.
      10
      3
      MIT
    • A
      license
      B
      quality
      C
      maintenance
      Production-grade, autonomous Model Context Protocol (MCP) server that elevates AI models from stateless code generators into persistent, self-verifying software engineers.
      21
      1
      MIT