@ainyc/canonry 2.5.1 → 2.8.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -58,9 +58,30 @@ canonry agent attach my-project --url https://my-agent.example.com/hooks/canonry
58
58
  Your agent receives `run.completed`, `insight.critical`, `insight.high`, and
59
59
  `citation.gained` notifications. Detach with `canonry agent detach my-project`.
60
60
 
61
+ ### Bringing your own agent (MCP)
62
+
63
+ For MCP clients like Claude Desktop, Cursor, Codex, or custom shells that
64
+ prefer a typed tool catalog over shell commands, Canonry ships a stdio
65
+ adapter. The fastest path is the `canonry mcp install` helper:
66
+
67
+ ```bash
68
+ canonry mcp install --client claude-desktop # or: cursor
69
+ canonry mcp install --client claude-desktop --read-only # 33 read tools only
70
+ canonry mcp config --client codex # print snippet for unsupported clients
71
+ ```
72
+
73
+ `install` merges a `canonry` entry into the client's config, backs up the
74
+ original, and is idempotent. Restart the client after install to pick it up.
75
+
76
+ The adapter exposes 48 tools — projects, runs, snapshots, insights, health,
77
+ keyword and competitor management, schedules, GSC and GA reads, and the
78
+ config-as-code apply path. Auth and configuration are inherited from
79
+ `~/.canonry/config.yaml`. See [`docs/mcp.md`](docs/mcp.md) for the full
80
+ surface and safety rules.
81
+
61
82
  ## How agents use Canonry
62
83
 
63
- Canonry's CLI and API are the agent interface — no special SDK, no MCP layer, no virtual filesystem. Every command supports `--format json`; every dashboard view has a matching API endpoint.
84
+ Canonry's CLI and API are the agent interface. The optional `canonry-mcp` adapter is a thin wrapper over the same public API client — no parallel surface, no virtual filesystem, no privileged SDK. Every CLI command supports `--format json`; every dashboard view has a matching API endpoint.
64
85
 
65
86
  - **Monitor** visibility sweeps across providers on a schedule, tracking citation changes over time
66
87
  - **Analyze** regressions, emerging opportunities, and correlations with site changes
@@ -70,7 +91,7 @@ Canonry's CLI and API are the agent interface — no special SDK, no MCP layer,
70
91
  ## Features
71
92
 
72
93
  - **Built-in AI agent (Aero).** Reads state, analyzes regressions, fires write tools (`run_sweep`, `dismiss_insight`, `update_schedule`, etc.), wakes up unprompted after runs. Backed by [`pi-agent-core`](https://github.com/badlogic/pi-mono) — 15+ LLM providers, streaming first.
73
- - **Agent-first.** Every CLI command supports `--format json`; every UI view has a matching API endpoint.
94
+ - **Agent-first.** Every CLI command supports `--format json`; every UI view has a matching API endpoint. An optional `canonry-mcp` stdio adapter exposes 48 tools to MCP clients like Claude Desktop and Codex.
74
95
  - **Multi-provider.** Query Gemini, OpenAI, Claude, Perplexity, and local LLMs from a single platform.
75
96
  - **Config-as-code.** Kubernetes-style YAML files. Version control your monitoring, let agents apply changes declaratively.
76
97
  - **Self-hosted.** Runs locally with SQLite. No cloud account required.