LabscoMCP early access ↗
MCP SERVER · OFFICIAL PROJECT

Lore Company Knowledge

Your company's knowledge base, answering in whichever assistant your team already uses.

by lore ↗Vector Stores & RAG Retrieval✓ Official

LABSCO SUMMARY

Permission-preserving retrieval is the part that decides whether a knowledge base can be connected at all.

A company knowledge base contains salary bands and half-finished acquisition memos alongside the standard procedures. A connector that flattens permissions turns every assistant seat into an information leak, and a connector that preserves them makes the whole corpus safely reachable. Lore state the per-employee scoping explicitly, which is the right claim to make — and the right one to verify with a test account before rolling it out. Their answers-with-receipts framing is worth using: an answer you can trace to a document is what makes this usable for pricing questions.

What it is

Lore is a company knowledge base built from the documents you already have — past quotes, standard procedures, proposals, the handbook. The endpoint puts that in the assistants people already have open.

What you get

Search and retrieval across the company's uploaded knowledge, with the permission model preserved: their own description is that each employee's assistant sees only the pages that employee is allowed to see.

Requirements

OAuth or a personal token. Per-seat pricing with page, agent and audit-retention limits by tier, and free trials on the lower plans. How data through the connection is handled is a question to put to them directly.

Setup effort

Paste a URL, then authorize — add the endpoint to your client, then approve the OAuth consent screen

See installation options