LoreKeeper

com.lorekeeperPublished by lorekeeper.comOfficial publisherv1.0.2Updated Oct 29, 2026

Mess in, magic out: your D&D and TTRPG notes become a private world store any AI app can read.

VerifiedStreamable HTTPWeb executableKnowledge & Memory

Overview

AI-generated overview

LoreKeeper turns D&D and TTRPG notes into a private world store that AI apps can read through a remote MCP endpoint.

What you can do
  • The listing names no individual tools, so capabilities come from the short description only.
  • It is described as taking messy tabletop campaign notes and turning them into a structured, private world store.
  • That store is meant to be readable by any AI app, so an assistant can draw on campaign lore.
  • It runs as a hosted remote endpoint rather than a local package.
When to use it
Worth considering if you keep D&D or other TTRPG campaign notes and want an AI assistant to work from that material as a shared world reference.
Requirements
A remote MCP endpoint at api.lorekeeper.com over streamable HTTP. OAuth authentication is required, so a LoreKeeper account is needed. No environment variables or headers are declared.
Before you install
Campaign notes are uploaded to a third-party hosted service, so check its privacy and data-handling terms before sending private material. OAuth grants the server access under your account; review the scopes requested. No tool list is published, so what it can read or change is unverified.

Installation

In SourceWeft

  1. Open LoreKeeper in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.lorekeeper%2Florekeeper/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "lorekeeper": {
      "type": "http",
      "url": "https://api.lorekeeper.com/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

3
  1. v1.0.2LatestOct 29, 2026
  2. v1.0.1Oct 26, 2026
  3. v1.0.0Oct 26, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.