schist
Agent-first knowledge graph. Git is truth, SQLite is query, humans just watch.
schist is a generic, domain-agnostic knowledge graph where AI agents are the primary writers. Content is markdown + YAML frontmatter, version-controlled in git. SQLite provides the query layer. A static web viewer (D3.js + lunr.js) gives humans a read-only visualization.
Installation
pip install schist
This installs the schist CLI and the schist-ingest console script (used by the git post-commit hook).
Quick Start
# Create a vault
mkdir -p ~/vaults/research/{notes,papers,concepts,.schist}
# Add your first note
schist add --vault ~/vaults/research \
--title "First Note" \
--tags getting-started \
--body "Hello, knowledge graph."
# Search it
schist search --vault ~/vaults/research "knowledge"
# Get graph context (useful for agent session start)
schist context --vault ~/vaults/research
CLI Commands
| Command | Description |
|---|---|
schist add |
Create a new note |
schist link |
Add a connection between nodes |
schist search |
Full-text search |
schist query |
Raw SQL query |
schist build |
Generate static viewer data |
schist context |
Dump session context |
schist schema |
Print or validate schema |
MCP Server
The schist MCP server (@schist/mcp-server) is published separately on npm:
npm install -g @schist/mcp-server
Register it as a user-scope MCP server:
schist --vault /absolute/path/to/vault init --print-mcp-config --format claude --identity local
# then run the printed `claude mcp add ...` line
Claude Code stores user-scope MCP servers in ~/.claude.json (managed
by the CLI). On older Claude Code CLIs without mcp add,
--print-mcp-config also emits a commented JSON fallback — uncomment
the block and hand-merge it under the top-level mcpServers key in
~/.claude.json. Claude Desktop uses
~/Library/Application Support/Claude/claude_desktop_config.json
instead; the JSON shape is the same.
See the full README for architecture docs, hub & spoke setup, and MCP tool reference.
License
MIT
Release files for schist 0.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| schist-0.2.0.tar.gz | 81.7 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| schist-0.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 130.1 kB
Release files / schist-0.2.0.tar.gz
| Download URL | schist-0.2.0.tar.gz |
|---|---|
| Size | 81.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ea236d6d318a237e205e010322e9b097cd22d23ce8cec25eeb2d45584625e02f
|
|
BLAKE2b-256 checksum How to use checksums |
ef461d5e756766c2b6900105942d558349f78e2dde106f60ef87076ad6f0c9c2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 23, 2026.
Transparency logRelease files / schist-0.2.0-py3-none-any.whl
| Download URL | schist-0.2.0-py3-none-any.whl |
|---|---|
| Size | 48.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ef0890042cfaac44156e30eba87a1b9de907e8bc14298097e0c219c318145b29
|
|
BLAKE2b-256 checksum How to use checksums |
cf9e81fd6cee9b386bde5f9083cea7e0af8c25195510c9dc9c2ae370e53626d4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 23, 2026.
Transparency log