Expand description
Library surface of the scone binary (MCP server module).
Modules§
- connectors
- Cloud connectors: pull documents out of the services people already keep their thinking in, and hand them to the engine as episodes.
- hook
scone hook <event>: Claude Code hook handlers, all local, all fail-open. The predecessor’s plugin runs Node scripts with 3-second network caps; ours is the engine binary itself on millisecond budgets (design: docs/superpowers/specs/2026-08-28-team-brain-concept.md).- mcp
- MCP server: persistent memory for any MCP agent (spec §8).
- serve
- Self-hostable HTTP API (spec §8): the same core calls the CLI and MCP make — no privileged path. Every request authenticates with a Bearer key bound to exactly one space (per-key scoping; memory/bugs.md P-1), and bounds mirror the MCP surface (P-4).
- setup
scone setup <client>: plug and play (gap-analysis P1). Zero questions: detect the binary, write the config, say what happened.- web
- URL ingestion (gap-analysis P3): fetch a page, convert to clean markdown locally, feed the engine. Network lives here in the CLI layer; scone-core stays offline by construction.