Skip to main content
Glama
README.md
<div align="center">

<img src="https://github.com/ncsound919/VibeServe/blob/main/assets/update-banner.png" alt="VibeServe" width="100%" />

# VibeServe v1.1
### *The Ultimate Agentic IDE, Orchestrator, and MCP Backend*

[![CI](https://github.com/ncsound919/VibeServe/actions/workflows/ci.yml/badge.svg)](https://github.com/ncsound919/VibeServe/actions/workflows/ci.yml)
[![PyPI](https://img.shields.io/pypi/v/vibeserve.svg?color=00FF9F)](https://pypi.org/project/vibeserve/)
[![Node.js](https://img.shields.io/badge/Node.js-20.x-green.svg)](https://nodejs.org)
[![React](https://img.shields.io/badge/React-18-blue.svg)](https://reactjs.org)
[![Python 3.10+](https://img.shields.io/badge/python-3.10%2B-blue.svg)](https://python.org)
[![MCP](https://img.shields.io/badge/MCP-compatible-00FF9F.svg)](https://modelcontextprotocol.io)
[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](LICENSE)

## What is VibeServe?

**VibeServe** is the first full-stack, fully-integrated AI development platform. It unifies a **React-based AI IDE**, a **Node.js Orchestrator**, and a **Python MCP Server** into a single cohesive system. 

It transforms natural language intent into fully-architected, accessible, production-ready UI code โ€” powered by a **7-step agentic pipeline**, a fully aware context engine, and dynamic human-in-the-loop controls.

```
๐Ÿ—๏ธ architect โ†’ ๐Ÿ’ป code โ†’ ๐Ÿ” review โ†’ โœ… verify โ†’ ๐Ÿ”„ iterate โ†’ ๐Ÿงช test โ†’ ๐Ÿš€ deploy
```


## Unified Repository Structure

This repository is a monorepo housing the three core pillars of the VibeServe ecosystem:

### 1. `ide/` (The Front-End Client)
The **VibeServe IDE** (formerly Nexus-Alpha) is a Vite/React application acting as the command center. It features an interactive command palette, real-time agent trajectories, code editors, artifact previews, and full MCP tool visibility. It's fully WCAG AAA accessible and designed for extreme performance.

### 2. `orchestrator/` (The Control Plane)
The **VibeServe Orchestrator** (formerly CodeNexus) is a high-performance Node.js backend. It coordinates agents, handles WebSockets for real-time streaming, runs deep security audits (AST analysis), and manages the lifecycle of the AI agents and their sandbox environments.

### 3. `mcp/` (The Python Backend)
The original **VibeServe MCP Server**. This is a production-grade FastMCP server containing 28 specialized tools, SQLite-backed memory, multi-LLM routing with auto-fallback (OpenAI, DeepSeek, OpenRouter, Local Ollama), and direct integration endpoints. 




## Quickstart

### One-Command Startup

```bash
# Clone and start everything
git clone https://github.com/ncsound919/VibeServe
cd VibeServe/ide
npm start
```

This starts:
- The Vite dev server (port 3000)
- The Hono API server (port 3002)
- WebSocket connections for real-time agent streaming

### Prerequisites
* **Node.js** 20+
* **Python** 3.10+
* **pnpm** (for the orchestrator)

### Setup the Entire Ecosystem

1. **Clone the monorepo:**
   ```bash
   git clone https://github.com/ncsound919/VibeServe
   cd VibeServe
   ```

2. **Start the MCP Server:**
   ```bash
   cd mcp
   pip install -e ".[dev]"
   cp .env.example .env
   # Start in dev mode or hook into Claude Desktop
   pytest tests/ -v
   ```

3. **Start the Orchestrator:**
   ```bash
   cd ../orchestrator
   pnpm install
   pnpm run build
   pnpm run dev
   ```

4. **Start the IDE:**
   ```bash
   cd ../ide
   npm install
   npm run dev
   ```

The system will now be fully interconnected.

---

## Architecture

```
VibeServe IDE (React / Vite)
       โ†“ WebSocket / REST
VibeServe Orchestrator (Node.js / Express)
       โ†“ stdio MCP Protocol
VibeServe MCP Server (Python / FastMCP)
  โ”œโ”€โ”€ 28 Tools ยท 5 Resources ยท 6 Prompts
  โ”œโ”€โ”€ V5 Agentic Pipeline
  โ”œโ”€โ”€ LLMRouter (Auto-fallback chain)
  โ”œโ”€โ”€ MemoryStore (aiosqlite)
  โ””โ”€โ”€ SchemaValidator (WCAG AAA enforcement)


---

## License

MIT License. See [LICENSE](LICENSE) for details.

---

## Windows Bridge (TypeScript + Hono)

The `vibeserve/ts_bridge/` directory contains a **TypeScript-native Hono HTTP bridge** that
replaces the Python `http_bridge.py` on Windows, avoiding ProactorEventLoop issues with
asyncio servers. It spawns `python -m vibeserve` as a child process and communicates with
the Python MCP server via **stdin/stdout JSON-RPC** (the standard MCP stdio transport).

### Quick Start

```powershell
cd vibeserve\ts_bridge
npm install
.\start-bridge.ps1
```

Or with custom settings:

```powershell
.\start-bridge.ps1 -Port 9000 -Python "python3.12" -Host "0.0.0.0"
```

### Architecture

```
Client (HTTP / WebSocket)
       โ†“
ts_bridge (Hono + TypeScript)
       โ†“ stdin/stdout JSON-RPC
python -m vibeserve (FastMCP stdio server)
```

### Endpoints

| Method | Path          | Description                     |
|--------|---------------|---------------------------------|
| GET    | `/health`     | Health check                    |
| POST   | `/tools/list` | List available MCP tools        |
| POST   | `/tools/call` | Call an MCP tool by name        |
| WS     | `/ws`         | WebSocket for streaming tool calls |

### WebSocket Protocol

Connect to `ws://host:port/ws` and send JSON messages:

```json
{ "type": "tool_call", "name": "vs_memory_get", "arguments": { "workspace_id": "demo" } }
{ "type": "ping" }
```

### Testing

```bash
cd vibeserve\ts_bridge
npm test
```

TDQS

C2.7/5.0

Scored across 20 tools

Disambiguation4/5

Most tools have distinct purposes, but some overlap exists (e.g., vibe_audit, vibe_review, and vibe_verify all involve code quality checks). Descriptions help clarify, but ambiguity remains for a few.

Naming Consistency3/5

The majority follow a 'vibe_<verb>' pattern, but several tools like generate_ui_spec, list_design_systems, memory_stats, and validate_ui_spec break this pattern, mixing conventions.

Tool Count4/5

20 tools is on the higher end but justified for a comprehensive development workflow server covering design, architecture, coding, testing, deployment, and auditing. Some tools could potentially be merged.

Completeness4/5

The toolset covers major stages of development from specification to deployment and auditing. Missing project setup or config management tools, but core workflows are well-represented.

Maintenance

ActivitySlowing
ResponsivenessNo issues