add_npc
To add new NPC nodes.
LABSCO SUMMARY
You write the schema; the tools that write to it are generated from it.
That inversion is what keeps the graph coherent: a required field with a relationship means the AI creates both the node and its edge every time, and an enum means it picks from your list rather than inventing a race. Worth knowing before you build on it: conflicting information is last-write-wins, so track sources in metadata or split disputed facts into separate nodes.
What it is
A local knowledge graph server aimed at text-based RPGs and interactive storytelling, where the tools an AI gets are generated from schemas you write.
What you get
- Nodes with a name, a nodeType you define, and metadata strings describing them
- Edges between nodes with an edgeType such as owns or located_in, and an optional weight from 0 to 1
- Tools generated from each schema: add, update and delete per entity type, so an npc schema yields add_npc, update_npc and delete_npc
- Schema features that steer the model — required fields, enum choices, and relationship definitions that make it create the edge along with the node
- 11 pre-built schemas for text-based RPGs, ready to start from
- Error feedback returned to the AI, so it can correct a malformed write
- A SchemaManager page for editing schemas visually, and a Memory Viewer for exploring the graph as a node-link diagram, table or raw JSON
Requirements
Node.js 18 or higher and npm. Clone, npm install, npm run build, then point your client at dist/index.js. Schema files ending in .schema.json go in dist/data/schemas and are picked up at startup; a schema's name must start with add_ to be recognised. Data lives in dist/data/memory.json, and MEMORY_FILE and SCHEMAS_DIR can move both.
Setup effort
Build from source — git clone https://github.com/CheMiguel23/memorymesh.git
USE CASES
01
Keeping a long campaign consistent
Store characters, locations and items as typed nodes so last week's details survive into this week's session.
02
Making the AI record relationships, not just facts
Declare a required property with a relationship, and the edge gets created with the node every time.
03
Modelling something that is not an RPG
Write your own schemas — a social network, an org chart — and get the matching tools generated.
04
Seeing what the AI actually stored
Open the graph in the Memory Viewer and inspect nodes, edges and the raw JSON.
6 tools
Listed in project docs. Your client may show a different list.
update_npc
To modify existing NPC nodes.
delete_npc
To remove NPC nodes.
add_location
update_location
delete_location
BEFORE YOU INSTALL
What to know first
Requires
- Node.js 18 or later
- npm
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
git clone https://github.com/CheMiguel23/memorymesh.git
cd memorymesh
npm install
npm run buildMCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"memorymesh": {
"command": "node",
"args": [
"<YOUR_PATH_TO_PROJECT>/memorymesh/dist/index.js"
]
}
}
}<YOUR_PATH_TO_PROJECT>/ is the full path of the folder that holds your memorymesh clone, so the path ends in memorymesh/dist/index.js (on Windows, for example C:\\Projects\\memorymesh\\dist\\index.js). Restart Claude Desktop completely afterwards.
