Your LoreHub world, ready for any AI agent
One world, for every role on the team
Each role asks the agent for something different. These are the tools and prompts each one uses.
readworks with any keywriteneeds a Write keyGet the canon map, read a dialogue as a script, and with a Write key draft dialogues, nodes, lines, options and links.
get_world_overviewget_dialoguesearch_worldcreate_dialoguerename_dialogueadd_nodeedit_nodeadd_optionedit_optionlink_nodesRead characters, places, lore and the timeline, check a scene for continuity, and create, edit and relate documents.
get_documentlist_documentsget_timelinecontinuity_checkcreate_documentedit_documentrelate_documentsSee a story's route map and variables, check a dialogue for dead ends, and add variables and the nodes that set them.
list_dialoguesget_story_mapcheck_dialoguecreate_variableset_variable_on_nodemove_nodeDirector's notes → reference briefs and shot lists, and with a Write key draw Meta Areas and set a node's meta values.
get_dialogue_metareference_briefshot_listadd_meta_areaedit_meta_areaset_node_metaEvery line of a story by speaker with line and word counts, the world's numbers, and a voice casting sheet per character.
get_character_linesget_world_statsvoice_casting_sheetRead every line with its translations and status, review a language for tone and terms, and write translations.
get_translationstranslation_reviewset_translationGet a dialogue's export JSON, as the Export button gives it, and a guide with loader code for Unity, Godot or Unreal.
get_exportengine_import_guideWhat your agent can read and change
Sixteen tools read and seventeen write, plus six ready-made prompts. Every result says how many calls the world has left today.
Work with any key. Most answer in one API call.
list_worldsThe worlds you added, with their ids and which one is current.
use_worldSwitches the current world for this session, by name or id.
get_world_overviewThe canon map: stories, documents by folder and tag, and counts of everything.
search_worldMatches in document names, dialogue names, lines and option texts.
list_dialoguesStories and their dialogues with ids, filtered by name if you like.
get_dialogueA dialogue as a script: each node's speaker, lines, options, conditions, variables, meta values and Meta Areas.
check_dialogueUnreachable nodes, options without a target, dead ends and variables set but never checked.
get_documentA character, place or other document: its description, tags, relations and the dialogues that mention it.
list_documentsDocuments with their folder and tags, filtered by tag, folder or name.
get_timelineThe calendar and the events in date order, with their linked documents.
get_story_mapA story's route map, its route scopes, and every variable with where it's set and checked.
get_character_linesEvery line of a story grouped by speaker, with line and word counts.
get_translationsEach line and option with its translation and status in every language.
get_exportA dialogue's Export Schema v2 JSON, as the Export button gives it.
get_world_statsDialogues, nodes, lines and words per story and character, and translation progress.
get_dialogue_metaEach Meta Area's title, note, priority and rules, the lines inside it, and where areas overlap.
Need a Write key. Agents create and edit, never delete, and every change shows in your history. A write can take more than one API call.
create_dialogueCreates a dialogue in a story.
rename_dialogueRenames a dialogue.
add_nodeAdds a node, optionally after another, with a speaker and lines.
edit_nodeChanges a node's speaker and lines in place.
move_nodeMoves a node on the canvas.
set_node_metaSets a node's meta values, like shot = close_up.
add_optionAdds an option, optionally shown only when variables have given values.
edit_optionChanges an option's text.
link_nodesLinks a node, an option or the start to a node, optionally with conditions.
create_variableCreates a true/false story variable.
set_variable_on_nodeMakes a node set a variable when it plays.
create_documentCreates a document with a description, folder and tags.
edit_documentChanges a document's name, description or folder, and adds tags.
relate_documentsRelates two documents, like Father and Son.
add_meta_areaDraws a Meta Area with a note, colour and rules.
edit_meta_areaChanges a Meta Area's text, place, size or rules.
set_translationWrites a line's translation in one language.
continuity_checkChecks a scene against the documents and the timeline.
translation_reviewFinds missing and outdated translations and reviews meaning, tone and terms.
engine_import_guideThe export's shape and loader code for Unity, Godot or Unreal.
reference_briefA visual brief per Meta Area: subject, characters, shot, background and mood.
shot_listA numbered shot list for a dialogue, one shot per node.
voice_casting_sheetOne entry per speaking character, with voice direction and sample lines.
Set it up in a minute
You need uv, which downloads and runs the server for you, and an API key for each world. Your keys stay in your system keychain, never in an MCP config.
In LoreHub, open the avatar menu → Profile → API keys, pick the world, choose Read or Write, choose when the key expires and select Create key. Pick Read to explore, and Write when you want the agent to build. LoreHub shows the key, which starts with lh_, only once: copy it. The world id is on the same page: under the form once you pick a world, and next to each key in the list, as World id with a Copy button. Right after you create a key, LoreHub also shows the ready-made world add command.
Run the ready-made command, or this one with the World id, and paste the key when it asks. The command has no key in it. It checks the key with LoreHub and stores it in your system keychain: the macOS Keychain, Windows Credential Manager or the Secret Service on Linux.
uvx lorehub-mcp world add --id <world id>Add one key per world. One world is current, like a subscription in az: the tools use it unless the agent names another, and the agent can switch for a session with use_world.
# * marks the current world
uvx lorehub-mcp world list
# by name or id
uvx lorehub-mcp world use "Tom's World"
uvx lorehub-mcp world remove <name or id>The command and the config need no key: the server reads it from your keychain.
claude mcp add LoreHub -- uvx lorehub-mcpIn Claude Desktop, open Settings → Desktop app → Extensions → Local MCP servers → Edit config, open claude_desktop_config.json in a text editor and add the LoreHub entry inside mcpServers, keeping what is already in the file. In Cursor, add it to ~/.cursor/mcp.json:
{
"mcpServers": {
"LoreHub": {
"command": "uvx",
"args": ["lorehub-mcp"]
}
}
}Then quit Claude Desktop completely (Cmd+Q on Mac, Quit from the tray icon on Windows) and open it again: LoreHub shows under Local MCP servers as Running. If it says uvx was not found, put the full path that which uvx prints (where uvx on Windows) in command.
On a machine without a keychain, put the key and its world in the server's environment instead. LOREHUB_API_KEY needs LOREHUB_WORLD_ID, and together they win over the worlds you added.
{
"mcpServers": {
"LoreHub": {
"command": "uvx",
"args": ["lorehub-mcp"],
"env": {
"LOREHUB_API_KEY": "lh_your-key",
"LOREHUB_WORLD_ID": "your-world-id"
}
}
}
}