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
Voyei

6 hours ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

16 hours ago