Built an MCP server that connects Cursor to your team’s architectural decisions and project context.
The problem it solves:
Every new Cursor session starts from zero. Your team’s decisions, which state library you use, how you structure database access, which patterns you’ve agreed on, aren’t there. So Cursor generates code that slowly drifts from your actual architecture.
What Hopsule does:
You record decisions and context once in Hopsule. The MCP server injects them into every Cursor session automatically. No copy-pasting. No re-explaining.
Example: Your team records: “Database access must go through the repository layer.” Every Cursor session that follows knows it, without you typing it again.
What’s included:
-
MCP server for Cursor
-
CLI Tool (npm install -g hopsule)
-
IDE extension for inline enforcement
-
Decision lifecycle (Draft → Accepted → Deprecated)
-
GitHub Sync & Github PR Comment App
Advisory-only. We never block your code, just surface conflicts where they happen.
