MCP, hooks and skills

MCP servers

Create one server body in config/mcp.d/catalog.yaml:

enabled: true
required: false
transport: http
url: https://mcp.example.com
bearer_token_env: NOOKINS_CATALOG_TOKEN

Replace the example endpoint with a reviewed server. Put the referenced token in your private secrets.env, never in YAML or chat. Streamable HTTP requires HTTPS except for loopback. Stdio servers are managed processes with an empty environment and explicitly mapped secrets. Nookins owns transport timeouts.

Enable the agent's mcp feature only for the appropriate audience:

features:
  mcp:
    audience: owner_only

Merge this into the existing features map; do not create a duplicate YAML key. Configuring the server alone does not grant imported tools. Validate/preview/apply, check capability readiness, then test a harmless read through the intended agent. A server connection error is not permission to relax authorization or expose a local endpoint publicly.

WASI hooks

Hooks observe events and emit bounded diagnostics. Put a reviewed module under the selected home's extensions/hooks/, then define its actual module name, SHA-256 and events in config/hooks.d/audit.yaml:

enabled: true
module: audit.wasm
sha256: 0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef
events: [management.proposal.review_requested]

The digest above is a placeholder; compute the real module digest. Hooks cannot read Nookins files or environment, open network sockets, or invoke tools. Nookins owns their fuel budget. For actions triggered by events, use automations. Disable a hook by setting enabled: false and applying the reviewed configuration.

Skills and reference corpora

Skills contain instructions and name their capability dependencies. They do not install packages or grant permissions. Installed packages may include immutable text/reference corpora; an agent needs the corresponding attachment and authority to use them. Review source and redistribution rights for imported material.

Every agent has version-matched Nookins self-documentation through the built-in understand_nookins skill and nookins_runtime_docs corpus. Ask it to explain the running version's capabilities or settings. Nookins.self.inspect reports documentation readiness; missing or corrupt documentation is not served as a stale version. Public website documentation supplements this local version-matched reference.

Optional workspace tools

Files, downloads and execution are explicit agent workspace capabilities. Networked execution requires execution and an allowed-domain list. Enabling a tool may download a verified optional workspace component; check capability status and asset commands rather than assuming the base installer includes every runtime.

Keep provider logins, messaging pairing, browser sessions and extension secrets separate. Each integration has its own authorization and lifecycle.