Ripple MCP

Ripple is a planned voice-aware collaborative task assistant for hackathon use.

It is intended to process a team meeting recording, identify speaker turns, map labels to consenting team members, extract tasks/deadlines/dependencies, and manage that task graph via MCP.

Current status

The MCP server is live on branch feature/task-tools.

Implemented MCP tools:

Database: SQLite via Node.js built-in node:sqlite (Node ≥ 22.5.0). Development database: data/ripple.db (git-ignored).

Related MCP server: MCP Project Manager

Monorepo structure

• apps/web/ — React + Vite frontend placeholder

• services/mcp-server/ — Node.js + TypeScript MCP server placeholder

• services/voice-service/ — transcription/diarization placeholder

• packages/shared/ — shared types/schemas placeholder

• docs/ — architecture and team workflow docs

• tests/ — testing strategy placeholder

• data/ — local development data (non-committed artifacts)

Planned architecture

See docs/architecture.md.

Prerequisites

• Git

• Node.js (LTS)

• npm

Setup

git clone https://github.com/Yengeshwaran/ripple-mcp.git
cd ripple-mcp

When installable packages are added:

npm install

Development commands

# Install dependencies
npm install

# Start MCP server (port 3100)
npm run mcp:dev

# TypeScript type check
npm run mcp:typecheck

# Run automated tests
npm test

MCP endpoint: http://localhost:3100/mcp (Streamable HTTP) Health endpoint: http://localhost:3100/health

Testing with MCP Inspector

1. npx @modelcontextprotocol/inspector

2. Connection type: Streamable HTTP

3. URL: http://localhost:3100/mcp

4. Connect → call ping, create_task, list_tasks, or assign_task

Team guide

• Onboarding: docs/TEAM_SETUP.md

• Contribution rules: docs/CONTRIBUTING.md

Team responsibilities

1. Team lead: MCP backend, data model, integration, and final release.

2. Member 2: React frontend and task dashboard.

3. Member 3: voice-processing research, speaker-label mapping workflow, task extraction, and integration testing.