mindgraph-mcp 0.14.9 → 0.16.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +3 -3
- package/dist/cli.js +1112 -205
- package/dist/index.js +600 -94
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -132,7 +132,7 @@ profile):
|
|
|
132
132
|
| `mindgraph_reason` | Claims with evidence, open questions, hypotheses, theories, anomalies |
|
|
133
133
|
| `mindgraph_commit` | Goals, projects, decisions, options, milestones, and dated decision-context linkage |
|
|
134
134
|
| `mindgraph_plan` | Plans, tasks, procedures, governance policies, risk assessments, executions |
|
|
135
|
-
| `mindgraph_retrieve` | Context retrieval with bounded graph expansion, search, min-cost traversal, document index |
|
|
135
|
+
| `mindgraph_retrieve` | Context retrieval with bounded graph expansion, search, min-cost traversal, document index. Since 0.16.0, read results return as a rendered, token-bounded text block (labels, uids, summaries, epistemic status tags, relationships) — pass `format: "json"` on any call for the raw server response |
|
|
136
136
|
| `mindgraph_ingest` | Chunk / document / session ingestion with LLM-powered extraction |
|
|
137
137
|
| `mindgraph_synthesize` | Project-scoped cross-document synthesis — mine signals, spawn Article-generation jobs |
|
|
138
138
|
| `mindgraph_ontology` | Operational Ontology (Layer 7) — typed domain objects, NL queries with provenance, extraction proposal review (approve/reject), object linking |
|
|
@@ -189,7 +189,7 @@ teammates one logical agent, which claims each other's work).
|
|
|
189
189
|
| `MINDGRAPH_BASE_URL` | `https://api.mindgraph.cloud` | Override for self-hosted deployments |
|
|
190
190
|
| `MINDGRAPH_PROFILE` | `general` | `coding` exposes `mindgraph_code`/`mindgraph_sync` and the work composites |
|
|
191
191
|
| `MINDGRAPH_HARNESS` | `generic` | `claude-code` / `codex` — adapter selection and provenance |
|
|
192
|
-
| `MINDGRAPH_AGENT_ID` |
|
|
192
|
+
| `MINDGRAPH_AGENT_ID` | *(stable per-user id)* | Agent identity stamped on every write and used for durable-work leases. Defaults to a stable `u-<hash>` derived from user@host, shared by the hooks, the registration, and the serve path — set explicitly for cross-device continuity or per-teammate identities |
|
|
193
193
|
| `MINDGRAPH_ORG_ID` | *(unset)* | Pin operations to a specific organization when a key has access to more than one |
|
|
194
194
|
| `MINDGRAPH_CODEGRAPH_BIN` | *(auto)* | Explicit path to the codegraph binary (PATH and `~/.local/bin` are probed) |
|
|
195
195
|
|
|
@@ -202,7 +202,7 @@ Once installed, start asking Claude about your knowledge graph naturally:
|
|
|
202
202
|
> "Ingest this PDF and extract the main claims."
|
|
203
203
|
> "Find entities mentioned across multiple project documents, then spin up a synthesis."
|
|
204
204
|
|
|
205
|
-
The server auto-injects
|
|
205
|
+
The server auto-injects your agent identity on every write so you always know which nodes came from your MCP sessions — the same identity the session hooks use for durable-work leases, so work claimed in one harness resumes in the other.
|
|
206
206
|
|
|
207
207
|
## Architecture
|
|
208
208
|
|