@datacore-one/mcp 1.0.2 → 1.1.1

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
@@ -18,7 +18,24 @@ Install globally:
18
18
  npm install -g @datacore-one/mcp
19
19
  ```
20
20
 
21
- Add to your Claude Desktop config (`~/Library/Application Support/Claude/claude_desktop_config.json`):
21
+ Then connect from any MCP-compatible client. On first use, the server creates `~/Datacore/` with:
22
+
23
+ - `engrams.yaml` — Your learned knowledge
24
+ - `journal/` — Daily session logs
25
+ - `knowledge/` — Ingested reference material
26
+ - `packs/` — Engram packs (starter packs installed automatically)
27
+ - `config.yaml` — Configuration (all fields optional)
28
+ - `CLAUDE.md`, `AGENTS.md`, `.cursorrules`, `.github/copilot-instructions.md` — Editor context files so any AI assistant immediately understands Datacore
29
+
30
+ Everything is plain text -- no databases, no lock-in.
31
+
32
+ ## Connecting
33
+
34
+ Datacore is a standard [MCP](https://modelcontextprotocol.io) server. It works with any client that speaks MCP v1.0+ over stdio or HTTP -- the AI model behind the client does not matter.
35
+
36
+ ### Claude Code
37
+
38
+ Add to `.mcp.json` in your project root (or `~/.claude.json` globally):
22
39
 
23
40
  ```json
24
41
  {
@@ -30,7 +47,9 @@ Add to your Claude Desktop config (`~/Library/Application Support/Claude/claude_
30
47
  }
31
48
  ```
32
49
 
33
- Or for Claude Code, add to `.mcp.json` in your project root:
50
+ ### Claude Desktop
51
+
52
+ Add to `~/Library/Application Support/Claude/claude_desktop_config.json`:
34
53
 
35
54
  ```json
36
55
  {
@@ -42,7 +61,19 @@ Or for Claude Code, add to `.mcp.json` in your project root:
42
61
  }
43
62
  ```
44
63
 
45
- On first use, the server creates `~/Datacore/` with your engrams, journal, and knowledge files. Everything is plain text -- no databases, no lock-in.
64
+ ### Cursor / Windsurf / Other MCP Clients
65
+
66
+ Most MCP-compatible editors use the same config format. Check your editor's MCP documentation for where to place the server config. The command is always `datacore-mcp`.
67
+
68
+ ### HTTP (Remote / Multi-Client)
69
+
70
+ For shared or remote setups, run in HTTP mode:
71
+
72
+ ```bash
73
+ datacore-mcp --http
74
+ ```
75
+
76
+ Then point your MCP client to `http://127.0.0.1:3100/mcp`. See [HTTP Transport](#http-transport) for options.
46
77
 
47
78
  ## Two Modes
48
79
 
@@ -55,7 +86,14 @@ Mode is auto-detected. If you have a full [Datacore](https://github.com/datacore
55
86
 
56
87
  Override with environment variables: `DATACORE_PATH` (full) or `DATACORE_CORE_PATH` (core).
57
88
 
58
- ## Tools
89
+ ## Tools (17 core + 3 full-mode)
90
+
91
+ ### Session
92
+
93
+ | Tool | Description |
94
+ |------|-------------|
95
+ | `datacore.session.start` | Begin a session — injects relevant engrams, shows today's journal |
96
+ | `datacore.session.end` | End a session — captures journal summary and creates engrams |
59
97
 
60
98
  ### Core
61
99
 
@@ -64,15 +102,17 @@ Override with environment variables: `DATACORE_PATH` (full) or `DATACORE_CORE_PA
64
102
  | `datacore.capture` | Write a journal entry or knowledge note |
65
103
  | `datacore.learn` | Create an engram from a statement |
66
104
  | `datacore.inject` | Get relevant engrams for a task |
67
- | `datacore.search` | Search journal and knowledge by keyword |
105
+ | `datacore.recall` | Search all sources (engrams + journal + knowledge) |
106
+ | `datacore.search` | Search journal and knowledge by keyword or semantic |
68
107
  | `datacore.ingest` | Ingest text as a knowledge note with engram extraction |
69
- | `datacore.status` | System status, counts, update info |
108
+ | `datacore.status` | System status, counts, actionable recommendations |
70
109
 
71
110
  ### Lifecycle
72
111
 
73
112
  | Tool | Description |
74
113
  |------|-------------|
75
- | `datacore.feedback` | Signal whether an injected engram was helpful |
114
+ | `datacore.promote` | Activate candidate engrams |
115
+ | `datacore.feedback` | Signal whether engrams were helpful (single or batch) |
76
116
  | `datacore.forget` | Retire an engram by ID or search |
77
117
 
78
118
  ### Packs
@@ -91,6 +131,29 @@ Override with environment variables: `DATACORE_PATH` (full) or `DATACORE_CORE_PA
91
131
  | `datacore.modules.info` | Detailed info about a module |
92
132
  | `datacore.modules.health` | Health check for modules |
93
133
 
134
+ ## Prompts
135
+
136
+ The server provides MCP prompts — workflow templates your AI can discover and use automatically:
137
+
138
+ | Prompt | Description |
139
+ |--------|-------------|
140
+ | `datacore-session` | Start a working session with context injection |
141
+ | `datacore-learn` | Record a learning through the engram lifecycle |
142
+ | `datacore-guide` | Complete guide to all tools and workflows |
143
+
144
+ Prompts are the primary way the AI understands Datacore. When your AI connects, it can list available prompts and immediately knows the session lifecycle, engram workflow, and how all tools relate.
145
+
146
+ ## Resources
147
+
148
+ | Resource | Description |
149
+ |----------|-------------|
150
+ | `datacore://guide` | Agent workflow reference (markdown) |
151
+ | `datacore://status` | System status summary (JSON) |
152
+ | `datacore://engrams/active` | All active engrams (JSON) |
153
+ | `datacore://journal/today` | Today's journal entry (markdown) |
154
+ | `datacore://journal/{date}` | Journal entry by date |
155
+ | `datacore://engrams/{id}` | Specific engram by ID |
156
+
94
157
  ## How Engrams Work
95
158
 
96
159
  Engrams are typed knowledge units with activation dynamics:
@@ -123,6 +186,8 @@ Bundled starter packs are installed automatically on first run.
123
186
 
124
187
  ## Configuration
125
188
 
189
+ ### Environment Variables
190
+
126
191
  | Variable | Default | Description |
127
192
  |----------|---------|-------------|
128
193
  | `DATACORE_PATH` | `~/Data` | Full installation path |
@@ -134,6 +199,25 @@ Bundled starter packs are installed automatically on first run.
134
199
  | `DATACORE_HTTP_PORT` | `3100` | HTTP transport port |
135
200
  | `DATACORE_HTTP_HOST` | `127.0.0.1` | HTTP bind address |
136
201
 
202
+ ### config.yaml
203
+
204
+ Create `config.yaml` in your Datacore directory (or `.datacore/config.yaml` in full mode):
205
+
206
+ ```yaml
207
+ version: 2
208
+ engrams:
209
+ auto_promote: false # true: learn creates active engrams immediately
210
+ packs:
211
+ trusted_publishers: [] # publisher IDs whose packs are flagged for auto-install
212
+ search:
213
+ max_results: 20
214
+ snippet_length: 500 # chars around match
215
+ hints:
216
+ enabled: true # include _hints in tool responses for agent guidance
217
+ ```
218
+
219
+ All fields have defaults -- the file is optional.
220
+
137
221
  ## HTTP Transport
138
222
 
139
223
  For remote or multi-client setups:
@@ -142,8 +226,9 @@ For remote or multi-client setups:
142
226
  DATACORE_HTTP_PORT=8080 datacore-mcp --http
143
227
  ```
144
228
 
145
- Health check: `GET /health`
146
- MCP endpoint: `POST /mcp`
229
+ - MCP endpoint: `POST /mcp`
230
+ - Health check: `GET /health`
231
+ - Default bind: `127.0.0.1:3100`
147
232
 
148
233
  ## Module System (Full Mode)
149
234