@aionis/mcp 0.1.6 → 0.1.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
@@ -27,7 +27,7 @@ The server exposes stable product tools, not internal Runtime packets:
27
27
  | Tool | Purpose |
28
28
  |---|---|
29
29
  | `aionis_context` | Compile governed Agent context for the current run. Optionally records a lightweight observation first. |
30
- | `aionis_record_step` | Record a planner/worker/verifier/reviewer step. Feedback attribution is optional. |
30
+ | `aionis_record_step` | Record a planner/worker/verifier/reviewer step, including planner plan assets and rejected branch evidence. Feedback attribution is optional. |
31
31
  | `aionis_handoff` | Record branch-aware multi-agent handoff state. |
32
32
  | `aionis_remember` | Store ordinary project memory through the governed observe path. |
33
33
  | `aionis_govern_memory` | Route external Mem0/Zep/vector/markdown candidates through Aionis Memory Firewall before prompt use. |
@@ -48,6 +48,20 @@ Runtime guide, and `budget_profile`, `max_prompt_chars`, `repo_state`, and
48
48
  For example, pass `repo_state.missing_files` so Aionis can tell the Agent that a
49
49
  missing active target is pending work rather than stale memory.
50
50
 
51
+ For Claude Code or Cursor demos, the recommended flow is:
52
+
53
+ 1. Use `aionis_record_step` as a planner to record the accepted plan,
54
+ active targets, acceptance checks, and execution boundary.
55
+ 2. Use `aionis_record_step` again for any rejected branch as `outcome:
56
+ "failed"` with the rejected target files.
57
+ 3. Ask `aionis_context` for the worker/reviewer context before implementation.
58
+ 4. Use `aionis_flight_recorder` after the run to replay which plan memories and
59
+ failed branches were visible at decision time.
60
+
61
+ This is the MCP shape of Aionis Plan as Memory Asset: the MCP client can use a
62
+ strong planner once, then let later workers continue from adjudicated execution
63
+ memory instead of raw chat history.
64
+
51
65
  The tool returns these structured fields in `structuredContent`:
52
66
 
53
67
  | Field | Meaning |
package/dist/server.js CHANGED
@@ -55,7 +55,7 @@ function register(server, client, name, config) {
55
55
  export function createAionisMcpServer(client) {
56
56
  const server = new McpServer({
57
57
  name: "aionis-mcp",
58
- version: "0.1.6",
58
+ version: "0.1.7",
59
59
  });
60
60
  register(server, client, "aionis_context", {
61
61
  title: "Get Aionis Agent Context",
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@aionis/mcp",
3
- "version": "0.1.6",
3
+ "version": "0.1.7",
4
4
  "description": "MCP stdio bridge for Aionis execution memory.",
5
5
  "license": "Apache-2.0",
6
6
  "homepage": "https://docs.aionis.work/integrations/mcp",
@@ -26,7 +26,7 @@
26
26
  "prepack": "npm run build"
27
27
  },
28
28
  "dependencies": {
29
- "@aionis/sdk": "^0.1.9",
29
+ "@aionis/sdk": "^0.1.10",
30
30
  "@modelcontextprotocol/sdk": "^1.29.0",
31
31
  "zod": "^3.25.76"
32
32
  },