@scribed/cli 0.1.28 → 0.1.30
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 +15 -1
- package/dist/index.js +897 -255
- package/dist/mcp/server.js +795 -183
- package/package.json +3 -3
package/README.md
CHANGED
|
@@ -2,7 +2,7 @@
|
|
|
2
2
|
|
|
3
3
|
Command-line client + MCP server for Scribed — CRM records, phone + texting, inbox, calendar + booking, transcriptions, HR, the Vault + workspace pages, and automations from the terminal or from an MCP host such as Cursor or Claude. The entire domain surface is **derived from the scribed-agent tool catalog**: nothing is hand-duplicated, so a new eligible catalog tool automatically becomes a CLI command (`scribed call <tool>`) and an MCP tool.
|
|
4
4
|
|
|
5
|
-
Verified catalog (2026-10-18): **1,
|
|
5
|
+
Verified catalog (2026-10-18): **1,110 external tools across 48 categories**;
|
|
6
6
|
581 tools in 28 categories are included in the default core set. Route
|
|
7
7
|
coverage does not imply full UI parity: session-only actions and the remaining
|
|
8
8
|
option audit are tracked in the repository's `output/ui-parity/` reports.
|
|
@@ -156,6 +156,20 @@ scribed signup --resume --email you@example.com --phone-code <code> --json
|
|
|
156
156
|
|
|
157
157
|
Google/Apple consent stays in the browser: run `scribed login`, choose **Sign up**, complete the wizard, and then authorize the CLI. Browser login never collects signup details in the terminal. Subsequent onboarding tools remain limited by their API authorization; the offline signup lifecycle test does not prove live onboarding apply.
|
|
158
158
|
|
|
159
|
+
### Connect a provider
|
|
160
|
+
|
|
161
|
+
```bash
|
|
162
|
+
scribed call integration_connect_start provider=google-calendar
|
|
163
|
+
```
|
|
164
|
+
|
|
165
|
+
Open the returned Scribed link in your signed-in browser and complete the
|
|
166
|
+
provider's consent flow. Then call the returned status tool with its exact
|
|
167
|
+
arguments and check any provider-specific completion conditions. Preparing the
|
|
168
|
+
link does not connect an account. Workspace-owned providers require an explicit
|
|
169
|
+
workspace and the existing admin permissions; Runs cannot start a handoff.
|
|
170
|
+
Supported providers come from the canonical schema. Credentials, payments and
|
|
171
|
+
other consent flows retain their separately documented human steps.
|
|
172
|
+
|
|
159
173
|
### Credentials and environment
|
|
160
174
|
|
|
161
175
|
Credentials live in `${XDG_CONFIG_HOME:-~/.config}/scribed/config.json` (directory `0700`, file `0600`, atomically replaced). Environment overrides for CI always win over the file:
|