@aionis/mcp 0.1.5 → 0.1.7

package/README.md

@@ -2,6 +2,8 @@
 
 MCP stdio bridge for Aionis execution memory.
 
+Docs: [https://docs.aionis.work/integrations/mcp](https://docs.aionis.work/integrations/mcp)
+
 Use this package when you want Claude Code, Cursor, or another MCP client to
 try Aionis without rewriting the host Agent loop first.
 
@@ -25,7 +27,7 @@ The server exposes stable product tools, not internal Runtime packets:
 | Tool | Purpose |
 |---|---|
 | `aionis_context` | Compile governed Agent context for the current run. Optionally records a lightweight observation first. |
-| `aionis_record_step` | Record a planner/worker/verifier/reviewer step. Feedback attribution is optional. |
+| `aionis_record_step` | Record a planner/worker/verifier/reviewer step, including planner plan assets and rejected branch evidence. Feedback attribution is optional. |
 | `aionis_handoff` | Record branch-aware multi-agent handoff state. |
 | `aionis_remember` | Store ordinary project memory through the governed observe path. |
 | `aionis_govern_memory` | Route external Mem0/Zep/vector/markdown candidates through Aionis Memory Firewall before prompt use. |
@@ -46,6 +48,20 @@ Runtime guide, and `budget_profile`, `max_prompt_chars`, `repo_state`, and
 For example, pass `repo_state.missing_files` so Aionis can tell the Agent that a
 missing active target is pending work rather than stale memory.
 
+For Claude Code or Cursor demos, the recommended flow is:
+
+1. Use `aionis_record_step` as a planner to record the accepted plan,
+   active targets, acceptance checks, and execution boundary.
+2. Use `aionis_record_step` again for any rejected branch as `outcome:
+   "failed"` with the rejected target files.
+3. Ask `aionis_context` for the worker/reviewer context before implementation.
+4. Use `aionis_flight_recorder` after the run to replay which plan memories and
+   failed branches were visible at decision time.
+
+This is the MCP shape of Aionis Plan as Memory Asset: the MCP client can use a
+strong planner once, then let later workers continue from adjudicated execution
+memory instead of raw chat history.
+
 The tool returns these structured fields in `structuredContent`:
 
 | Field | Meaning |
@@ -122,3 +138,9 @@ npm run -s lite:start
 
 For deeper host integration, use `@aionis/sdk`. The MCP bridge is the
 drop-in path; the SDK is the full application integration path.
+
+Claude Code / Cursor walkthrough:
+[https://docs.aionis.work/integrations/mcp](https://docs.aionis.work/integrations/mcp)
+
+Runnable proof artifacts:
+[https://docs.aionis.work/examples](https://docs.aionis.work/examples)

package/dist/server.js

@@ -55,7 +55,7 @@ function register(server, client, name, config) {
 export function createAionisMcpServer(client) {
     const server = new McpServer({
         name: "aionis-mcp",
-        version: "0.1.4",
+        version: "0.1.7",
     });
     register(server, client, "aionis_context", {
         title: "Get Aionis Agent Context",

package/package.json

@@ -1,8 +1,14 @@
 {
   "name": "@aionis/mcp",
-  "version": "0.1.5",
+  "version": "0.1.7",
   "description": "MCP stdio bridge for Aionis execution memory.",
   "license": "Apache-2.0",
+  "homepage": "https://docs.aionis.work/integrations/mcp",
+  "repository": {
+    "type": "git",
+    "url": "https://github.com/ostinatocc/Aionis.git",
+    "directory": "packages/aionis-mcp"
+  },
   "type": "module",
   "bin": {
     "aionis-mcp": "dist/index.js"
@@ -12,7 +18,7 @@
     "README.md"
   ],
   "engines": {
-    "node": ">=22.0.0"
+    "node": ">=22.5.0"
   },
   "scripts": {
     "build": "tsc -p tsconfig.json",
@@ -20,7 +26,7 @@
     "prepack": "npm run build"
   },
   "dependencies": {
-    "@aionis/sdk": "^0.1.8",
+    "@aionis/sdk": "^0.1.10",
     "@modelcontextprotocol/sdk": "^1.29.0",
     "zod": "^3.25.76"
   },