feat(v2): monorepo with single MCP router fronting Nakatomi + AutoMem#1
Merged
mrdulasolutions merged 1 commit intomainfrom Apr 20, 2026
Merged
feat(v2): monorepo with single MCP router fronting Nakatomi + AutoMem#1mrdulasolutions merged 1 commit intomainfrom
mrdulasolutions merged 1 commit intomainfrom
Conversation
Restructure REVA-TURBO into a full ops stack:
plugin/ the Claude Code skills engine (46 skills, was at root)
services/mcp-router/ single public /mcp endpoint (FastAPI + FastMCP)
services/nakatomi-backend/ private CRM (Nakatomi upstream + Rev A seed)
services/automem-backend/ private memory (AutoMem upstream)
railway/ one-click template: 1 project, 3 services + 3 plugins
docs/ moved ARCHITECTURE / INSTALL / ROADMAP here,
added ARCHITECTURE_V2.md
The router is the key idea: one URL, one bearer token, unified tool
namespace (crm_*, mem_*, reva_*). Cross-system tools like
reva_remember_about_entity orchestrate CRM + memory writes in a single
MCP call — something two isolated MCPs cannot do.
Rev A overlays (pipeline stages, custom_fields, memory taxonomy tags)
applied at deploy time by services/nakatomi-backend/seed/reva.py. No
forked source.
Plugin install.sh now accepts REVA_MCP_URL + REVA_API_KEY env and
registers the MCP server in ~/.claude/mcp.json automatically. Added
two new skills (reva-turbo-reva-crm, reva-turbo-reva-memory) pointing
at the router.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Restructure REVA-TURBO into a full ops stack:
plugin/ the Claude Code skills engine (46 skills, was at root)
services/mcp-router/ single public /mcp endpoint (FastAPI + FastMCP)
services/nakatomi-backend/ private CRM (Nakatomi upstream + Rev A seed)
services/automem-backend/ private memory (AutoMem upstream)
railway/ one-click template: 1 project, 3 services + 3 plugins
docs/ moved ARCHITECTURE / INSTALL / ROADMAP here,
added ARCHITECTURE_V2.md
The router is the key idea: one URL, one bearer token, unified tool namespace (crm_, mem_, reva_*). Cross-system tools like reva_remember_about_entity orchestrate CRM + memory writes in a single MCP call — something two isolated MCPs cannot do.
Rev A overlays (pipeline stages, custom_fields, memory taxonomy tags) applied at deploy time by services/nakatomi-backend/seed/reva.py. No forked source.
Plugin install.sh now accepts REVA_MCP_URL + REVA_API_KEY env and registers the MCP server in ~/.claude/mcp.json automatically. Added two new skills (reva-turbo-reva-crm, reva-turbo-reva-memory) pointing at the router.