Module setup 

scone setup <client>: plug and play (gap-analysis P1). Zero questions: detect the binary, write the config, say what happened.

Structs

Client

A client scone can register itself with by editing a config file.

Enums

Shape

How a client spells “here is a stdio MCP server”. The clients agree on the idea and disagree on every detail, so the shape is data.

Constants

CLIENTS

Every client whose config layout we have verified. Adding one is a row here, not a new code path.

Functions

client_by_name

desktop_config_path

merged_desktop_config

Merge scone’s MCP server entry into a Claude Desktop config, preserving everything already there. Pure function, unit-tested.

merged_json_config

Merge scone into any JSON-shaped client config, preserving everything already there (other servers, unrelated settings, user edits). Pure function, unit-tested against every shape.

merged_settings_hooks

Merge scone’s hook wiring into a Claude Code settings.json, preserving everything else. Pure function, unit-tested.

merged_toml_config

Merge scone into Codex CLI’s TOML config, preserving the rest of the file’s tables. Pure function, unit-tested.

setup_claude_code

setup_claude_code_hooks

Wire this project’s .claude/settings.json to the scone hook handlers.

setup_claude_desktop

setup_client

Register scone with any known client: read what is there, merge, write back. Never clobbers a config it cannot parse.