Graphmind

io.github.CloudCorpRecordsPublished by GitHub account CloudCorpRecordsv0.1.0Updated Oct 29, 2026

Persistent knowledge graph: entities, relations, and observations for agents.

VerifiedSTDIODesktop onlyFiles & StorageKnowledge & Memory

Overview

AI-generated overview

Local MCP server that gives an assistant a persistent knowledge graph of entities, typed relations and observations, stored in one JSON file.

What you can do
  • Create entities with a type and plain-text observations, and add typed relations between existing entities
  • Append observations to existing entities, skipping duplicates
  • Delete entities, observations or relations
  • Read the whole graph, or open specific entities by name with the relations between them
  • Search entity names, types and observations by case-insensitive substring
When to use it
Useful when an assistant should remember facts across sessions without running a database or signing up for a service, and when you want that memory to stay a readable, hand-editable JSON file you can inspect or version.
Requirements
Runs locally over stdio via npx or the Docker image; no account, API key or network service needed. The store path comes from the GRAPHMIND_FILE environment variable and defaults to ./graphmind.json in the working directory. With Docker, mount a volume over the working directory to keep the graph between runs.
Before you install
The tools write to and delete from the graph file, and deleting an entity also removes every relation touching it. The file is rewritten after each change, so point GRAPHMIND_FILE at a path you are willing to have modified. Entity names are identity, so duplicates are silently skipped and renaming means deleting and recreating.

Installation

In SourceWeft

  1. Open Graphmind in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

graphmind

graphmind is a small, durable memory for agents: a knowledge graph you can build up a fact at a time and query back later. You record entities — people, places, projects, anything with a name — each with a type and a growing list of plain-text observations, and you connect them with typed relations ("Alice — lives_in → Lisbon"). The whole graph lives in one JSON file on disk, so the memory survives restarts and stays readable, diffable, and editable by hand.

There is no database to run and no service to sign up for. The graph file is the product.

Install

bash
npx @reneturcios/graphmind read

Or run the container image:

bash
docker run -i ghcr.io/cloudcorprecords/graphmind

The container defaults to the MCP server (see below). Pass CLI arguments to use it as a CLI instead. If you run the container, mount a volume over the working directory if you want the graph file to persist between runs.

Where the graph lives

The store file path comes from the GRAPHMIND_FILE environment variable and defaults to ./graphmind.json in the current working directory. The file is loaded when the server (or a CLI command) starts, and it is rewritten after every change, so what is on disk is always the full current graph:

json
{  "entities": [    { "name": "Alice", "entityType": "person", "observations": ["Lives in Lisbon"] }  ],  "relations": [    { "from": "Alice", "to": "Lisbon", "relationType": "lives_in" }  ]}

CLI

The CLI is a read/inspect face over the same store file the MCP server writes:

bash
# Print the whole graph as JSONgraphmind read
# Print the subgraph matching a search termgraphmind search lisbon
# Point at a specific store fileGRAPHMIND_FILE=~/notes/graph.json graphmind read
graphmind --version

Exit codes: 0 on success, 1 when the store cannot be read or written, 2 for usage errors.

MCP server

One bin serves both faces. The mcp subcommand starts a stdio MCP server:

bash
npx -y @reneturcios/graphmind mcp

MCP client configuration:

json
{  "mcpServers": {    "graphmind": {      "command": "npx",      "args": ["-y", "@reneturcios/graphmind", "mcp"],      "env": { "GRAPHMIND_FILE": "/path/to/graphmind.json" }    }  }}

Tools

ToolInputWhat it does
create_entitiesentities: array of {name, entityType, observations}Adds entities whose names are not already taken. Existing names are skipped and the stored entity is left untouched. Returns only the entities actually created.
create_relationsrelations: array of {from, to, relationType}Adds relations whose exact triple is not already present. Returns only the relations actually created.
add_observationsobservations: array of {entityName, contents}Appends observation strings to existing entities, skipping strings the entity already has. Returns what was added, per entity.
delete_entitiesentityNames: array of stringsRemoves the named entities and every relation that touches any of them.
delete_observationsdeletions: array of {entityName, observations}Removes the listed observation strings from the named entities.
delete_relationsrelations: array of {from, to, relationType}Removes relations matching the given exact triples.
read_graph(none)Returns the entire graph: all entities and all relations.
search_nodesquery: stringCase-insensitive substring search over entity names, types, and observations. Returns the matching entities plus the relations whose endpoints both matched.
open_nodesnames: array of stringsReturns the named entities plus the relations between them. Unknown names are skipped.

Behaviour worth knowing

  • Names are identity. An entity is its name; creating a second entity with the same name does nothing. Rename by deleting and recreating.
  • Relations need real endpoints. create_relations requires both the from and to entities to already exist, and fails the whole call if one is missing — no stub entities are invented, so a typo surfaces immediately instead of quietly corrupting the graph.
  • Observations are a set, in order. Adding a string an entity already carries is a no-op; new strings append in the order given.
  • Deletes cascade only from entities. Deleting an entity removes its relations; deleting observations or relations never touches anything else.

Development

bash
npm installnpm run build   # tsc -> dist/npm test        # node test runner over test/*.test.ts, no networknpm run dev     # run the CLI from source via tsx

License

MIT — see LICENSE.

Source: README.md at commit f676d42

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.0LatestOct 29, 2026

Score

50% 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 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • 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
  • License10 pts