INITE Brain
Long-term memory for AI agents: a bitemporal knowledge graph with cited answers.
Connect it
Settings → Connectors → Add custom connector
URL: https://brain.inite.ai/mcpSettings → Apps & Connectors → Advanced → Developer mode
Create connector with URL: https://brain.inite.ai/mcp{
"mcpServers": {
"inite-brain-service": {
"url": "https://brain.inite.ai/mcp"
}
}
}claude mcp add --transport http inite-brain-service https://brain.inite.ai/mcp{
"servers": {
"inite-brain-service": {
"type": "http",
"url": "https://brain.inite.ai/mcp"
}
}
}30 tools, verified live
about_brainread-onlyWhat this server is and what it can do, before you connect. Reads nothing and stores nothing.
how_to_connectread-onlyThe two ways to authenticate, and what each is for. Reads nothing and stores nothing.
search_knowledgeread-onlySemantic search over the company knowledge graph. Returns entities with their top facts and external references back to the originating verticals. Apply asOf for historical "what was true on X" queries (valid time: a fact brain learned after X still shows). Embedding model on this tenant: set per workspace.
search_multi_hopread-onlyPlanner-LLM decomposes the query into ⤠maxHops anchored sub-queries; later hops are anchored to the running entity set so the engine never spends compute on candidates already disqualified. Built for questions that combine evidence across turns / sessions, or that require reasoning over multiple entities ("tenants who complained in April AND upgraded after"). Set synthesize=true to get a ground
graph_retrieveread-onlyResolves the named entities by canonical name, walks their 1-hop neighbourhood over knowledge_edge, and returns facts across seeds ⪠neighbours, optionally filtered by predicate hints. Works from entities named up front and returns what the graph holds around them ("who runs engineering at Acme" â the answer lives on a neighbour, not on Acme itself). Seeds score 1.0, neighbours 0.7; soft-fails
synthesizeread-onlyRuns hybrid search then feeds the retrieved facts to a generator LLM that produces a citation-bearing answer (each claim ends with [factId]); a verifier LLM then judges whether every claim is supported. Three guardrail modes: strict (default) returns null on partial / unsupported / verifier outage (fail-closed); lenient returns the answer alongside the verifier verdict; off skips the verifier. Ret
memory_diffread-onlyReturns everything brain learned, unlearned, or replaced between two ISO 8601 cursors [from, to). createdFacts = new active facts; retractedFacts = facts marked retracted in-window with no successor; changedFacts = facts that were superseded by another (carries before+after); newEntities = entities created in-window; forgottenEntities = GDPR-erased tombstones; lapsedExpectations = temporary states
get_entity_profileread-onlyFull profile of one entity: canonical name, type, externalRefs (cross-vertical ids), and active facts. externalRefs point back to the originating vertical, where fresh state can be rehydrated via @inite/api-kit.
get_entity_timelineread-onlyChronological audit of all facts brain has learned about this entity, including retracted ones. Useful for "what did we know when" investigations.
summarize_entityread-onlyReturns a short one-line briefing about the entity â name, type, the most-confident active facts, external refs â suitable for dropping into an LLM context window. Caches in-process (per companyId / entityId / asOf / styleHint) so a hot entity touched across many turns doesn't reload the profile. styleHint='neutral' | 'sales' | 'support' are template-rendered (no LLM call). styleHint='client_l
get_competing_factsread-onlyReturns facts in COMPETING status â those the conflict resolver couldn't auto-supersede because two same-predicate bitemporal facts overlap in valid-time and are too cosine-close within margin. Grouped by (entityId, predicate); 2-fact groups are pairs the resolver left for adjudication, 3+-fact groups are multi-way disagreements escalated for human review. Answers "is this entity already conflic
detect_contradictionread-onlyDry-run preflight against fn::resolve_fact. Answers "if I were to record this fact right now, what would the resolver decide?" without writing to the database. wouldOutcome â {INSERTED, SUPERSEDED, COMPETING, REJECTED}; reasoning explains which rule fired (semantics class, score gap vs margin, cosine threshold, etc); opposingFacts lists the same-predicate priors the resolver would have weighed a
get_factread-onlyRead a single fact as stored â predicate (aspect), object (statement), confidence, validity window, source attribution (vertical / recorder / conversationId), and lifecycle state. Retracted facts still resolve (retracted: true) â "why did I stop remembering this" is part of the trust story; only visibility fences turn into not-found. groundingStatus (grounded | ungrounded) appears on facts sta
get_fact_provenanceread-onlyReturn the grounding provenance behind one fact: the verbatim conversation turns it was derived from (episodes, chronological, with char-span quotes when the deriver stamped them). When the server runs with the recursive-closure flag the response additionally carries derivedFacts + closure (the transitive derivedFrom support graph); a plain deployment returns episodes only â the response is a pa
find_related_entitiesread-onlyGet entities connected to the given one via the knowledge graph.
match_procedureread-onlyCosine-matches procedural memory (curated 'how to' patterns the operator recorded) against a free-text context query. Returns top-K procedures sorted by similarity DESC then priority ASC. Surfaces the behaviour rules that apply to a context â e.g. "user asks about pricing" â "mention they're on platinum tier; they get 20% off". Procedural memory is the third tier alongside facts (semantic) and
list_proceduresread-onlyPaginated listing of procedural memory for admin/review UIs. Sorted by priority ASC, createdAt DESC. Set includeRetired=true to see soft-deleted rows.
search_communitiesread-onlyCosine-matches the query against topic-community summaries â the coarse retrieval scope. A community is a cluster of related entities (label propagation over the entity graph) with one rolled-up summary. Suited to broad questions ("what do we know about X domain"): it returns an overview of a domain rather than individual facts. Communities are (re)built off-hours by the dreams loop; an empty re
list_communitiesread-onlyPaginated listing of topic communities, largest first. Each row carries a label, a rolled-up summary, and the member count. Gives the knowledge map at a glance.
find_entity_communitiesread-onlyReturns the topic communities a given entity is a member of. Places an entity in its broader context â which clusters / themes it participates in â and leads from one entity to the wider neighbourhood the cluster summarises.
whyread-onlyReturn the design decisions, rationale, invariants and gotchas recorded against a code anchor â the non-derivable engineering "why" a parser cannot recover from source. The anchor is a SCIP-style symbol string ("pkg/namespace/symbol") or a file path ("repo/path/file.ts"). Pass asOf to recall what was known at a past instant (bitemporal). Returns found:0 with empty memory when nothing is recorded
recall_decisionsread-onlyFind recorded design decisions / rationale / invariants / gotchas by NL topic ("why do we resolve facts through one gateway?"), across ALL code anchors â a semantic search over code-memory, rather than one known anchor. Returns matches with their code anchor + kind, ranked by relevance.
get_source_reputationread-onlyReturn everything brain knows ABOUT a source (not its facts): the operator-declared identity (type, authLevel â authority in conflict resolution), the learned per-domain agreement rates (domain = predicate; null domain = the global blended rate; rates need >=8 samples before the resolver trusts them over the neutral 0.5), and the reputation-over-time history. sourceKey is `vertical:recorder` (re
workspace_statusread-onlyThe tenant this credential writes to (companyId, its display name, whether it is a personal workspace), what is already in its memory (entities, active facts, facts recorded in the last 7 days), how many Domain Packs are installed, for a user-bound connection who the user is in this memory (`user.name` â the name the memory has learned from them, null until it has), and `nextSteps` â the setup
record_factInsert a fact about an entity. Triggers brain conflict resolution (INSERTED / SUPERSEDED / COMPETING / REJECTED). Most facts come from event ingestion; this records one directly.
link_entitiesInsert an edge between two entities. `kind` is the edge type â `identity_of` merges the `from` entity into `to` (cross-vertical identity reconciliation), other typed edges (`paid_for`, `mentioned_in`, `worked_with`, â¦) are surfaced in related-entity reads and contribute to PPR / SubgraphRAG context. Most edges come from event ingestion; this inserts one directly. identity_of rejects a request
retract_factcan modifyMark a fact as no longer believed. Cascades to facts derived from this one. Does not delete; the row remains for audit.
record_procedureRecord a 'how to' pattern that is surfaced when a similar context appears later. trigger = the context phrase the rule should match against (e.g. "user asks about pricing"); action = the behaviour to apply (e.g. "mention they're on platinum tier; they get 20% off"). priority orders ties when multiple procedures match the same context (lower is higher priority; default 100). decayHalfLifeDays is a
retire_procedurecan modifyMark a procedural memory row as retired (sets retiredAt). A retired procedure is no longer matched or listed by default. For a rule that no longer applies â distinct from a hard delete because the row stays for audit.
record_decisionCapture the non-derivable engineering "why" about a code location: a design decision, its rationale, an invariant that must hold, or a gotcha. Anchored to a SCIP-style symbol or file path (NOT line numbers â survives edits). Stored as a bitemporal typed fact: re-recording a `decided` / `invariant` for the same anchor SUPERSEDES the prior one (decision evolution over time), while `because` / `got
Change history
Alternatives in Developer Tools
Compare →KLKorean Law MCPA
Korean law: statutes, precedents, ordinances, treaties and citation verification (법제처 API).
EMemailmdA
Render markdown into email-safe HTML, lint drafts for deliverability problems, and preview emails.
SESemioticA
Verified React chart generation: select, validate, repair, render, and inspect charts through MCP.
RRReactive ResumeA
Free open-source resume builder with remote MCP tools for resumes and job applications.
PAPg AiguideA
Comprehensive PostgreSQL documentation and best practices, including ecosystem tools
COContrastAPIA
55 tools, 7 Resources, Sigma rules, email SPF/DMARC, MITRE, CVE/KEV, risk_score. No key.