NuklearRabbit
c5b7e21f81
Four read-only, service-token-protected MCP provider endpoints (operations summary, attention vehicles, vehicle details, knowledge search facade). Shared-secret auth reusing the M4 callback pattern. Service-request audit trail for every call. Extracted shared operations-summary logic out of the dashboard router to avoid duplicating retrieval logic. 66 backend tests passing, ruff clean. Verified all four endpoints and audit trail directly via curl against the live stack (no live MCP Hub instance available in this environment).
MobilityOps
Connected operations for vehicle rental and service teams.
MobilityOps is a working proof of concept for a fictitious mobility company. It combines vehicle and booking operations, a controlled vehicle-return workflow, data-quality review, RAGcore-backed internal knowledge, n8n orchestration and read-only tools published through ITWorx MCP Hub.
All people, companies, vehicles, bookings and documents are synthetic. The workflows, validation, integrations, audit logging and access boundaries are intended to be real.
Scope
The PoC implements:
- operations dashboard;
- vehicle and booking views;
- one complete vehicle-return workflow;
- five deterministic data-quality checks;
- human review and customer merge;
- audit trail;
- RAGcore-backed knowledge assistant with citations;
- one n8n return-processing workflow;
- four read-only MCP tools through ITWorx MCP Hub;
- deterministic demo reset and five-minute showcase.
It is not an ERP, CRM, accounting package, public booking site, payment system or autonomous agent.
Repository map
CLAUDE.md— binding implementation rules.MASTER_BUILD_PROMPT.md— prompt to start an autonomous Claude run.PROJECT_STATE.md— short persistent project memory.docs/— product, architecture, UX and acceptance specification.contracts/— OpenAPI, event and MCP contracts.knowledge/— fictitious source documents for the MobilityOps RAGcore workspace.seed/— deterministic synthetic dataset and generator.n8n/— importable workflow definitions.backend/andfrontend/— minimal bootable scaffold, not the finished application.
Local scaffold
cp .env.example .env
docker compose up --build
Expected scaffold endpoints:
- Web:
http://localhost:1228 - API health:
http://localhost:8128/health - n8n:
http://localhost:5678
The finished project must keep these defaults configurable.