Aionis MCP Server
@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:
{
"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:
aionis_session_begin
-> aionis_session_turn
-> Agent action
-> aionis_session_action
-> aionis_session_verify
-> aionis_session_finishPersist 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 |
| Begin the canonical SDK AgentSession and return its portable handle. |
| Resume an interrupted session from that handle. |
| Record an observation and return the SDK-rendered Agent prompt. |
| Record the host action result and capture the new subject state. |
| Run the Runtime-owned project verifier. |
| Complete only after verifier success; otherwise continue/recover. |
| Get the canonical SDK Agent context without MCP-side rendering. |
| Submit exact guide-attributed feedback. |
| Recover exact archived memory. |
| Suppress, unsuppress, rehydrate, or activate memory. |
| Store ordinary project memory. |
| 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.