loaditout.ai
SkillsPacksTrendingLeaderboardAPI DocsBlogSubmitRequestsCompareAgentsXPrivacyDisclaimer
{}loaditout.ai
Skills & MCPPacksBlog

GERP

MCP Tool

quantDIY/GERP

GERP is an open source ERP built atop Google Workspace (Google-ERP). A FAANG-grade, multi-domain, headless ERP matrix with GraphQL ready for custom fronted integrations. Built with Go, Cloud Spanner, Temporal Sagas, a GraphQL BFF, CLI, and a native MCP interface for autonomous AI agents. MIT License

Install

$ npx loaditout add quantDIY/GERP

Platform-specific configuration:

.claude/settings.json
{
  "mcpServers": {
    "GERP": {
      "command": "npx",
      "args": [
        "-y",
        "GERP"
      ]
    }
  }
}

Add the config above to .claude/settings.json under the mcpServers key.

About

🌐 GERP (Google-Enterprise Resource Planning)

GERP is a FAANG-grade, multi-domain Enterprise Resource Planning (ERP) matrix. GERP demonstrates how to scale massive distributed data systems using absolute Domain-Driven Design (DDD), cross-domain Temporal Sagas, and zero SQL foreign keys.

This is not just an ERP. It is a self-aware corporate engine exposed natively to AI agents via the Model Context Protocol (MCP).

Designed to utilize the Google Workspace API for iam role management, permissions, and identity, then integrating all Gsuite tools & apps natively, creating a seamless ERP management system that completes the Google Workspace experiemce. Everything you need to run a business of any size, infinitely customizable, from a single vendor. Lightweight, lightspeed, Go code with the QuanuX Knowledge Vector enabling AI agents to build your ERP to their AGI standards while you focus on your business.

---

🏛️ Core Architectural Pillars
1. The Golden Thread (Zero SQL Foreign Keys)

To achieve infinite horizontal scale, GERP completely abandons database-layer foreign keys between domains. A SalesOrder in Revenue does not use an SQL JOIN to find a Customer in Master Data. Instead, GERP employs the Golden Thread: strict uuid.UUID pointers managed in application space. Each domain owns its Spanner tables exclusively.

2. Distributed Temporal Sagas

Because domains are isolated, GERP cannot rely on single-database ACID transactions. Instead, it uses Temporal Workflows as its ne

Tags

ai-agentscloud-spannercobra-clidomain-driven-designerpgerpgolanggoogle-cloud-platformgoogle-erpgoogle-workspacegraphqliamknowledge-vectormcp-servermicroservicestemporal-workflowsviper-cli

Reviews

Loading reviews...

Quality Signals

2
Stars
0
Installs
Last updated21 days ago
Security: AREADME

Safety

Risk Levelmedium
Data Access
read
Network Accessnone

Details

Sourcegithub-crawl
Last commit3/27/2026
View on GitHub→

Embed Badge

[![Loaditout](https://loaditout.ai/api/badge/quantDIY/GERP)](https://loaditout.ai/skills/quantDIY/GERP)