Data Portability

Your data is yours. Lore DB is designed with zero lock-in — everything you put in can come out.

What “no lock-in” means

• Documents are Markdown. Plain text that works everywhere.
• Exports are JSON. Standard format, readable by any tool or script.
• MCP is a standard protocol. Your AI tool config is one URL you can add or remove in 10 seconds.
• OAuth means no password dependency. You sign in with Google — there’s no Lore DB-specific account to manage.

Exporting a library

1. Open a library you own
2. Click Export (or use the GET /api/libraries/{id}/export endpoint)
3. Download the JSON file

The export includes everything:

{
  "name": "Engineering Runbooks",
  "description": "Deployment, incident response, and monitoring",
  "documents": [
    {
      "title": "Deployment Procedures",
      "content": "# Deployment Procedures\n\nFull markdown content...",
      "created_at": "2026-03-15T10:00:00Z",
      "updated_at": "2026-03-20T14:30:00Z"
    }
  ]
}

No metadata is stripped. No content is truncated. What you exported is what you imported.

Importing a library

1. Go to Libraries
2. Click Import
3. Select your JSON file
4. Documents are created and indexed automatically

You can import exports from other Lore DB accounts, or create the JSON format manually from any source.

Disconnecting an AI tool

Removing Lore DB from your AI tool takes seconds:

• Claude Desktop: Delete the lore-db entry from claude_desktop_config.json
• Claude Code: Run claude mcp remove lore-db
• Cursor / VS Code: Delete the entry from .cursor/mcp.json
• ChatGPT: Remove the connector in Settings

Your documents remain in Lore DB until you delete them. The AI tool simply loses access.

What if Lore DB shuts down?

We plan to be around for a long time. But if the worst happens:

1. Your exports work offline. The JSON files contain complete document content — no references to Lore DB servers.
2. Markdown is universal. Your content works in any wiki, docs site, or knowledge base.
3. MCP is an open standard. If another MCP-compatible knowledge base appears, migrating is importing a JSON file.

We will always give advance notice before any service changes, and we will always provide a way to export your data.