Skip to content
Back to search

wrenlore

Self-hosted knowledge infrastructure for humans and AI agents.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/wrenlore--wrenlore/badge.svg)](/listings/wrenlore--wrenlore)

HTML

<a href="/listings/wrenlore--wrenlore"><img src="/api/listings/wrenlore--wrenlore/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

Requirements: Docker Engine, the Docker Compose plugin and Git.

git clone https://github.com/wrenlore/wrenlore.git
cd wrenlore
cp .env.example .env

# Edit .env: set APP_SECRET to a random value of at least 32 characters.
# For non-local use, also set APP_URL and explicit database credentials.

docker compose up -d --build
curl -f http://localhost:3000/api/health

Open [http://localhost:3000](http://localhost:3000). The application runs migrations on startup. Keep the database and storage volumes when upgrading.

For TLS, reverse-proxy configuration, backups and production environment values, use the [deployment runbook](README-deploy.md).

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 139 lines
  1. # WrenLore
  2. [![MCP regressions](https://github.com/wrenlore/wrenlore/actions/workflows/mcp-regressions.yml/badge.svg)](https://github.com/wrenlore/wrenlore/actions/workflows/mcp-regressions.yml)
  3. [![Editor regressions](https://github.com/wrenlore/wrenlore/actions/workflows/editor-regressions.yml/badge.svg)](https://github.com/wrenlore/wrenlore/actions/workflows/editor-regressions.yml)
  4. [![GitHub release](https://img.shields.io/github/v/release/wrenlore/wrenlore)](https://github.com/wrenlore/wrenlore/releases/latest)
  5. [![License: AGPL-3.0](https://img.shields.io/badge/license-AGPL--3.0-1d3b32)](LICENSE)
  6. **Self-hosted knowledge infrastructure for humans and AI agents.**
  7. WrenLore is a collaborative wiki for teams that want clean human editing, private deployment and useful AI access without giving an agent a shared administrator account.
  8. [Website](https://wrenlore.com/) · [Releases](https://github.com/wrenlore/wrenlore/releases) · [Deployment guide](README-deploy.md) · [MCP setup](docs/MCP.md) · [Security](SECURITY.md)
  9. ![WrenLore knowledge workspace showing people, documents and systems connected to permission-aware search, versioned editing and scoped MCP access](docs/assets/screenshots/wrenlore-showcase-overview.jpg)
  10. ## What makes WrenLore different
  11. | Capability | What it means in practice |
  12. |---|---|
  13. | **A proper team wiki** | Structured pages, spaces, comments, page permissions, public sharing and version history in a focused web interface. |
  14. | **Scoped MCP access** | Agents search, read, create and revision-safely edit knowledge through user-owned tokens with read/write, space and expiry controls. |
  15. | **Attribution that survives automation** | Supported agent actions are recorded as **User, via Agent**, rather than disappearing behind a generic integration account. |
  16. | **Grounded AI workflows** | Permission-aware retrieval, provider/model administration and AI-assisted editing keep answers attached to the team's real source material. |
  17. | **Identity and operational control** | SSO, local MFA, audit events and self-hosted deployment give operators control over access, infrastructure and data. |
  18. | **Open source** | AGPL-3.0 source, PostgreSQL data and Docker-based deployment provide a real exit path instead of a decorative export button. |
  19. WrenLore has no per-user licence fee. You run the infrastructure and choose any external model services you want to connect.
  20. ## Quick start
  21. Requirements: Docker Engine, the Docker Compose plugin and Git.
  22. ```bash
  23. git clone https://github.com/wrenlore/wrenlore.git
  24. cd wrenlore
  25. cp .env.example .env
  26. # Edit .env: set APP_SECRET to a random value of at least 32 characters.
  27. # For non-local use, also set APP_URL and explicit database credentials.
  28. docker compose up -d --build
  29. curl -f http://localhost:3000/api/health
  30. ```
  31. Open [http://localhost:3000](http://localhost:3000). The application runs migrations on startup. Keep the database and storage volumes when upgrading.
  32. For TLS, reverse-proxy configuration, backups and production environment values, use the [deployment runbook](README-deploy.md).
  33. ## Built for agent access without the shared admin token
  34. WrenLore exposes a Streamable HTTP MCP endpoint at `/mcp`. A workspace administrator enables agent connections, then each user creates their own named token.
  35. Tokens can be:
  36. - read-only or read/write;
  37. - restricted to selected spaces;
  38. - given an expiry and revoked independently;
  39. - copied once, then stored as a hash;
  40. - traced back to the owning user and named agent connection.
  41. The user's live workspace, space and page permissions remain authoritative on every call. Writes use expected revisions and idempotency keys, so an agent cannot silently overwrite a newer human edit or apply the same operation twice after a lost network response.
  42. Current MCP tools cover context, spaces, page trees, search, page reads, page creation, direct document edits, comments and history. Deletion, moves, sharing and permission changes are deliberately outside MCP V1.
  43. See [MCP setup, client examples and editing semantics](docs/MCP.md).
  44. ![WrenLore MCP sequence showing scoped tokens, permission checks and revision-safe agent editing](docs/assets/screenshots/agents-at-the-gate.jpg)
  45. ## A few real workspace views
  46. <table>
  47. <tr>
  48. <td width="50%">
  49. <img src="docs/assets/screenshots/knowledge-constellation.jpg" alt="A WrenLore mind map connecting product, engineering, operations, research and agent knowledge" />
  50. <br /><strong>Connected knowledge</strong><br />Decisions, evidence, owners and operational context stay legible.
  51. </td>
  52. <td width="50%">
  53. <img src="docs/assets/screenshots/open-source-by-design.jpg" alt="A WrenLore diagram showing open source code, controlled data, chosen infrastructure and agent APIs" />
  54. <br /><strong>Open by design</strong><br />Inspect the code, control the data and choose where it runs.
  55. </td>
  56. </tr>
  57. <tr>
  58. <td width="50%">
  59. <img src="docs/assets/screenshots/trusted-answer-flow.jpg" alt="A WrenLore flowchart from a user question through permission-aware retrieval to a verified answer" />
  60. <br /><strong>Grounded answers</strong><br />Permission-aware retrieval keeps answers inspectable and bounded.
  61. </td>
  62. <td width="50%">
  63. <img src="docs/assets/screenshots/north-star-roadmap.jpg" alt="A WrenLore product timeline from structured team knowledge to attributable automation" />
  64. <br /><strong>A practical direction</strong><br />Portable knowledge, human approval and attributable automation.
  65. </td>
  66. </tr>
  67. </table>
  68. ![A WrenLore incident room combining a timeline, operational metrics, decisions, owners and follow-up tasks](docs/assets/screenshots/incident-room.jpg)
  69. The showcase pages above were created through WrenLore's own MCP endpoint and persisted with **User, via Agent** attribution.
  70. ## Deployment shape
  71. The supplied Compose stack runs:
  72. - the WrenLore application, built from this repository;
  73. - PostgreSQL with pgvector;
  74. - Redis with append-only persistence;
  75. - local file storage by default, with S3-compatible storage available.
  76. Docker is the preferred deployment and deployment-like verification path. WrenLore does not use upstream Docmost images, update flows or release automation.
  77. ## Documentation
  78. - [Deployment runbook](README-deploy.md)
  79. - [MCP setup and semantics](docs/MCP.md)
  80. - [Page-history user guide](docs/user-guide/page-history.md)
  81. - [Entra ID SAML setup](docs/SAML_ENTRA_SETUP.md)
  82. - [Contributing](CONTRIBUTING.md)
  83. - [Public release checklist](docs/PUBLIC_RELEASE_CHECKLIST.md)
  84. - [Public provenance summary](docs/provenance/public-release-provenance.md)
  85. ## Provenance and licensing
  86. WrenLore is derived from the Docmost Community Edition codebase. The WrenLore public foundation is tagged `wrenlore-open-foundation-2026-05-01` in this repository, and the codebases diverge from that point.
  87. WrenLore is not an upstream Docmost deployment target and is not affiliated with or endorsed by Docmost. Docmost and related marks are trademarks of Docmost Inc.
  88. WrenLore is derived from AGPL-3.0-licensed Docmost Community code and is itself licensed under AGPL-3.0. This repository does not include Docmost Enterprise Edition source code, assets, tests, documentation or implementation details. Public visibility of upstream Enterprise Edition material is not permission to reuse it.
  89. WrenLore's SSO, audit, AI, sharing controls and other product capabilities are WrenLore-native implementations based on WrenLore requirements, public standards, public documentation, public interoperability behaviour and original implementation work. Feature overlap can exist between products; this project does not reuse proprietary Docmost Enterprise implementation.
  90. Source for every released WrenLore version is available through the corresponding tag and release archive. See the [public provenance summary](docs/provenance/public-release-provenance.md) and [contribution policy](CONTRIBUTING.md) for the clean-cut engineering rules.
  91. ## Security posture
  92. WrenLore tracks vulnerabilities in its dependency stack and inherited Community-derived code. After the documented fork point, fixes are implemented independently from public vulnerability disclosures and WrenLore code analysis; the project does not cherry-pick, merge or rebase from upstream Docmost.
  93. Security reports are handled under [SECURITY.md](SECURITY.md). Audit coverage is actively expanded and is not represented as complete for every browser and administrative action.
  94. ## Licence
  95. WrenLore is provided under the [GNU Affero General Public License v3.0](LICENSE), without warranty.

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.