@getmarrow/mcp 3.9.39 → 3.9.41

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 +20 -6
  2. package/package.json +3 -3
package/README.md CHANGED
@@ -17,13 +17,15 @@ With `@getmarrow/mcp`, any MCP-compatible client can ask Marrow before risky wor
17
17
 
18
18
  ## Trust and Data Boundaries
19
19
 
20
- Marrow is tenant-aware by design. Private account, fleet, memory, workflow, and proof-pack data stays scoped to the authenticated account and authorized agent-bound keys. Shared/hive learning uses visibility-controlled, sanitized aggregate signals; it is not raw cross-customer decision sharing.
20
+ Marrow is tenant-aware by design. Private account, fleet, workflow, proof-pack, and agent data stays scoped to the authenticated account and authorized agent-bound keys.
21
+
22
+ Enterprise tenants receive a strong private governance baseline from day one: risk gates, proof requirements, workflow templates, private/account learning, and exact next actions. Teams that enable sanitized aggregate contribution unlock richer k-anonymous collective workflow guidance. Contribution never means raw prompts, decisions, proof packs, code, secrets, account identifiers, agent identifiers, or customer identities.
21
23
 
22
24
  For business pilots, review the live trust notes before production rollout: https://getmarrow.ai/docs#trust-boundaries
23
25
 
24
- ## What's New in v3.9.39
26
+ ## What's New in v3.9.40
25
27
 
26
- v3.9.39 adds MCP tools for Marrow's governance-control layer.
28
+ v3.9.40 adds MCP tools for Marrow's governance-control layer.
27
29
 
28
30
  - `marrow_governance_control_plane` returns Marrow's cross-harness control-plane contract.
29
31
  - `marrow_hermes_integration` maps Hermes `/goal`, verification evidence, `/learn`, `/journey`, and background subagents into Marrow proof/outcome workflows.
@@ -34,6 +36,17 @@ v3.9.39 adds MCP tools for Marrow's governance-control layer.
34
36
 
35
37
  ---
36
38
 
39
+ ## Current Backend Surfaces
40
+
41
+ The Marrow API also exposes two agent-facing surfaces that help MCP clients and operators verify whether passive capture is producing useful fleet data:
42
+
43
+ - `GET /v1/agent/data-quality` returns an authenticated attribution scorecard for the current account or bound agent, including `agent_id`, `source_meta`, harness/client, workflow type, outcome closure, and non-trivial data coverage.
44
+ - `GET /v1/agent/integrations/{client}` returns a per-harness setup guide for supported clients such as Codex, Claude Code, Cursor, Composer, Windsurf, Cline, OpenCode, Hermes, OpenClaw, Gemini, Grok, DeepSeek, Qwen, Kimi, MiniMax, GLM, MCP clients, CI runners, and custom harnesses.
45
+
46
+ These endpoints are protected by Marrow API-key or agent-bound-key auth and are documented in the source-of-truth docs at [getmarrow.ai/docs](https://getmarrow.ai/docs/).
47
+
48
+ ---
49
+
37
50
  ## Start Here
38
51
 
39
52
  For most agents and new users, start with the universal installer:
@@ -396,7 +409,8 @@ Convert a detected recurring pattern into an enforced workflow. Pattern ID comes
396
409
 
397
410
  `marrow_think` surfaces three additional fields when the backend provides them:
398
411
  - `onboarding_hint` — contextual tip for new accounts
399
- - `intelligence.collective` — anonymized insights aggregated across all Marrow accounts (k-anonymity ≥5 accounts per insight)
412
+ - `intelligence.collective` — entitlement-gated, k-anonymous aggregate patterns when the tenant contributes sanitized aggregate signals and the minimum-account threshold is met
413
+ - `curated_baseline_guidance` — strong private baseline guidance for private or non-contributing tenants
400
414
  - `intelligence.team_context` — recent decisions from other sessions in the same account, so multi-agent teams stay aware of each other's work
401
415
 
402
416
  ---
@@ -699,7 +713,7 @@ npx @getmarrow/install doctor
699
713
  Deep doctor with harmless write/outcome verification:
700
714
 
701
715
  ```bash
702
- MARROW_API_KEY=mrw_live_... npx @getmarrow/install doctor --self-test
716
+ MARROW_API_KEY=<your_marrow_key> npx @getmarrow/install doctor --self-test
703
717
  ```
704
718
 
705
719
  Healthy output should confirm `key valid: yes`, `account active: yes`, `agent identity accepted: yes`, `write test event: passed`, and `outcome closed: passed`. If it fails, Marrow returns the exact reason and fix command.
@@ -708,7 +722,7 @@ Stable project-local key file:
708
722
 
709
723
  ```bash
710
724
  mkdir -p .marrow
711
- printf "MARROW_API_KEY=mrw_live_...\\n" > .marrow/env
725
+ printf "MARROW_API_KEY=<your_marrow_key>\\n" > .marrow/env
712
726
  chmod 600 .marrow/env
713
727
  npx @getmarrow/mcp setup
714
728
  ```
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@getmarrow/mcp",
3
- "version": "3.9.39",
3
+ "version": "3.9.41",
4
4
  "description": "Governance, proof, and intelligence controls for MCP-compatible agent fleets.",
5
5
  "bin": {
6
6
  "marrow-mcp": "dist/cli.js"
@@ -42,7 +42,7 @@
42
42
  ],
43
43
  "repository": {
44
44
  "type": "git",
45
- "url": "https://github.com/MajinBuu0x9/marrow-mcp.git"
45
+ "url": "git+https://github.com/getmarrow/marrow-mcp.git"
46
46
  },
47
47
  "license": "MIT",
48
48
  "files": [
@@ -50,7 +50,7 @@
50
50
  "README.md"
51
51
  ],
52
52
  "dependencies": {
53
- "@getmarrow/sdk": "^3.7.38"
53
+ "@getmarrow/sdk": "^3.7.40"
54
54
  },
55
55
  "devDependencies": {
56
56
  "@types/node": "^25.5.2",