knowmind 0.3.6 → 0.3.7

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 CHANGED
@@ -1,207 +1,207 @@
1
- # knowmind
2
-
3
-
4
- <!-- mcp-name: io.github.Schubeler-Consulting/knowmind -->
5
-
6
- **Persistent memory for your AI tools.** Store something once, and it is available in Claude Code, Cursor, and any other MCP client that runs a local (stdio) server — as a typed knowledge graph with provenance, confidence, and a bitemporal history for every fact. Hosted in Germany (Hetzner, Nuremberg data center); the CLI and MCP server in this repository are Apache-2.0.
7
-
8
- **The free tier is permanently free and requires no payment details.** The API, CLI, and MCP server are included in every tier.
9
-
10
- [![npm](https://img.shields.io/npm/v/knowmind)](https://www.npmjs.com/package/knowmind) · [knowmind.de](https://knowmind.de)
11
-
12
- ## Connect your AI tool in three steps
13
-
14
- 1. Create a free account at [knowmind.de](https://knowmind.de) and generate an access token: Dashboard → API tokens.
15
- 2. Store the token locally:
16
-
17
- ```
18
- npx -y knowmind login --token kmt_xxxxxxxx
19
- ```
20
-
21
- 3. Wire up your client:
22
-
23
- **Claude Code** (one command)
24
- ```
25
- claude mcp add knowmind --env KNOWMIND_TOKEN=kmt_xxx -- npx -y knowmind mcp
26
- ```
27
-
28
- **Cursor** (`~/.cursor/mcp.json`) — also works for Claude Desktop, Windsurf, Cline, Continue, Goose, and Zed with their respective config files:
29
- ```json
30
- {
31
- "mcpServers": {
32
- "knowmind": {
33
- "command": "npx",
34
- "args": ["-y", "knowmind", "mcp"],
35
- "env": { "KNOWMIND_TOKEN": "kmt_xxx" }
36
- }
37
- }
38
- }
39
- ```
40
-
41
- **Any other MCP client**: knowmind is a standard MCP server over stdio (`npx -y knowmind mcp`). On Windows, if `npx` does not start directly, use `"command": "cmd"`, `"args": ["/c", "npx", "-y", "knowmind", "mcp"]`.
42
-
43
- `npx -y knowmind install <ide>` writes this configuration for you (e.g. `claude`, `cursor`, `vscode`), and `npx -y knowmind init` sets up automatic memory hygiene — recall before each task, store after each meaningful change — for clients with a hook or rule mechanism (Claude Code, Cursor).
44
-
45
- ## How knowmind stores facts
46
-
47
- - **Bitemporal history.** Every fact carries two time axes: when it was true and when it was recorded. Corrections never overwrite the original; the old statement stays queryable with the date it stopped being valid, so you can reconstruct what the system knew on any given day.
48
- - **Provenance and confidence per fact.** New facts require a confidence level and keep a link to their source. Older facts without a confidence level are marked as such.
49
- - **Typed knowledge graph.** Entities and relations use a restricted set of edge types; catch-all relations are rejected at write time.
50
- - **Operated in the EU, isolated per tenant.** The service runs on Hetzner in Nuremberg, Germany, with tenant isolation, a public data processing agreement, and a subprocessor list at [knowmind.de/legal/avv](https://knowmind.de/legal/avv). Access logs are hash-chained and externally timestamped (RFC 3161).
51
-
52
- knowmind is a hosted service; there is no self-hosted community edition. If you need self-hosting, one of the projects below will serve you better. knowmind is built for the people and teams that need an operated memory service with an audit trail in the EU.
53
-
54
- ## Pricing
55
-
56
- | Tier | Price | For whom |
57
- |---|---|---|
58
- | Free | €0 | individuals and evaluation |
59
- | Pro | €15/month or €150/year | individual professionals |
60
- | Team | €99/month | teams with shared memory |
61
- | Business | €349/month | larger teams |
62
- | Enterprise | from €1,000/month | organizations with on-premise requirements |
63
-
64
- The free tier includes 2,500 memories, 1 user, and a 30-day access log.
65
-
66
- How that compares (vendor pricing pages, checked 2026-09-05):
67
-
68
- | Product | Free tier | First paid tier | Self-hosting |
69
- |---|---|---|---|
70
- | knowmind | 2,500 memories | €15/month | no (Enterprise on-premise option) |
71
- | Mem0 | 10,000 entries, 1,000 retrievals/month | $19/month | yes (Apache-2.0) |
72
- | Zep | 10,000 credits/month | $125/month | Graphiti open source; Zep as BYOC |
73
- | cognee | 1M tokens, 1 workspace | $2.50 per 1M tokens | yes |
74
- | Letta | limited agents, own keys | $20/month | yes (per vendor) |
75
- | Supermemory | ~$5 usage included | $19/month | from Scale tier |
76
-
77
- Details and current prices: [knowmind.de/pricing](https://knowmind.de/pricing).
78
-
79
- ## Commands
80
-
81
- ```
82
- npx -y knowmind search "Where does the staging deploy run?"
83
- npx -y knowmind upload notes.md --title "Meeting notes 2026-05-12"
84
- npx -y knowmind stats
85
- npx -y knowmind health
86
- npx -y knowmind status --line # one-line status for your AI tool's statusline
87
- ```
88
-
89
- ## Available Tools
90
-
91
- Thirteen tools over MCP. Every one works against your own workspace; the server
92
- never sees another tenant's data.
93
-
94
- ### Reading
95
-
96
- **`knowmind_recall`** — Search your memory and get the passages that answer a
97
- question, ranked. Combines keyword search, vector similarity and the knowledge
98
- graph, then reranks with a cross-encoder.
99
- `query` (string, required) · `k` (integer, default 5, max 20) · `hops` (integer,
100
- default 2 — how far to follow graph edges from a hit)
101
- *Usage:* your AI tool asks "Which database does the billing service use?" before
102
- answering, instead of guessing.
103
- *Errors:* returns an empty result set when nothing matches — never an invented
104
- answer.
105
-
106
- **`knowmind_recall_at_time`** — The same search, but as your memory stood on a
107
- given date. Facts superseded after that date are excluded; facts that were valid
108
- then are returned even if they are no longer true.
109
- `query` (string, required) · `as_of` (ISO date or timestamp, required in
110
- practice) · `k` (integer, default 5)
111
- *Usage:* "What was our pricing in March?" — answers from the state of that day,
112
- not today's.
113
- *Difference from `knowmind_recall`:* use `recall` for what is true now, and
114
- `recall_at_time` for what was true then. Asking `recall` about the past returns
115
- today's facts.
116
-
117
- **`knowmind_list_recent`** — The most recently added entries, newest first.
118
- `k` (integer, default 10)
119
- *Usage:* a quick look at what landed in memory during this session.
120
-
121
- **`knowmind_list_relations`** — All typed edges attached to one entry, in both
122
- directions.
123
- `memory_id` (string, required)
124
- *Usage:* "What does this contract connect to?" before changing or superseding it.
125
- *Errors:* unknown id returns an error, not an empty list.
126
-
127
- **`knowmind_schema`** — The entity classes and relation types this workspace
128
- accepts. No parameters.
129
- *Usage:* call it before `knowmind_entity` or `knowmind_link` to use a type the
130
- server will accept, rather than inventing one.
131
-
132
- **`knowmind_stats`** — Size of the corpus: documents, chunks, entities, edges.
133
- No parameters.
134
-
135
- **`knowmind_health`** — Whether the service and its stores are reachable. No
136
- parameters.
137
- *Usage:* a status line, or a check before a long ingest.
138
-
139
- ### Writing
140
-
141
- **`knowmind_store_memory`** — Store a short fact, decision or note. Stays as one
142
- unit; it is not split.
143
- `content` (string, required) · `title` (string) · `memory_type` (string, e.g.
144
- `semantic`, `episodic`) · `tags` (array of strings) · `source` (string) ·
145
- `domain` (string) · `relations` (array — edges to create along with the entry)
146
- *Usage:* "We decided to keep the monolith until Q3" after a meeting.
147
- *Errors:* rejected with 422 when the text contains what looks like a password or
148
- an access key. Store a pointer instead, not the secret.
149
-
150
- **`knowmind_upload_document`** — Store a longer text as a document. It is split
151
- into passages, embedded, and becomes searchable through `knowmind_recall`.
152
- `content` (string, required) · `title` (string) · `source` (string) ·
153
- `relations` (array)
154
- *Usage:* meeting minutes, a specification, a handbook chapter.
155
- *Difference from `knowmind_store_memory`:* one sentence you want back verbatim is
156
- a memory; a page you want searched is a document. A long text stored as a memory
157
- is retrieved as one block, which crowds out other results.
158
-
159
- **`knowmind_update_fact`** — Supersede a fact that has changed. The old version
160
- keeps its validity window and stays auditable; nothing is deleted.
161
- `target_id` (string, required) · `new_title` (string, required) · `new_content`
162
- (string, required) · `update_reason` (string)
163
- *Usage:* a price, a deadline or a responsibility changed. Never overwrite —
164
- supersede, so "what did we believe in July" stays answerable.
165
- *Errors:* unknown `target_id` is rejected.
166
-
167
- **`knowmind_entity`** — Create or update a typed entity (a person, a company, a
168
- product) with aliases.
169
- `name` (string, required) · `entity_class` (string, required — see
170
- `knowmind_schema`) · `description` (string) · `aliases` (array of strings)
171
- *Usage:* give "ACME Ltd." its aliases so a question about "ACME" finds it.
172
- *Errors:* a class outside the schema is rejected.
173
-
174
- **`knowmind_link`** — Create a typed edge between two entries, with a confidence
175
- value.
176
- `from_id` (string, required) · `to_id` (string, required) · `rel_type` (string,
177
- required — see `knowmind_schema`) · `confidence` (number 0–1)
178
- *Usage:* connect a contract to the client it belongs to. The inverse edge is
179
- created for you.
180
-
181
- **`knowmind_unlink`** — Remove a typed edge.
182
- `from_id`, `to_id`, `rel_type` (all required)
183
- *Usage:* an edge created in error. The entries themselves stay.
184
-
185
- ### On deleting
186
-
187
- There is no delete tool, and that is deliberate. Facts are superseded
188
- (`knowmind_update_fact`), edges are removed (`knowmind_unlink`), and the history
189
- stays auditable. Deleting an entire workspace including its data is a
190
- self-service action in the web interface at
191
- [knowmind.de](https://knowmind.de) — it is not something an agent should be able
192
- to do by calling a tool.
193
-
194
- ### Discovery
195
-
196
- `GET https://knowmind.de/api/mcp/v1` returns name, version, protocol version and
197
- the full tool list with input schemas — without a token. Directory crawlers and
198
- inspectors can read the complete surface anonymously; only `tools/call` requires
199
- a key.
200
-
201
- ## Links
202
-
203
- [Documentation](https://knowmind.de/docs) · [Pricing](https://knowmind.de/pricing) · [Data processing agreement](https://knowmind.de/legal/avv) · [Privacy](https://knowmind.de/legal/datenschutz)
204
-
205
- ---
206
-
207
- Die deutsche Fassung steht in [README.de.md](README.de.md).
1
+ # knowmind
2
+
3
+
4
+ <!-- mcp-name: io.github.Schubeler-Consulting/knowmind -->
5
+
6
+ **Persistent memory for your AI tools.** Store something once, and it is available in Claude Code, Cursor, and any other MCP client that runs a local (stdio) server — as a typed knowledge graph with provenance, confidence, and a bitemporal history for every fact. Hosted in Germany (Hetzner, Nuremberg data center); the CLI and MCP server in this repository are Apache-2.0.
7
+
8
+ **The free tier is permanently free and requires no payment details.** The API, CLI, and MCP server are included in every tier.
9
+
10
+ [![npm](https://img.shields.io/npm/v/knowmind)](https://www.npmjs.com/package/knowmind) · [knowmind.de](https://knowmind.de)
11
+
12
+ ## Connect your AI tool in three steps
13
+
14
+ 1. Create a free account at [knowmind.de](https://knowmind.de) and generate an access token: Dashboard → API tokens.
15
+ 2. Store the token locally:
16
+
17
+ ```
18
+ npx -y knowmind login --token kmt_xxxxxxxx
19
+ ```
20
+
21
+ 3. Wire up your client:
22
+
23
+ **Claude Code** (one command)
24
+ ```
25
+ claude mcp add knowmind --env KNOWMIND_TOKEN=kmt_xxx -- npx -y knowmind mcp
26
+ ```
27
+
28
+ **Cursor** (`~/.cursor/mcp.json`) — also works for Claude Desktop, Windsurf, Cline, Continue, Goose, and Zed with their respective config files:
29
+ ```json
30
+ {
31
+ "mcpServers": {
32
+ "knowmind": {
33
+ "command": "npx",
34
+ "args": ["-y", "knowmind", "mcp"],
35
+ "env": { "KNOWMIND_TOKEN": "kmt_xxx" }
36
+ }
37
+ }
38
+ }
39
+ ```
40
+
41
+ **Any other MCP client**: knowmind is a standard MCP server over stdio (`npx -y knowmind mcp`). On Windows, if `npx` does not start directly, use `"command": "cmd"`, `"args": ["/c", "npx", "-y", "knowmind", "mcp"]`.
42
+
43
+ `npx -y knowmind install <ide>` writes this configuration for you (e.g. `claude`, `cursor`, `vscode`), and `npx -y knowmind init` sets up automatic memory hygiene — recall before each task, store after each meaningful change — for clients with a hook or rule mechanism (Claude Code, Cursor).
44
+
45
+ ## How knowmind stores facts
46
+
47
+ - **Bitemporal history.** Every fact carries two time axes: when it was true and when it was recorded. Corrections never overwrite the original; the old statement stays queryable with the date it stopped being valid, so you can reconstruct what the system knew on any given day.
48
+ - **Provenance and confidence per fact.** New facts require a confidence level and keep a link to their source. Older facts without a confidence level are marked as such.
49
+ - **Typed knowledge graph.** Entities and relations use a restricted set of edge types; catch-all relations are rejected at write time.
50
+ - **Operated in the EU, isolated per tenant.** The service runs on Hetzner in Nuremberg, Germany, with tenant isolation, a public data processing agreement, and a subprocessor list at [knowmind.de/legal/avv](https://knowmind.de/legal/avv). Access logs are hash-chained and externally timestamped (RFC 3161).
51
+
52
+ knowmind is a hosted service; there is no self-hosted community edition. If you need self-hosting, one of the projects below will serve you better. knowmind is built for the people and teams that need an operated memory service with an audit trail in the EU.
53
+
54
+ ## Pricing
55
+
56
+ | Tier | Price | For whom |
57
+ |---|---|---|
58
+ | Free | €0 | individuals and evaluation |
59
+ | Pro | €15/month or €150/year | individual professionals |
60
+ | Team | €99/month | teams with shared memory |
61
+ | Business | €349/month | larger teams |
62
+ | Enterprise | from €1,000/month | organizations with on-premise requirements |
63
+
64
+ The free tier includes 2,500 memories, 1 user, and a 30-day access log.
65
+
66
+ How that compares (vendor pricing pages, checked 2026-09-05):
67
+
68
+ | Product | Free tier | First paid tier | Self-hosting |
69
+ |---|---|---|---|
70
+ | knowmind | 2,500 memories | €15/month | no (Enterprise on-premise option) |
71
+ | Mem0 | 10,000 entries, 1,000 retrievals/month | $19/month | yes (Apache-2.0) |
72
+ | Zep | 10,000 credits/month | $125/month | Graphiti open source; Zep as BYOC |
73
+ | cognee | 1M tokens, 1 workspace | $2.50 per 1M tokens | yes |
74
+ | Letta | limited agents, own keys | $20/month | yes (per vendor) |
75
+ | Supermemory | ~$5 usage included | $19/month | from Scale tier |
76
+
77
+ Details and current prices: [knowmind.de/pricing](https://knowmind.de/pricing).
78
+
79
+ ## Commands
80
+
81
+ ```
82
+ npx -y knowmind search "Where does the staging deploy run?"
83
+ npx -y knowmind upload notes.md --title "Meeting notes 2026-05-12"
84
+ npx -y knowmind stats
85
+ npx -y knowmind health
86
+ npx -y knowmind status --line # one-line status for your AI tool's statusline
87
+ ```
88
+
89
+ ## Available Tools
90
+
91
+ Thirteen tools over MCP. Every one works against your own workspace; the server
92
+ never sees another tenant's data.
93
+
94
+ ### Reading
95
+
96
+ **`knowmind_recall`** — Search your memory and get the passages that answer a
97
+ question, ranked. Combines keyword search, vector similarity and the knowledge
98
+ graph, then reranks with a cross-encoder.
99
+ `query` (string, required) · `k` (integer, default 5, max 20) · `hops` (integer,
100
+ default 2 — how far to follow graph edges from a hit)
101
+ *Usage:* your AI tool asks "Which database does the billing service use?" before
102
+ answering, instead of guessing.
103
+ *Errors:* returns an empty result set when nothing matches — never an invented
104
+ answer.
105
+
106
+ **`knowmind_recall_at_time`** — The same search, but as your memory stood on a
107
+ given date. Facts superseded after that date are excluded; facts that were valid
108
+ then are returned even if they are no longer true.
109
+ `query` (string, required) · `as_of` (ISO date or timestamp, required in
110
+ practice) · `k` (integer, default 5)
111
+ *Usage:* "What was our pricing in March?" — answers from the state of that day,
112
+ not today's.
113
+ *Difference from `knowmind_recall`:* use `recall` for what is true now, and
114
+ `recall_at_time` for what was true then. Asking `recall` about the past returns
115
+ today's facts.
116
+
117
+ **`knowmind_list_recent`** — The most recently added entries, newest first.
118
+ `k` (integer, default 10)
119
+ *Usage:* a quick look at what landed in memory during this session.
120
+
121
+ **`knowmind_list_relations`** — All typed edges attached to one entry, in both
122
+ directions.
123
+ `memory_id` (string, required)
124
+ *Usage:* "What does this contract connect to?" before changing or superseding it.
125
+ *Errors:* unknown id returns an error, not an empty list.
126
+
127
+ **`knowmind_schema`** — The entity classes and relation types this workspace
128
+ accepts. No parameters.
129
+ *Usage:* call it before `knowmind_entity` or `knowmind_link` to use a type the
130
+ server will accept, rather than inventing one.
131
+
132
+ **`knowmind_stats`** — Size of the corpus: documents, chunks, entities, edges.
133
+ No parameters.
134
+
135
+ **`knowmind_health`** — Whether the service and its stores are reachable. No
136
+ parameters.
137
+ *Usage:* a status line, or a check before a long ingest.
138
+
139
+ ### Writing
140
+
141
+ **`knowmind_store_memory`** — Store a short fact, decision or note. Stays as one
142
+ unit; it is not split.
143
+ `content` (string, required) · `title` (string) · `memory_type` (string, e.g.
144
+ `semantic`, `episodic`) · `tags` (array of strings) · `source` (string) ·
145
+ `domain` (string) · `relations` (array — edges to create along with the entry)
146
+ *Usage:* "We decided to keep the monolith until Q3" after a meeting.
147
+ *Errors:* rejected with 422 when the text contains what looks like a password or
148
+ an access key. Store a pointer instead, not the secret.
149
+
150
+ **`knowmind_upload_document`** — Store a longer text as a document. It is split
151
+ into passages, embedded, and becomes searchable through `knowmind_recall`.
152
+ `content` (string, required) · `title` (string) · `source` (string) ·
153
+ `relations` (array)
154
+ *Usage:* meeting minutes, a specification, a handbook chapter.
155
+ *Difference from `knowmind_store_memory`:* one sentence you want back verbatim is
156
+ a memory; a page you want searched is a document. A long text stored as a memory
157
+ is retrieved as one block, which crowds out other results.
158
+
159
+ **`knowmind_update_fact`** — Supersede a fact that has changed. The old version
160
+ keeps its validity window and stays auditable; nothing is deleted.
161
+ `target_id` (string, required) · `new_title` (string, required) · `new_content`
162
+ (string, required) · `update_reason` (string)
163
+ *Usage:* a price, a deadline or a responsibility changed. Never overwrite —
164
+ supersede, so "what did we believe in July" stays answerable.
165
+ *Errors:* unknown `target_id` is rejected.
166
+
167
+ **`knowmind_entity`** — Create or update a typed entity (a person, a company, a
168
+ product) with aliases.
169
+ `name` (string, required) · `entity_class` (string, required — see
170
+ `knowmind_schema`) · `description` (string) · `aliases` (array of strings)
171
+ *Usage:* give "ACME Ltd." its aliases so a question about "ACME" finds it.
172
+ *Errors:* a class outside the schema is rejected.
173
+
174
+ **`knowmind_link`** — Create a typed edge between two entries, with a confidence
175
+ value.
176
+ `from_id` (string, required) · `to_id` (string, required) · `rel_type` (string,
177
+ required — see `knowmind_schema`) · `confidence` (number 0–1)
178
+ *Usage:* connect a contract to the client it belongs to. The inverse edge is
179
+ created for you.
180
+
181
+ **`knowmind_unlink`** — Remove a typed edge.
182
+ `from_id`, `to_id`, `rel_type` (all required)
183
+ *Usage:* an edge created in error. The entries themselves stay.
184
+
185
+ ### On deleting
186
+
187
+ There is no delete tool, and that is deliberate. Facts are superseded
188
+ (`knowmind_update_fact`), edges are removed (`knowmind_unlink`), and the history
189
+ stays auditable. Deleting an entire workspace including its data is a
190
+ self-service action in the web interface at
191
+ [knowmind.de](https://knowmind.de) — it is not something an agent should be able
192
+ to do by calling a tool.
193
+
194
+ ### Discovery
195
+
196
+ `GET https://knowmind.de/api/mcp/v1` returns name, version, protocol version and
197
+ the full tool list with input schemas — without a token. Directory crawlers and
198
+ inspectors can read the complete surface anonymously; only `tools/call` requires
199
+ a key.
200
+
201
+ ## Links
202
+
203
+ [Documentation](https://knowmind.de/docs) · [Pricing](https://knowmind.de/pricing) · [Data processing agreement](https://knowmind.de/legal/avv) · [Privacy](https://knowmind.de/legal/datenschutz)
204
+
205
+ ---
206
+
207
+ Die deutsche Fassung steht in [README.de.md](README.de.md).
package/package.json CHANGED
@@ -1,63 +1,63 @@
1
- {
2
- "name": "knowmind",
3
- "version": "0.3.6",
4
- "mcpName": "io.github.Schubeler-Consulting/knowmind",
5
- "description": "Knowmind — das Agentengehirn aus Deutschland: CLI + MCP-Server (Langzeitgedächtnis & Wissensgraph für Ihre KI, Server in Deutschland).",
6
- "type": "module",
7
- "license": "Apache-2.0",
8
- "homepage": "https://knowmind.de",
9
- "repository": {
10
- "type": "git",
11
- "url": "git+https://github.com/Schubeler-Consulting/knowmind.git"
12
- },
13
- "bugs": {
14
- "url": "https://knowmind.de/support",
15
- "email": "info@schuebeler-consulting.de"
16
- },
17
- "author": {
18
- "name": "Knowmind",
19
- "email": "info@schuebeler-consulting.de",
20
- "url": "https://knowmind.de"
21
- },
22
- "engines": {
23
- "node": ">=20"
24
- },
25
- "bin": {
26
- "knowmind": "bin/knowmind.js"
27
- },
28
- "files": [
29
- "bin",
30
- "src",
31
- "!src/*.test.js",
32
- "README.md",
33
- "CHANGELOG.md",
34
- "LICENSE",
35
- "scripts"
36
- ],
37
- "scripts": {
38
- "test": "node --test src/*.test.js",
39
- "tools:abgleich": "node scripts/tools-abgleich.mjs"
40
- },
41
- "dependencies": {
42
- "@huggingface/transformers": "^3.5.0"
43
- },
44
- "overrides": {
45
- "global-agent": "^4.1.3"
46
- },
47
- "keywords": [
48
- "knowmind",
49
- "mcp",
50
- "model-context-protocol",
51
- "knowledge-graph",
52
- "recall",
53
- "memory",
54
- "rag",
55
- "claude",
56
- "openai",
57
- "anthropic",
58
- "ai"
59
- ],
60
- "publishConfig": {
61
- "access": "public"
62
- }
63
- }
1
+ {
2
+ "name": "knowmind",
3
+ "version": "0.3.7",
4
+ "mcpName": "io.github.Schubeler-Consulting/knowmind",
5
+ "description": "Knowmind — das Agentengehirn aus Deutschland: CLI + MCP-Server (Langzeitgedächtnis & Wissensgraph für Ihre KI, Server in Deutschland).",
6
+ "type": "module",
7
+ "license": "Apache-2.0",
8
+ "homepage": "https://knowmind.de",
9
+ "repository": {
10
+ "type": "git",
11
+ "url": "git+https://github.com/Schubeler-Consulting/knowmind.git"
12
+ },
13
+ "bugs": {
14
+ "url": "https://knowmind.de/support",
15
+ "email": "info@schuebeler-consulting.de"
16
+ },
17
+ "author": {
18
+ "name": "Knowmind",
19
+ "email": "info@schuebeler-consulting.de",
20
+ "url": "https://knowmind.de"
21
+ },
22
+ "engines": {
23
+ "node": ">=20"
24
+ },
25
+ "bin": {
26
+ "knowmind": "bin/knowmind.js"
27
+ },
28
+ "files": [
29
+ "bin",
30
+ "src",
31
+ "!src/*.test.js",
32
+ "README.md",
33
+ "CHANGELOG.md",
34
+ "LICENSE",
35
+ "scripts"
36
+ ],
37
+ "scripts": {
38
+ "test": "node --test src/*.test.js",
39
+ "tools:abgleich": "node scripts/tools-abgleich.mjs"
40
+ },
41
+ "dependencies": {
42
+ "@huggingface/transformers": "^3.5.0"
43
+ },
44
+ "overrides": {
45
+ "global-agent": "^4.1.3"
46
+ },
47
+ "keywords": [
48
+ "knowmind",
49
+ "mcp",
50
+ "model-context-protocol",
51
+ "knowledge-graph",
52
+ "recall",
53
+ "memory",
54
+ "rag",
55
+ "claude",
56
+ "openai",
57
+ "anthropic",
58
+ "ai"
59
+ ],
60
+ "publishConfig": {
61
+ "access": "public"
62
+ }
63
+ }