@kybernesis/arcana

ianborders

Kybernesis Arcana long-term memory for eve agents: MCP connection, memory skills, and recall-first instructions. Mount once per brain.

Knowledge Memory

Add to Cursor Add to VS Code Run on PlugMCP

GitHub npm Website

Add to Cursor Add to VS Code Run on PlugMCP

1{2  "mcpServers": {3    "kybernesis-arcana": {4      "command": "npx",5      "args": [6        "-y",7        "@kybernesis/[email protected]"8      ]9    }10  }11}

.cursor/mcp.jsonMCP server

Transport: stdio
Status: Local

Power your agent

Add this server

The publisher's own command. Not a PlugMCP endpoint.

Add to Cursor Add to VS Code Run on PlugMCP

Host a copy with our keys and logs.

Local command

npx -y @kybernesis/[email protected]

Claude Code has no install link for a local command. Copy the command below and run it in a terminal.

shClaude Code

1claude mcp add kybernesis-arcana -- npx -y @kybernesis/arcana@0.7.0

Run in a terminal.

jsonClaude Desktop

1{2  "mcpServers": {3    "kybernesis-arcana": {4      "command": "npx",5      "args": [6        "-y",7        "@kybernesis/[email protected]"8      ]9    }10  }11}

claude_desktop_config.json

Local · npmPublisher installStep-by-step: add this in Claude

Remote URL or a command on your machine? How the two installs differ

Run on PlugMCP

Host a copy with our keys and logs.

A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.

Launch

Server facts

Local

Transport: stdio
Version: 0.7.0
Last checked: 2026-10-28

Stars: —
Tools: —
Uptime: —

Tools

No tool list yet. Remote servers get one after the first health check.

FAQ

Questions

How do I install @kybernesis/arcana?

Copy the stdio config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.

Does @kybernesis/arcana need an API key?

No required environment variable is listed on this record.

What transport does @kybernesis/arcana use?

@kybernesis/arcana runs locally over stdio.

When was @kybernesis/arcana last checked?

Last checked 2026-10-28. Kybernesis Arcana long-term memory for eve agents: MCP connection, memory skills, and recall-first instructions. Mount once per brain.

From the publisher

Documentation

Kybernesis Platform

The product monorepo for Kybernesis — the ecosystem layer that makes eve agent deployments enterprise-ready and uniquely Kybernesis. Eve is the plumbing; this is the moat.

Packages (all Apache-2.0, published to npm)

Package	What it gives an agent
`@kybernesis/arcana`	Durable Arcana memory through an MCP connection, recall/remember/brain-note skills, per-session workspace selection, and recall-first instructions
`@kybernesis/enterprise`	Control-plane identity verification and per-agent grant enforcement for governed user and agent-to-agent requests
`@kybernesis/multiplayer`	Shared Slack conversations with per-speaker identity, attributed thread context, mentionless continuation, DM resets, and verified DM/channel surface helpers
`@kybernesis/buzz`	Membership in a Buzz workspace as a full participant: per-speaker verified identity through the control plane, self-service identity linking, presence, typing and seen signals, image attachments, session continuity across restarts, and projects/issues/PRs/notes as tools
`@kybernesis/evals`	Composable smoke, memory, safety, routing, and optional engineer evaluation suites, plus tool-result helpers
`@kybernesis/engineer`	A vision-verified engineering extension with sandbox screenshot and artifact-delivery tools, build/ship skills, and credential-safe git/branch helpers
`@kybernesis/dispatch`	Declared remote-agent edges and receiver channels with principal forwarding, pinned trusted peers, and optional control-plane-governed discovery and authentication
`@kybernesis/connectors`	Per-principal SaaS and remote MCP tools resolved through the control plane, including multi-account naming and brokered execution
`@kybernesis/local`	Shell, file, search, edit, and local MCP tools relayed to the user's machine through KYBER Studio with declared per-effect consent and optional guards
`@kybernesis/manage`	Authenticated management routes and routine tools for installing capabilities, storing the agent credential, creating or removing schedules, and owner-only setup (model reach, Slack, iMessage line, Link wallet, computer password) on writable agent hosts
`@kybernesis/exe`	exe.dev self-hosting with LLM integration and ChatGPT/Grok subscription models, host preflight and supervision, optional Slack, Photon and Linq (iMessage) bindings, VM sandboxes, and web previews
`@kybernesis/computer`	A persistent, isolated computer per agent (a Docker desktop with Chrome that a person can watch and take over), a computer tool that returns real screenshots, browser open and tab tools, and the rule for when to use it instead of a connector
`@kybernesis/vault`	The person's own logins, cards and addresses, per person and per agent: the agent sees labels only, the control plane holds the secrets, and a fill tool types them into the page on the agent's computer
`@kybernesis/payments`	Stripe Link as the agent's wallet on its owner's behalf, with the person's approval on every purchase and a one-time card typed into checkout on the agent's computer
`@kybernesis/identity`	The agent's `.agent` identity: verification document, signed push tokens, and paired peers as tools
`@kybernesis/notify`	Push notifications to the person's phone when their agent needs them or finishes a turn, through the control plane
`@kybernesis/voice`	Realtime voice for KYBER Studio, the phone and the watch: the voice speaks as the agent and hands every real request to the agent's own session
`@kybernesis/create`	The `kyb` CLI for configurable agent scaffolding, Arcana setup, diagnostics, skill installation, credentialing, registration, deployment, and eval-gated upgrades; `kyb init --host=exe` installs computer and vault by default

Also in this repo

fixtures/ — private, never published. governed-ref is the minimal governed eve agent used as the enterprise package's reference consumer and E2E harness (proved the invite → grant → access → revoke loop against the production control plane); eyes-spike exercises the Docker workshop sandbox.

registry/ — source of https://registry.kybernesis.ai, the shadcn-format eve integration registry serving all of the above. It deploys automatically from master.

eve registry add @kybernesis=https://registry.kybernesis.ai/r/{name}.json
eve add @kybernesis/arcana
eve add @kybernesis/enterprise
eve add @kybernesis/computer
eve add @kybernesis/vault
eve add @kybernesis/evals

docs/ — HANDOFF.md is the repo map and fresh-machine setup; gaps.md is the honest ledger of what is verified, what is built-but-never-run, and what is missing. Read it before promising anything to a client.

Related, not in this repo

Control plane (KybernesisAI/kybernesis-admin, prod: agent.kybernesis.ai) — the issuer/governance service the enterprise package verifies against, and the broker for connectors and local access.
Kyber (KybernesisAI/kyber) — our own production company agent: the reference deployment that dogfoods every package here via published versions.
KYBER Studio (KybernesisAI/kyber-studio) — the desktop client. Signed, notarized, self-updating; the consumer of local, connectors, manage, vault, computer and voice.
KYBER Studio Mobile (KybernesisAI/kyber-studio-mobile) — the same client on iOS and Android (Expo), and the receiver for notify.
Sid (KybernesisAI/sid) — the off-Vercel reference deployment (exe.dev, iMessage, a Grok subscription). If something works there, it works at a client.

Development

Node 24 is required (eve refuses older Node).

npm install
npm run build        # builds every package
npm run typecheck
npm test
node scripts/check-registry.mjs

Every package is built against one eve line: eve is a peer dependency scoped to that line (>=0.81.1 <0.82.0) with the exact certified version (0.81.1, the same as EVE_VERSION in packages/create/src/util.ts) in devDependencies. Moving to a new eve is a deliberate, eval-gated certification, not a version bump.

Publishing: bump the package version (scripts/prepublish.mjs refuses a version already on npm), run node scripts/check-eve-line.mjs, then publish with the npm account's browser 2FA. Update the registry item if install-time files changed and push to master. The consuming agent's eval suite gates every release.

History note: these packages were originally developed inside the Kyber agent monorepo (KybernesisAI/kyber) and extracted here 2026-08-05; pre-extraction history lives there and in the retired per-package mirrors (arcana-eve, enterprise-eve).

@kybernesis/arcana

ianborders

Kybernesis Arcana long-term memory for eve agents: MCP connection, memory skills, and recall-first instructions. Mount once per brain.

Knowledge Memory

Add to Cursor Add to VS Code Run on PlugMCP

GitHub npm Website

Add to Cursor Add to VS Code Run on PlugMCP

1{2  "mcpServers": {3    "kybernesis-arcana": {4      "command": "npx",5      "args": [6        "-y",7        "@kybernesis/[email protected]"8      ]9    }10  }11}

.cursor/mcp.jsonMCP server

Transport: stdio
Status: Local

Power your agent

Add this server

The publisher's own command. Not a PlugMCP endpoint.

Add to Cursor Add to VS Code Run on PlugMCP

Host a copy with our keys and logs.

Local command

npx -y @kybernesis/[email protected]

Claude Code has no install link for a local command. Copy the command below and run it in a terminal.

shClaude Code

1claude mcp add kybernesis-arcana -- npx -y @kybernesis/arcana@0.7.0

Run in a terminal.

jsonClaude Desktop

1{2  "mcpServers": {3    "kybernesis-arcana": {4      "command": "npx",5      "args": [6        "-y",7        "@kybernesis/[email protected]"8      ]9    }10  }11}

claude_desktop_config.json

Local · npmPublisher installStep-by-step: add this in Claude

Remote URL or a command on your machine? How the two installs differ

Run on PlugMCP

Host a copy with our keys and logs.

A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.

Launch

Server facts

Local

Transport: stdio
Version: 0.7.0
Last checked: 2026-10-28

Stars: —
Tools: —
Uptime: —

Tools

No tool list yet. Remote servers get one after the first health check.

FAQ

Questions

How do I install @kybernesis/arcana?

Copy the stdio config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.

Does @kybernesis/arcana need an API key?

No required environment variable is listed on this record.

What transport does @kybernesis/arcana use?

@kybernesis/arcana runs locally over stdio.

When was @kybernesis/arcana last checked?

Last checked 2026-10-28. Kybernesis Arcana long-term memory for eve agents: MCP connection, memory skills, and recall-first instructions. Mount once per brain.

From the publisher

Documentation

Kybernesis Platform

The product monorepo for Kybernesis — the ecosystem layer that makes eve agent deployments enterprise-ready and uniquely Kybernesis. Eve is the plumbing; this is the moat.

Packages (all Apache-2.0, published to npm)

Package	What it gives an agent
`@kybernesis/arcana`	Durable Arcana memory through an MCP connection, recall/remember/brain-note skills, per-session workspace selection, and recall-first instructions
`@kybernesis/enterprise`	Control-plane identity verification and per-agent grant enforcement for governed user and agent-to-agent requests
`@kybernesis/multiplayer`	Shared Slack conversations with per-speaker identity, attributed thread context, mentionless continuation, DM resets, and verified DM/channel surface helpers
`@kybernesis/buzz`	Membership in a Buzz workspace as a full participant: per-speaker verified identity through the control plane, self-service identity linking, presence, typing and seen signals, image attachments, session continuity across restarts, and projects/issues/PRs/notes as tools
`@kybernesis/evals`	Composable smoke, memory, safety, routing, and optional engineer evaluation suites, plus tool-result helpers
`@kybernesis/engineer`	A vision-verified engineering extension with sandbox screenshot and artifact-delivery tools, build/ship skills, and credential-safe git/branch helpers
`@kybernesis/dispatch`	Declared remote-agent edges and receiver channels with principal forwarding, pinned trusted peers, and optional control-plane-governed discovery and authentication
`@kybernesis/connectors`	Per-principal SaaS and remote MCP tools resolved through the control plane, including multi-account naming and brokered execution
`@kybernesis/local`	Shell, file, search, edit, and local MCP tools relayed to the user's machine through KYBER Studio with declared per-effect consent and optional guards
`@kybernesis/manage`	Authenticated management routes and routine tools for installing capabilities, storing the agent credential, creating or removing schedules, and owner-only setup (model reach, Slack, iMessage line, Link wallet, computer password) on writable agent hosts
`@kybernesis/exe`	exe.dev self-hosting with LLM integration and ChatGPT/Grok subscription models, host preflight and supervision, optional Slack, Photon and Linq (iMessage) bindings, VM sandboxes, and web previews
`@kybernesis/computer`	A persistent, isolated computer per agent (a Docker desktop with Chrome that a person can watch and take over), a computer tool that returns real screenshots, browser open and tab tools, and the rule for when to use it instead of a connector
`@kybernesis/vault`	The person's own logins, cards and addresses, per person and per agent: the agent sees labels only, the control plane holds the secrets, and a fill tool types them into the page on the agent's computer
`@kybernesis/payments`	Stripe Link as the agent's wallet on its owner's behalf, with the person's approval on every purchase and a one-time card typed into checkout on the agent's computer
`@kybernesis/identity`	The agent's `.agent` identity: verification document, signed push tokens, and paired peers as tools
`@kybernesis/notify`	Push notifications to the person's phone when their agent needs them or finishes a turn, through the control plane
`@kybernesis/voice`	Realtime voice for KYBER Studio, the phone and the watch: the voice speaks as the agent and hands every real request to the agent's own session
`@kybernesis/create`	The `kyb` CLI for configurable agent scaffolding, Arcana setup, diagnostics, skill installation, credentialing, registration, deployment, and eval-gated upgrades; `kyb init --host=exe` installs computer and vault by default

Also in this repo

fixtures/ — private, never published. governed-ref is the minimal governed eve agent used as the enterprise package's reference consumer and E2E harness (proved the invite → grant → access → revoke loop against the production control plane); eyes-spike exercises the Docker workshop sandbox.

registry/ — source of https://registry.kybernesis.ai, the shadcn-format eve integration registry serving all of the above. It deploys automatically from master.

eve registry add @kybernesis=https://registry.kybernesis.ai/r/{name}.json
eve add @kybernesis/arcana
eve add @kybernesis/enterprise
eve add @kybernesis/computer
eve add @kybernesis/vault
eve add @kybernesis/evals

docs/ — HANDOFF.md is the repo map and fresh-machine setup; gaps.md is the honest ledger of what is verified, what is built-but-never-run, and what is missing. Read it before promising anything to a client.

Related, not in this repo

Control plane (KybernesisAI/kybernesis-admin, prod: agent.kybernesis.ai) — the issuer/governance service the enterprise package verifies against, and the broker for connectors and local access.
Kyber (KybernesisAI/kyber) — our own production company agent: the reference deployment that dogfoods every package here via published versions.
KYBER Studio (KybernesisAI/kyber-studio) — the desktop client. Signed, notarized, self-updating; the consumer of local, connectors, manage, vault, computer and voice.
KYBER Studio Mobile (KybernesisAI/kyber-studio-mobile) — the same client on iOS and Android (Expo), and the receiver for notify.
Sid (KybernesisAI/sid) — the off-Vercel reference deployment (exe.dev, iMessage, a Grok subscription). If something works there, it works at a client.

Development

Node 24 is required (eve refuses older Node).

npm install
npm run build        # builds every package
npm run typecheck
npm test
node scripts/check-registry.mjs