I
inite-ai/inite-brain-service
Open-source bitemporal knowledge graph — long-term memory for AI agents
View on GitHub ↗Link checked 2026-11-12 · HTTP 200 · opens the vendor's own site
Install & config
Remote endpoint (mcpServers - Claude Desktop / Cursor / Windsurf)
{
"mcpServers": {
"inite-ai-inite-brain-service": {
"url": "https://brain.inite.ai/mcp"
}
}
}Paste this into the mcpServers config of Claude Desktop or Cursor. The endpoint comes from public evidence; we do not install or host it. Official Registry record: this endpoint lists no request headers. That is not the same as key-free - the project docs decide.
VS Code (.vscode/mcp.json - the key is servers, remote needs type: http)
{
"servers": {
"inite-ai-inite-brain-service": {
"type": "http",
"url": "https://brain.inite.ai/mcp"
}
}
}VS Code differs from the other three: the top-level key is <code>servers</code> and a remote endpoint also needs <code>"type": "http"</code>. Paste into .vscode/mcp.json.
Claude Code (command line)
claude mcp add --transport http inite-ai-inite-brain-service https://brain.inite.ai/mcp
Claude Code does not read a config file; add the server with this command.
Install command from the repository
npm install @inite/brain
Parsed from the README we fetched on 2026-10-27; we have not executed it.
This is the install method the repository states, not an MCP client config, so no JSON is generated.
Key names differ by client: Clients & CLI
- Star count
- 43 ★ · inite-ai/inite-brain-service · read from the GitHub search API · (checked 2026-11-13 20:00:50)
- Source
- read directly from its GitHub page · type: open-source project
- Harvest history
- first seen 2026-10-27 · last seen 2026-11-14 · seen 20× · listed by 2 sources
- Score
- score 203 · 43 ★ · 2 sources · repo
- Install
npm install @inite/brain
FAQ (answers come from our records)
How do I install it?
The repository provides this install command:
npm install @inite/brain. It comes from the repository itself; we cannot guarantee it runs as-is in your client.Who is it for?
We filed it under these tags: 记忆增强. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository
inite-ai/inite-brain-service；first catalogued 2026-10-27；last seen 2026-11-14。There is no official certification or quality rating here — we record sources and dates only.INITE Brain
以下摘录自该仓库的 README（片段） · 在 GitHub 读完整 README →
Open-source memory for AI agents: a bitemporal knowledge graph with provenance, over MCP and REST.
Website ·
Quick start ·
Architecture ·
Domain Packs ·
Getting started ·
Docs ·
Agent guide
## Quick start
Needs Docker with Compose v2, openssl, and an OpenAI API key (the default
model configuration). Runs the released image (linux/amd64 and
linux/arm64) with SurrealDB; no clone, no build.
bash
: "${OPENAIAPIKEY:?export OPENAIAPIKEY first}"
mkdir inite-brain && cd inite-brain
curl -fsSLO https://raw.githubusercontent.com/inite-ai/inite-brain-service/main/docker-compose.quickstart.yml
BRAINKEY="brain$(openssl rand -hex 24)"
KEYHASH="$(printf %s "$BRAINKEY" | openssl dgst -sha256 -r | cut -d' ' -f1)"
cat > .env conversations · documents · facts"]
raw[("Source records documents · episodes · evidence")]
derive["Indexers and scene builders candidates · entity resolution · conflicts"]
memory[("Connected memory on SurrealDB facts + graph · scenes · beliefs")]
retrieve["Retrieval semantic + lexical · graph · multi-hop"]
answer["Synthesis + verification answer with citations or abstention"]
packs["Domain Packs vocabulary · memoryModel · tools"]
media["Evidence registration / upload scan hook · trusted processors"]
input --> raw
input --> derive
media --> raw
raw --> derive
derive --> memory
memory --> retrieve
raw --> retrieve
retrieve --> answer
packs -. "domain configuration" .-> derive
packs -. "capabilities and consent" .-> media
| Memory layer | What it preserves |
| Facts and entities | Typed claims, canonical entities, relationships, confidence, source attribution and temporal history. |
| Episodes | Source turns and conversation context that derived memory can point back to or be rebuilt from. |
| Scenes | Bounded events with gists, entities, state changes and source links. Optional gist embeddings and a scene retrieval lane make them searchable alongside other evidence. |
| Beliefs | Derived state with revision history and supporting scenes. Pack-projected state deltas can feed belief promotion. |
| Evidence | Assets, located fragments, processing runs and derived representations, with links to the memories they support. |
Rebuildable memory. Derived worlds can be rebuilt from retained episodes in
a staging version. Readers stay pinned to the previous world until promotion.
Scene maintenance can process dirty conversations on a schedule, with budgets,
leases and metrics; it can compose scenes and promote supported beliefs.
Configurable retrieval. Retrieval profiles select mechanisms for the corpus
and question. Semantic and lexical search, graph expansion, reranking, raw
passages, scene retrieval and belief retrieval are distinct capabilities. A
known entity can enter through graphretrieve; a question spanning
relationships can use searchmultihop.
Separate serving and background work. The NestJS service uses a
SurrealDB-backed job queue, leases and worker-thread offloads. Run the image as
one process or split PROCESSROLE=api|worker; see the
operations guide.
The code includes capabilities that are opt-in, not a promise that every
installation runs every layer. Scene construction, scene serving, belief
promotion, evidence upload/processing and pack projections have separate gates.
Website ·
Quick start ·
Architecture ·
Domain Packs ·
Getting started ·
Docs ·
Agent guide
## Quick start
Needs Docker with Compose v2, openssl, and an OpenAI API key (the default
model configuration). Runs the released image (linux/amd64 and
linux/arm64) with SurrealDB; no clone, no build.
bash
: "${OPENAIAPIKEY:?export OPENAIAPIKEY first}"
mkdir inite-brain && cd inite-brain
curl -fsSLO https://raw.githubusercontent.com/inite-ai/inite-brain-service/main/docker-compose.quickstart.yml
BRAINKEY="brain$(openssl rand -hex 24)"
KEYHASH="$(printf %s "$BRAINKEY" | openssl dgst -sha256 -r | cut -d' ' -f1)"
cat > .env conversations · documents · facts"]
raw[("Source records documents · episodes · evidence")]
derive["Indexers and scene builders candidates · entity resolution · conflicts"]
memory[("Connected memory on SurrealDB facts + graph · scenes · beliefs")]
retrieve["Retrieval semantic + lexical · graph · multi-hop"]
answer["Synthesis + verification answer with citations or abstention"]
packs["Domain Packs vocabulary · memoryModel · tools"]
media["Evidence registration / upload scan hook · trusted processors"]
input --> raw
input --> derive
media --> raw
raw --> derive
derive --> memory
memory --> retrieve
raw --> retrieve
retrieve --> answer
packs -. "domain configuration" .-> derive
packs -. "capabilities and consent" .-> media
| Memory layer | What it preserves |
| Facts and entities | Typed claims, canonical entities, relationships, confidence, source attribution and temporal history. |
| Episodes | Source turns and conversation context that derived memory can point back to or be rebuilt from. |
| Scenes | Bounded events with gists, entities, state changes and source links. Optional gist embeddings and a scene retrieval lane make them searchable alongside other evidence. |
| Beliefs | Derived state with revision history and supporting scenes. Pack-projected state deltas can feed belief promotion. |
| Evidence | Assets, located fragments, processing runs and derived representations, with links to the memories they support. |
Rebuildable memory. Derived worlds can be rebuilt from retained episodes in
a staging version. Readers stay pinned to the previous world until promotion.
Scene maintenance can process dirty conversations on a schedule, with budgets,
leases and metrics; it can compose scenes and promote supported beliefs.
Configurable retrieval. Retrieval profiles select mechanisms for the corpus
and question. Semantic and lexical search, graph expansion, reranking, raw
passages, scene retrieval and belief retrieval are distinct capabilities. A
known entity can enter through graphretrieve; a question spanning
relationships can use searchmultihop.
Separate serving and background work. The NestJS service uses a
SurrealDB-backed job queue, leases and worker-thread offloads. Run the image as
one process or split PROCESSROLE=api|worker; see the
operations guide.
The code includes capabilities that are opt-in, not a promise that every
installation runs every layer. Scene construction, scene serving, belief
promotion, evidence upload/processing and pack projections have separate gates.
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[](https://anclum.com/en/s/inite-ai-inite-brain-service/)
- Source
- github · https://github.com/inite-ai/inite-brain-service
- Browse by field
- Memory & context
- Traction
- 43 ★
- Listed by
- 2 independent sources
- added
- today
More like this
Filed under
Every tag opens the full list for that filter. Counts are the live catalogue figures.