# @aionis/mcp

MCP transport for Aionis Verified Continuity.

Start a Runtime installed with a real project verifier, then configure your MCP
host to launch the bridge:

```json
{
  "mcpServers": {
    "aionis": {
      "command": "npx",
      "args": [
        "-y",
        "@aionis/mcp@next",
        "--base-url",
        "http://127.0.0.1:3001",
        "--scope-from",
        "workspace"
      ],
      "env": {
        "AIONIS_TENANT_ID": "local"
      }
    }
  }
}
```

The bridge does not implement another continuation engine. It transports the
same serialized SDK `AgentSession` handle between MCP calls:

```text
aionis_session_begin
  -> aionis_session_turn
  -> Agent action
  -> aionis_session_action
  -> aionis_session_verify
  -> aionis_session_finish
```

Persist the returned `handle` after every call. After interruption, pass that
handle to `aionis_session_resume`. The Runtime owns state capture and verifier
authority; `aionis_session_finish` returns `completed` only when the configured
verifier passes, otherwise it returns continuation/recovery state.

## Tools

| Tool | Product behavior |
|---|---|
| `aionis_session_begin` | Begin the canonical SDK AgentSession and return its portable handle. |
| `aionis_session_resume` | Resume an interrupted session from that handle. |
| `aionis_session_turn` | Record an observation and return the SDK-rendered Agent prompt. |
| `aionis_session_action` | Record the host action result and capture the new subject state. |
| `aionis_session_verify` | Run the Runtime-owned project verifier. |
| `aionis_session_finish` | Complete only after verifier success; otherwise continue/recover. |
| `aionis_guide` | Get the canonical SDK Agent context without MCP-side rendering. |
| `aionis_feedback` | Submit exact guide-attributed feedback. |
| `aionis_rehydrate` | Recover exact archived memory. |
| `aionis_forget` | Suppress, unsuppress, rehydrate, or activate memory. |
| `aionis_remember` | Store ordinary project memory. |
| `aionis_health` | Check Runtime reachability. |

When the MCP host starts outside the repository, add `--repo-root
/absolute/path/to/repo`. `--scope-from workspace` persists a stable
`.aionis/workspace.json` identity so new processes continue in the same scope.