Menerio
MichaelZelbel/menerio
Event store centralizado que conecta seus apps em um sistema coeso
Ver no GitHubServidor MCP que atua como um event store centralizado para dados pessoais, conectando múltiplas aplicações através de um barramento de eventos. Cada app mantém propriedade de seus dados enquanto o Menerio garante sincronização consistente entre o ecossistema, eliminando silos de dados fragmentados.
Instalação
npx convez-ai MichaelZelbel/menerio1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.
Métricas
Casos de uso
- Sincronizar dados entre múltiplas ferramentas de IA sem duplicação
- Manter consistência de registros em um ecossistema de aplicações distribuídas
- Integrar Discord, Telegram, Slack, GitHub e outras plataformas em fluxo único
Veredito

Projeto ambicioso em estado alpha que resolve o problema real de fragmentação de dados entre apps. Arquitetura sólida baseada em event sourcing, mas requer familiaridade com TypeScript/Supabase e tolera rough edges na integração de alguns serviços.
README
A tradução para o português deste README ainda está na fila.
Menerio
What it is
Menerio is a central event store for personal data.
Project status: Alpha Menerio is usable but still evolving. APIs, data structures, and UI may change without notice. Some features are partially implemented or experimental. We recommend it for early adopters and contributors who are comfortable with rough edges.
It connects multiple apps into a single system by capturing and distributing events. Instead of isolated tools with their own data silos, Menerio acts as the backbone that keeps everything in sync.
Each connected app remains the owner of its data, while Menerio ensures that relevant changes are shared across the system.
Why it exists
Most apps today operate in isolation. Data is fragmented, duplicated, and quickly becomes inconsistent.
Menerio solves this by introducing a simple principle:
- Every record has one clear owner
- All changes are emitted as events
- All connected apps stay in sync through a central event bus
This enables a system where:
- Data remains consistent across apps
- Ownership is always clear
- Integrations become simple and scalable
The goal is not to replace apps, but to connect them into a coherent system.
Core Concepts
Single Source of Truth
Each piece of data belongs to exactly one app. Other apps receive synchronized copies but never become the source of truth.
Event-Based Architecture
All changes are emitted as events (e.g. event.created, event.updated). Menerio stores and distributes these events to subscribed apps.
Star Model (one center, many spokes)
Apps do not communicate directly with each other. All communication flows through Menerio as the center.
Synchronization with Ownership
Changes made in one app propagate back to the owning app through Menerio, ensuring consistency without conflicts.
Features (Current State)
- Central event ingestion and storage
- Event distribution to connected applications
- Basic data synchronization model
- Supabase-backed data layer
- Lovable-based frontend and application structure
Known Limitations
- Some integrations (Discord, Telegram, Slack) require manual setup and are lightly tested.
- AI-powered features depend on external API keys and credit allowances that may not be configured in every environment.
- GitHub sync is functional but edge cases around conflict resolution are still maturing.
- The moderation system exists but has not been stress-tested at scale.
- Documentation covers the current state but may lag behind rapid changes.
Tech Stack
- Lovable (frontend and application scaffolding)
- Supabase (database, auth, backend services)
Documentation
- Architecture — app layers, frontend and backend structure
- Project Structure — root folders and conventions
- Data Model — main database entities explained in plain English
- Branding / White-Label — build the app as your own brand (skin) on your own domain
- Test Scenarios — end-to-end test coverage
- Open Source Philosophy — principles and licensing rationale
Getting Started
- Clone the repository
- Copy
.env.exampleto.env - Fill in your environment variables
- Install dependencies and start the dev server:
npm install, thennpm run dev
See CONTRIBUTING.md for checks and details.
Open Source
This project is open source under the AGPL-3.0 license.
The goal is to build Menerio in public as a foundational system for connecting personal data and applications.
Contributing
Contributions are welcome. See CONTRIBUTING.md for setup instructions and guidelines.