Lore DB for Developers

Connect your IDE to your team’s documentation. Look up internal APIs, deployment procedures, and architecture decisions without leaving your code editor.

The problem

You’re debugging a production issue at 2 AM. You know there’s a runbook somewhere, but where? Confluence? Google Docs? A Slack thread from six months ago? By the time you find it, the issue has escalated.

The solution

Connect your IDE (Cursor, VS Code, Claude Code) to Lore DB via MCP. Your AI assistant can now search your team’s documentation in real time.

Example workflow

You’re working in Cursor on a payment service bug:

1. You ask Claude: “What’s our retry policy for Stripe webhooks?”
2. Claude searches Lore DB and finds the “Payment Service — Stripe Webhook Configuration” doc
3. It answers with the exact retry intervals, timeout settings, and the reasoning behind them
4. You fix the bug using the documented configuration
5. You notice the doc is missing the new error code. You tell Claude: “Add the WEBHOOK_TIMEOUT_429 error code to that document”
6. Claude updates the doc — no context switch, no browser tab

What to put in Lore DB

As a developer, your highest-value documents are:

• Architecture decisions (ADRs) — Why the system is built the way it is
• Deployment runbooks — Step-by-step procedures for each service
• API documentation — Internal API contracts, request/response formats
• Configuration guides — Environment variables, feature flags, thresholds
• Incident post-mortems — What went wrong, what was fixed, what to watch for
• Onboarding guides — How to set up the dev environment, run tests, deploy

Getting started

1. Connect your IDE (takes 30 seconds)
2. Create a library for your team’s docs
3. Add your most important runbooks and guides
4. Add AI agent instructions to your CLAUDE.md