A knowledge base your MCP clients can work with

WrenLore exposes governed knowledge workflows through the Model Context Protocol, so approved agents can retrieve and maintain the same pages people use.

Agent access needs a boundary, not a shared admin token

Scoped credentials

Issue user-owned MCP tokens with an explicit relationship to the person authorising the agent.

Permission-aware retrieval

Agents work inside the spaces and pages their credentials can access.

Readable attribution

Record edits as user, via agent, so reviewers can see who authorised an automated change.

Standard client connection

Use MCP-compatible clients without writing a one-off integration for every AI tool.

Questions teams ask

Which MCP clients can connect?

WrenLore documents standard MCP setup and is designed for clients that support remote MCP servers and bearer-token authentication.

Can an MCP client edit pages?

Yes, when the issued token and underlying user permissions allow the requested action.

Can tokens be revoked?

MCP credentials can be rotated or revoked by the user or administrator.

Run your knowledge base on your infrastructure.

WrenLore is open source, self-hosted and available under AGPL-3.0.

Get WrenLore on GitHub