@getmarrow/mcp 3.8.1 → 3.8.3

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.
Files changed (2) hide show
  1. package/README.md +50 -455
  2. package/package.json +1 -1
package/README.md CHANGED
@@ -4,438 +4,30 @@
4
4
 
5
5
  ![npm](https://img.shields.io/npm/v/@getmarrow/mcp)
6
6
  ![npm](https://img.shields.io/npm/dw/@getmarrow/mcp)
7
- ![npm bundle size](https://img.shields.io/bundlephobia/minzip/@getmarrow/mcp)
8
- ![GitHub](https://img.shields.io/github/license/MajinBuu0x9/marrow-mcp)
9
- ![TypeScript](https://img.shields.io/badge/TypeScript-5.3%2B-blue)
10
- ![Node.js](https://img.shields.io/badge/Node.js-18%2B-green)
11
7
 
12
- Marrow gives your agent a memory that compounds.
13
-
14
- With `@getmarrow/mcp`, any MCP-compatible client can log intent before acting, inspect live loop state during work, and commit outcomes back to the hive when the work is done. That means your agent stops operating like an amnesiac and starts carrying forward real decision history.
15
-
16
- **Your agent stops repeating the same mistakes. It learns from prior sessions — and from the wider Marrow hive — through a clean MCP tool surface.**
17
-
18
- ---
19
-
20
- ## Improvement Since Onboarding
21
-
22
- `marrow_dashboard` and `marrow_digest` now return an `improvement` block comparing your agents' current performance against their day-1 baseline — a frozen snapshot of the first week of activity. Baseline captures automatically once an account reaches 7 days OR 20 decisions (whichever first).
23
-
24
- Four measured deltas, all from real decision data:
25
-
26
- - `attempts_per_success` — baseline week vs current week
27
- - `time_to_success_seconds` — median think → successful commit
28
- - `drift_rate` — % of decisions without a matching prior pattern
29
- - `success_rate` — baseline vs current outcome fraction
30
-
31
- Sample response:
32
-
33
- ```json
34
- {
35
- "improvement": {
36
- "status": "active",
37
- "days_since_baseline": 20,
38
- "decisions_since_baseline": 2124,
39
- "baseline_captured_at": "2026-04-23T15:07:41.919Z",
40
- "trigger_reason": "time_7d",
41
- "time_to_success_seconds": { "baseline": 244, "current": 24, "delta_pct": -90.16 }
42
- }
43
- }
44
- ```
45
-
46
- Accounts with <7 days of activity AND <20 decisions get an onboarding payload showing days/decisions until baseline fires. No heuristics, no estimates — every number comes from the agent's own decision history. Token-usage savings remain on the enterprise roadmap.
47
-
48
- ---
49
-
50
- ## What's New in v3.8.0
51
-
52
- ### Multi-API-Key Management Tools
53
-
54
- Five new MCP tools for managing API keys across your agent fleet — no dashboard required:
55
-
56
- - `marrow_create_key` — Create named, scoped API keys (`live`/`test` type, optional scopes and agent bindings)
57
- - `marrow_list_keys` — List all API keys with masked display and tier limits
58
- - `marrow_get_key` — Get key details, usage stats, and expiry info
59
- - `marrow_revoke_key` — Permanently revoke a key
60
- - `marrow_rotate_key` — Atomically rotate (revoke old + create new, returns new key once)
61
-
62
- Create/rotate return the full key exactly once with a warning. All other tools return masked keys only.
63
-
64
- ```bash
65
- npx @getmarrow/mcp --key mrw_...
66
- # Now available: marrow_create_key, marrow_list_keys, marrow_get_key,
67
- # marrow_revoke_key, marrow_rotate_key
68
- ```
69
-
70
- ---
71
-
72
- ### Previous: v3.7.0 — Passive Context Injection
73
-
74
- Marrow's passive loop is now complete. v3.2.0 shipped the **write side** — every tool call your agent makes is auto-logged via a PostToolUse hook. v3.7.0 ships the **read side** — Marrow's intelligence is auto-injected into your agent's prompt window via a UserPromptSubmit hook. No agent discipline required for either side.
75
-
76
- When you run `npx @getmarrow/mcp setup`, both hooks install automatically. From the next user prompt forward:
77
-
78
- 1. You type a message to your agent
79
- 2. Hook fires, takes your prompt, queries Marrow for relevant warnings + hive patterns + similar past decisions
80
- 3. Marrow context (if any) is injected into your agent's view as `additionalContext`
81
- 4. Agent responds knowing what failed last time, what worked, and what patterns to leverage
82
-
83
- The hook is fail-silent: 2-second timeout on the Marrow API call, errors swallowed, never blocks your prompt. No signal → no injection. `MARROW_AUTO_HOOK=false` disables both hooks. `MARROW_CONTEXT_HOOK_DEBUG=true` enables stderr diagnostics.
84
-
85
- This closes the loop Buu identified: Marrow now *just works* — your agent reads from the hive without you ever telling it to.
86
-
87
- ---
88
-
89
- ## Agent-Narrated Marrow Contribution
90
-
91
- Marrow now tells the agent exactly what it contributed to each decision, so the agent can surface that contribution to the user in plain English — no dashboard required.
92
-
93
- Three new fields:
94
-
95
- - `marrow_think` returns `marrow_contributed` describing what intelligence Marrow surfaced for this decision (warnings consulted, hive patterns, similar decisions, workflow templates, loop detection, collective insight).
96
- - `marrow_commit` returns `marrow_contributed` describing concrete signals on the commit itself (pattern reused, warning avoided, workflow step).
97
- - `marrow_session_end` returns `session_summary` aggregating Marrow's contribution across the session, plus a one-line `narrative` for the agent to surface as it wraps up.
98
-
99
- Each object includes `has_signal: boolean` — when true, the agent narrates Marrow's role in 1 sentence; when false, it stays quiet. The built-in `marrow-always-on` system prompt now instructs agents on tone and timing for these narrations.
100
-
101
- Sample think response:
102
-
103
- ```json
104
- {
105
- "decision_id": "...",
106
- "intelligence": { "...": "..." },
107
- "marrow_contributed": {
108
- "warnings_consulted": 2,
109
- "hive_patterns_surfaced": 12,
110
- "similar_decisions_found": 8,
111
- "workflow_templates_available": 1,
112
- "loop_detected": false,
113
- "collective_intelligence": true,
114
- "team_context_present": false,
115
- "has_signal": true
116
- }
117
- }
118
- ```
119
-
120
- The user installed Marrow to make their agent better. They should hear, in plain English, what Marrow actually did. Their agent's reply IS the dashboard.
121
-
122
- ---
123
-
124
- ## Agent-Narrated Milestones
125
-
126
- `marrow_commit` returns a `narrative` field. When a milestone fires (first commit, baseline capture, decision 100/500/1000/5000, weekly recap), the backend returns a human-readable string the agent relays to the user. Otherwise it returns `null`.
127
-
128
- ```json
129
- {
130
- "committed": true,
131
- "narrative": "Baseline captured. Your first-week averages: 42s per task, 1.3 attempts per success."
132
- }
133
- ```
134
-
135
- Narratives are aggregated metrics only — no user data, no decision content, no heuristics.
136
-
137
- ---
138
-
139
- ## Velocity Metrics
140
-
141
- `marrow_dashboard` and `marrow_digest` include three measured velocity metrics:
142
-
143
- - `attempts_per_success` — avg decisions before an agent lands a success
144
- - `time_to_success_seconds` — median seconds from `marrow_think` to successful `marrow_commit`
145
- - `drift_rate` — % of decisions that didn't link to a known pattern
146
-
147
- Each reports `{current, previous, delta_pct, direction}` so operators see whether agents are trending toward or away from improvement.
148
-
149
- All metrics are computed from real decision data — no estimates, no heuristics.
150
-
151
- ---
152
-
153
- ## Passive Mode
154
-
155
- Running `npx @getmarrow/mcp setup` installs a PostToolUse hook into `.claude/settings.json`. After setup, every tool call your agent makes (Bash, file edits, MCP calls) is auto-logged to Marrow in the background — no agent discipline required.
156
-
157
- Disable via: `MARROW_AUTO_HOOK=false`
158
-
159
- For troubleshooting hook behavior, set `MARROW_HOOK_DEBUG=true` to re-enable one-line stderr diagnostics.
160
-
161
- **Operator visibility + auto-intelligence tools.**
162
-
163
- ## Operator Tools
164
-
165
- ### marrow_dashboard
166
-
167
- Operator dashboard in one call. Account health, top failures, workflow status, recent activity, Marrow's saves metric. Now includes velocity metrics (see v3.3.0 section above).
168
-
169
- ### marrow_digest
170
-
171
- Periodic summary with success rate trend vs previous period. Optional `period` parameter (default `7d`). Now includes velocity summary (see v3.3.0 section above).
172
-
173
- ### marrow_session_end
174
-
175
- Explicitly end a session and optionally auto-commit any open decision. Prevents orphaned decisions.
176
-
177
- ### marrow_accept_detected
178
-
179
- Convert a detected recurring pattern into an enforced workflow. Pattern ID comes from `orient()` response's `suggested_workflows`.
180
-
181
- ## Intelligence Fields in marrow_think Response
182
-
183
- `marrow_think` surfaces three additional fields when the backend provides them:
184
- - `onboarding_hint` — contextual tip for new accounts
185
- - `intelligence.collective` — anonymized insights aggregated across all Marrow accounts (k-anonymity ≥5 accounts per insight)
186
- - `intelligence.team_context` — recent decisions from other sessions in the same account, so multi-agent teams stay aware of each other's work
187
-
188
- ---
189
-
190
- ## Available Templates
191
-
192
- 24 pre-built workflow templates across 8 industries. Browse via `marrow_list_templates` and install with `marrow_install_template`.
193
-
194
- - **Insurance (4):** `claims-triage`, `fraud-review`, `underwriting-decision`, `complaint-escalation`
195
- - **Healthcare (4):** `patient-triage`, `clinical-documentation`, `prior-authorization`, `coding-audit`
196
- - **E-commerce (3):** `order-fulfillment`, `refund-approval`, `return-processing`
197
- - **Legal (3):** `contract-review`, `case-triage`, `document-discovery`
198
- - **SaaS (6):** `code-review-deploy`, `incident-response`, `feature-rollout`, `ticket-triage`, `escalation-flow`, `lead-qualify`
199
- - **Fintech (2):** `etl-pipeline`, `approval-flow`
200
- - **Media (1):** `content-publish`
201
- - **Enterprise (1):** `change-management`
202
-
203
- Full catalog with descriptions: [getmarrow.ai/docs#template-marketplace](https://getmarrow.ai/docs/#template-marketplace)
204
-
205
- ```
206
- marrow_list_templates({ industry: 'insurance' })
207
- marrow_install_template({ slug: 'claims-triage' })
208
- ```
209
-
210
- ## Claude Code Compatibility
211
-
212
- Marrow MCP works natively with Claude Code. The server runs as a long-running process and handles the full MCP protocol correctly.
213
-
214
- ## One-Command Agent Setup
215
-
216
- Inject Marrow instructions directly into your project's `CLAUDE.md`:
217
-
218
- ```bash
219
- npx @getmarrow/mcp setup
220
- ```
221
-
222
- After setup, your agent uses Marrow automatically every session, and Claude Code PostToolUse hooks auto-log tool calls in the background — no human prompting required.
223
-
224
- ## Auto-Enroll by Default
225
- The `marrow-always-on` prompt is served to all MCP clients automatically. Set `MARROW_AUTO_ENROLL=false` to opt out.
226
-
227
- ## Security Hardening
228
- - **Input validation** — all URL path parameters are sanitized to prevent path traversal
229
- - **SSRF protection** — `MARROW_BASE_URL` must use HTTPS
230
- - **Crash protection** — malformed JSON on stdin no longer kills the server
231
- - **Error handling** — proper error logging throughout
232
- - **HTTP status checking** — API errors return clear messages
233
-
234
- ### Auto-Warn on Orient
235
- The `marrow_orient` tool now accepts `autoWarn: true` and warns you BEFORE you start a task that recently failed:
236
-
237
- ```json
238
- {
239
- "name": "marrow_orient",
240
- "arguments": {
241
- "autoWarn": true,
242
- "task": "Fix authentication error"
243
- }
244
- }
245
- ```
246
-
247
- **Response includes warnings:**
248
- ```
249
- ⚠️ HIGH: This task type failed 4x with approach='retry-without-fix'.
250
- Try approach='apply-patch-first' (89% success rate)
251
- ```
252
-
253
- ### Loop Detection on Think
254
- The `marrow_think` tool now accepts `checkLoop: true` and detects if you're about to retry a failed approach:
255
-
256
- ```json
257
- {
258
- "name": "marrow_think",
259
- "arguments": {
260
- "action": "Retry auth with method='internal'",
261
- "checkLoop": true
262
- }
263
- }
264
- ```
265
-
266
- **Response includes loop warnings:**
267
- ```
268
- 🚨 LOOP DETECTED: You're retrying a failed approach.
269
- Previous failure: 'retry-without-fix' approach not supported.
270
- Suggested: Use 'apply-patch-first' approach instead.
271
- ```
272
-
273
- ### Rate Limiting
274
- - `marrow_orient`: 30 requests/minute per account
275
- - `marrow_think`: 60 requests/minute per account
276
- - Automatic 429 responses when limit exceeded
277
-
278
- ### Enhanced PII Protection
279
- - Automatic stripping of emails, phone numbers, API keys from all responses
280
- - Applied to `recentLessons`, `warnings`, and `outcome` fields
281
- - Deep object stripping for complex data structures
282
-
283
- ---
284
-
285
- ## The Problem
286
-
287
- Most agents still operate with shallow memory.
288
-
289
- They might keep a short context window, maybe write a note or two, then lose the important part:
290
- - what they were trying to do
291
- - what they actually did
292
- - whether it worked
293
- - what pattern that should teach the next run
294
-
295
- That creates a familiar failure loop:
296
- - the same mistakes repeat
297
- - work gets marked done without structured outcome memory
298
- - agents drift between sessions
299
- - hosts have no clean way to inspect whether the work loop is actually closed
300
-
301
- **Marrow fixes this.**
302
-
303
- Through MCP, your agent can:
304
- - orient at session start
305
- - log intent before meaningful action
306
- - inspect loop state before handoff or completion
307
- - commit outcomes back to memory cleanly
308
-
309
- ---
310
-
311
- ## How It Works
312
-
313
- Marrow exposes a simple operating loop through MCP:
314
-
315
- ```text
316
- orient -> think -> act -> check -> commit
317
- ```
318
-
319
- That gives agents an actual memory discipline:
320
- - **orient** → pick up recent lessons and current loop state
321
- - **think** → log intent and receive decision intelligence
322
- - **act** → perform the meaningful work
323
- - **check** → inspect whether the loop is still open or missing something
324
- - **commit** → log the outcome and close the loop
325
-
326
- The value compounds with use. Each decision your agent logs makes the hive smarter — failure rates drop, patterns emerge, and the next session starts with real intelligence instead of a blank slate. Teams running multiple agents see this compound fastest, but even a single agent builds meaningful history within a few sessions.
8
+ `@getmarrow/mcp` connects your Claude, Cursor, or any MCP client to Marrow's collective memory. Every tool call auto-logged, intelligence auto-injected — no agent discipline required.
327
9
 
328
10
  ---
329
11
 
330
12
  ## Install
331
13
 
332
- ### Quick Start (Claude Code)
333
-
334
14
  ```bash
335
- # 1. Add the MCP server
336
- claude mcp add marrow -e MARROW_API_KEY=mrw_your_api_key -- npx @getmarrow/mcp
337
-
338
- # 2. Set up auto-enrollment (agent uses Marrow automatically)
339
- npx @getmarrow/mcp setup
15
+ npm install @getmarrow/mcp
340
16
  ```
341
17
 
342
- That's it. Your agent will use Marrow automatically in every session.
343
-
344
- ### Manual Setup
345
-
346
- Run it directly with `npx`:
18
+ ## One-Command Setup (Claude Code)
347
19
 
348
20
  ```bash
349
- # Option 1: Pass API key via CLI flag
350
- npx @getmarrow/mcp --key mrw_your_api_key
351
-
352
- # Option 2: Use environment variable
353
- MARROW_API_KEY=mrw_your_api_key npx @getmarrow/mcp
21
+ npx @getmarrow/mcp setup
354
22
  ```
355
23
 
356
- Or register it in your MCP client config.
357
-
358
- ---
359
-
360
- ## MCP Tools
361
-
362
- ### Core Loop Tools
363
-
364
- #### `marrow_orient`
365
- **Call this first** at session start. Returns failure warnings from your history so you avoid known mistakes immediately.
366
-
367
- #### `marrow_think`
368
- Log intent before meaningful action. Returns pattern insights, similar past decisions, and a recommended next step.
369
-
370
- #### `marrow_commit`
371
- Log the outcome after acting. Closes the decision loop.
372
-
373
- #### `marrow_run`
374
- Zero-ceremony wrapper. Handles orient → think → commit in a single call.
375
-
376
- #### `marrow_auto`
377
- Fire-and-forget logging. Pass what you're about to do (and optionally the outcome). Marrow handles everything in the background.
378
-
379
- ### Memory Management Tools
380
-
381
- #### `marrow_list_memories`
382
- List memories with optional filters:
383
- - `status` — Filter by status (active, outdated, deleted)
384
- - `query` — Search query
385
- - `limit` — Max results
386
- - `agentId` — Include memories shared with this agent
387
-
388
- #### `marrow_get_memory`
389
- Get a single memory by ID.
390
-
391
- #### `marrow_update_memory`
392
- Update memory text, tags, or metadata.
393
-
394
- #### `marrow_delete_memory`
395
- Soft delete a memory.
396
-
397
- #### `marrow_mark_outdated`
398
- Mark a memory as outdated.
24
+ Installs PostToolUse + UserPromptSubmit hooks. Every tool call auto-logs to Marrow. Intelligence auto-injected into your agent's context. Zero agent code required.
399
25
 
400
- #### `marrow_supersede_memory`
401
- Atomically replace a memory with a new version.
26
+ Disable: `MARROW_AUTO_HOOK=false`. Debug: `MARROW_HOOK_DEBUG=true`.
402
27
 
403
- #### `marrow_share_memory`
404
- Share a memory with specific agents.
28
+ ## Manual MCP Config
405
29
 
406
- #### `marrow_export_memories`
407
- Export memories to JSON or CSV format.
408
-
409
- #### `marrow_import_memories`
410
- Import memories with merge (dedup) or replace mode.
411
-
412
- #### `marrow_retrieve_memories`
413
- Full-text search with filters:
414
- - `query` — Search query (required)
415
- - `limit` — Max results
416
- - `from` / `to` — Date range (ISO-8601)
417
- - `tags` — Comma-separated tags
418
- - `source` — Source filter
419
- - `status` — Status filter
420
- - `shared` — Include shared memories
421
-
422
- ### Query Tools
423
-
424
- #### `marrow_ask`
425
- Query the collective hive in plain English. Ask about failure patterns, what worked, what broke, or get a recommendation.
426
-
427
- #### `marrow_status`
428
- Check Marrow platform health and status.
429
-
430
- ---
431
-
432
- ## Claude Code Config
433
-
434
- ```bash
435
- claude mcp add marrow -e MARROW_API_KEY=mrw_your_api_key -- npx @getmarrow/mcp
436
- ```
437
-
438
- ## Claude Desktop Config
30
+ Add to your Claude Desktop or MCP client config:
439
31
 
440
32
  ```json
441
33
  {
@@ -448,54 +40,57 @@ claude mcp add marrow -e MARROW_API_KEY=mrw_your_api_key -- npx @getmarrow/mcp
448
40
  }
449
41
  ```
450
42
 
451
- ---
452
-
453
- ## Environment Variables
454
-
455
- | Variable | Required | Description |
456
- |----------|----------|-------------|
457
- | `MARROW_API_KEY` | Yes | Your API key from getmarrow.ai (or use `--key` flag) |
458
- | `MARROW_BASE_URL` | No | Custom API URL (default: `https://api.getmarrow.ai`). Must use HTTPS. |
459
- | `MARROW_SESSION_ID` | No | Session identifier for multi-agent setups |
460
- | `MARROW_FLEET_AGENT_ID` | No | Agent identifier sent as `X-Marrow-Agent-Id` for fleet attribution |
461
- | `MARROW_AUTO_ENROLL` | No | Auto-enrollment prompt (default: `true`). Set to `false` to disable. |
462
- | `MARROW_AUTO_HOOK` | No | PostToolUse auto-logging kill switch. Set to `false` to disable the hook without editing settings. |
463
- | `MARROW_HOOK_DEBUG` | No | When set to `true`, the hook emits one-line stderr diagnostics for invalid JSON, missing API key, and runtime failures. |
43
+ ## Core MCP Tools
464
44
 
465
- ---
466
-
467
- ## The Always-On Prompt
45
+ | Tool | Description |
46
+ |------|-------------|
47
+ | `marrow_orient` | Session-start failure warnings |
48
+ | `marrow_think` | Log intent + get hive intelligence |
49
+ | `marrow_commit` | Record outcome — closes decision loop |
50
+ | `marrow_run` | Zero-ceremony: orient → think → commit |
51
+ | `marrow_auto` | Fire-and-forget background logging |
52
+ | `marrow_dashboard` | Account health, failures, velocity |
53
+ | `marrow_digest` | Weekly summary with trends |
54
+ | `marrow_session_end` | Close session with summary |
468
55
 
469
- Marrow includes a built-in prompt called `marrow-always-on` that instructs agents to use Marrow automatically. It's served by default — no configuration needed.
56
+ ### 🆕 v3.8.2 Multi-API-Key Management
470
57
 
471
- **To use:** In your MCP client, request the `marrow-always-on` prompt and include it in your system instructions. For Claude Code, run `npx @getmarrow/mcp setup` instead — it handles this automatically.
58
+ | Tool | Description |
59
+ |------|-------------|
60
+ | `marrow_create_key` | Create scoped API keys |
61
+ | `marrow_list_keys` | List all keys (masked) |
62
+ | `marrow_get_key` | Key details + usage stats |
63
+ | `marrow_rotate_key` | Atomically rotate a key |
64
+ | `marrow_revoke_key` | Permanently revoke |
472
65
 
473
- ---
474
-
475
- ## Why This Matters
66
+ ### Memory Management Tools
476
67
 
477
- Without Marrow:
478
- - Agents repeat the same failures session after session
479
- - Successful patterns get lost when the context window clears
480
- - There's no structured trail of what was tried and what worked
481
- - Every new session starts from zero
68
+ | Tool | Description |
69
+ |------|-------------|
70
+ | `marrow_list_memories` | List with filters |
71
+ | `marrow_get_memory` | Single memory by ID |
72
+ | `marrow_update_memory` | Update text or tags |
73
+ | `marrow_delete_memory` | Soft-delete a memory |
74
+ | `marrow_share_memory` | Share with specific agents |
482
75
 
483
- With Marrow:
484
- - Failure patterns surface before you repeat them
485
- - Successful outcomes compound across sessions
486
- - Every decision has a trail: intent → action → outcome
487
- - The hive gets smarter with every logged decision
76
+ ## Auto-Logging
488
77
 
489
- **Marrow tells you what went wrong last time before you do it again.**
78
+ Marrow auto-logs at three layers:
490
79
 
491
- ---
80
+ | Layer | How | Effort |
81
+ |-------|-----|--------|
82
+ | Server-side | Every API call auto-logged | Zero |
83
+ | SDK | `marrow.think()` / `marrow.commit()` | Minimal |
84
+ | MCP hooks | `npx @getmarrow/mcp setup` | Zero |
492
85
 
493
- ## License
86
+ Passive mode: run setup once, auto-logging runs silently forever.
494
87
 
495
- MIT
496
-
497
- ---
88
+ ## Full Documentation
498
89
 
499
- ## Related Packages
90
+ 📖 **Complete API reference, metrics, features, and examples:**
91
+ **[https://getmarrow.ai/docs](https://getmarrow.ai/docs)**
500
92
 
501
- - **[@getmarrow/sdk](https://www.npmjs.com/package/@getmarrow/sdk)** — TypeScript/Node.js SDK for programmatic access to Marrow. Use this for custom agent integrations outside of MCP.
93
+ - [Auto-Logging](https://getmarrow.ai/docs/#auto-logging)
94
+ - [Metrics & Intelligence](https://getmarrow.ai/docs/#metrics-intelligence)
95
+ - [API Key Management](https://getmarrow.ai/docs/#api-key-management)
96
+ - [API Reference](https://getmarrow.ai/docs/#api-reference)
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@getmarrow/mcp",
3
- "version": "3.8.1",
3
+ "version": "3.8.3",
4
4
  "description": "Your go-to memory provider for all agents, for any AI model.",
5
5
  "bin": {
6
6
  "marrow-mcp": "dist/cli.js"