Node Omnibus MCP Server

Created By
MCP-Mirrora year ago
Mirror of
Overview

what is Node Omnibus MCP Server?

Node Omnibus MCP Server is a comprehensive Model Context Protocol (MCP) server designed to provide advanced Node.js development tooling and automation capabilities.

how to use Node Omnibus MCP Server?

To use the Node Omnibus MCP Server, install it via Smithery, clone the repository, install dependencies, and start the server using npm commands. It can be integrated with any MCP-compatible client.

key features of Node Omnibus MCP Server?

  • Project creation with built-in support for various frameworks (React, Next.js, Express, Fastify, Plain Node.js)
  • Automatic TypeScript configuration and package management
  • Component generation and documentation
  • AI-powered assistance for project setup and code analysis

use cases of Node Omnibus MCP Server?

  1. Scaffolding new Node.js projects with ease.
  2. Generating React components and TypeScript interfaces automatically.
  3. Managing project configurations and documentation efficiently.

FAQ from Node Omnibus MCP Server?

  • What frameworks does it support?

It supports React, Next.js, Express, Fastify, and Plain Node.js.

  • Is there AI assistance available?

Yes, it provides AI-powered assistance for project creation and code improvements.

  • How do I start the server?

You can start the server using the command npm start after installation.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCP-Mirror
Star
0
Language
JavaScript
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago