dataspring-cli 0.4.4__tar.gz → 0.4.5__tar.gz

{dataspring_cli-0.4.4 → dataspring_cli-0.4.5}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: dataspring-cli
-Version: 0.4.4
+Version: 0.4.5
 Summary: DataSpring CLI - Query metrics and manage dashboards from the terminal
 Project-URL: Homepage, https://dataspring.app
 Project-URL: Documentation, https://dataspring.app/docs

{dataspring_cli-0.4.4 → dataspring_cli-0.4.5}/cli/main.py

@@ -94,7 +94,9 @@ class DataSpringGroup(TyperGroup):
 #: exit codes an agent branches on (hub D-99, suite standards §6).
 ROOT_HELP = """DataSpring CLI: query metrics, run the datacore and manage boards from the terminal.
 
-Sign in with `dataspring auth login`. Every command acts in one org: --org, then DATASPRING_ORG or FORSPRING_ORG, then .forspring.json, then the key's own org, then the only stored key; `dataspring whoami` says which. No command changes the org for later ones.
+Sign in with `dataspring auth login`: it prints a code and a link; open the link on any device and approve (works over SSH and in containers too). Every command acts in one org: --org, then DATASPRING_ORG or FORSPRING_ORG, then .forspring.json, then the key's own org, then the only stored key; `dataspring whoami` says which. No command changes the org for later ones.
+
+Agents over MCP need no CLI: `claude mcp add --transport http --scope user dataspring https://dataspring.app/api/mcp/`, then sign in and approve the org in the browser. For CI with no person present: `export DATASPRING_API_KEY=<key>` (a key from the console's "Automation and CI"; it acts in its own org).
 
 A refusal prints `<reason>: <what happened> Fix: <what fixes it>` and exits 4 (not_signed_in, product_off, org_suspended, role_too_low, org_mismatch), 3 (not_a_member), 2 (org_required) or 1 (account_unavailable: retry). Any other failure exits 1, a usage error 2, a removed command 64."""
 
@@ -593,17 +595,25 @@ def auth_login(
     no_browser: Annotated[bool, typer.Option("--no-browser", help="Do not try to open a browser; just print the URL")] = False,
     all_orgs: Annotated[bool, typer.Option("--all-orgs", help="Ask for a key in every org you belong to, not only the one you approve (the browser says so)")] = False,
 ):
-    """Sign in with the device flow: approve in any browser where you are signed in with your Forspring account.
+    """Sign in: the CLI prints a code and a link; open the link on any device and approve.
 
-    Prints the URL and the code at once (also when the output is redirected,
-    so an agent can run it in the background and hand both to a person),
-    then waits for the approval. Mints an ordinary API key labelled 'CLI on
-    <hostname>' for the org you approve (one per org you are in with
-    --all-orgs), stored in ~/.dataspring/credentials.json.
+    It works over SSH and in containers too: the machine running the CLI
+    needs no browser. The URL and the code are printed at once (also when the
+    output is redirected, so an agent can run it in the background and hand
+    both to a person), then it waits for the approval. Mints an ordinary API
+    key labelled 'CLI on <hostname>' for the org you approve (one per org you
+    are in with --all-orgs), stored in ~/.dataspring/credentials.json.
 
     Logging in picks no org for later commands: with more than one key
     stored, name it per command (--org, DATASPRING_ORG, .forspring.json).
-    DATASPRING_API_KEY, when set, always wins over the stored keys.
+
+    Automation and CI, with no person present: export DATASPRING_API_KEY=<key>
+    (a key made in the console's connect page, under "Automation and CI"); it
+    always wins over the stored keys and acts in its own org. --key stores
+    such a key instead.
+
+    Agents over MCP do not need this: claude mcp add --transport http
+    --scope user dataspring https://dataspring.app/api/mcp/
     """
     try:
         if key:

{dataspring_cli-0.4.4 → dataspring_cli-0.4.5}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "dataspring-cli"
-version = "0.4.4"
+version = "0.4.5"
 description = "DataSpring CLI - Query metrics and manage dashboards from the terminal"
 readme = "README.md"
 requires-python = ">=3.12"

{dataspring_cli-0.4.4 → dataspring_cli-0.4.5}/skills/dataspring-author/SKILL.md

@@ -21,8 +21,10 @@ at once (run it in the background and hand both to the person), then
 echo '{"org": "acme"}' > .forspring.json && dataspring whoami --json
 ```
 
-MCP: one connection per org, `https://dataspring.app/api/mcp/?org=<org>`, or
-`Authorization: Bearer ds_...` for a headless agent (the key's own org).
+MCP: `claude mcp add --transport http --scope user dataspring
+https://dataspring.app/api/mcp/` (or the same address in any client); the
+person signs in and the consent page names the org, bound to that connection.
+With no person present: `Authorization: Bearer ds_...` (the key's own org).
 
 A refusal leads with a reason and ends with its fix; match the reason. The
 ones you meet while building: `role_too_low` (connections, pipelines,

{dataspring_cli-0.4.4 → dataspring_cli-0.4.5}/skills/dataspring-consume/SKILL.md

@@ -8,8 +8,8 @@ description: How to query DataSpring correctly to answer analytical questions. U
 You are querying DataSpring. Three surfaces are available — pick the
 one the caller is using:
 
-- **MCP** — agent connected to a DataSpring MCP server (Claude
-  Desktop, Claude Code via stdio, etc.). Tool calls.
+- **MCP** — agent connected to DataSpring's MCP server (Claude.ai,
+  Claude Code, Cursor, etc.). Tool calls.
 - **CLI** — `dataspring` from the terminal. Shell commands.
 - **REST** — direct HTTP. Scripts, integrations.
 
@@ -80,11 +80,18 @@ which role, is the account's answer on every request. DataSpring has no
   parent. `DATASPRING_API_KEY=ds_...` (CI) acts in the key's own org.
   `dataspring whoami --json` says which org a command here acts in and why
   (`org_from`). There is no command that switches org for later commands.
-- **MCP.** One connection per org: `https://dataspring.app/api/mcp/?org=<org>`
-  (the slash before `?` is required), signed in with the Forspring account.
-  To work in two orgs, add two connections; no tool moves a connection. A
-  headless agent connects to the same URL with `Authorization: Bearer ds_...`;
-  the key acts in its own org, and `?org=` may only repeat it.
+- **MCP.** The address is `https://dataspring.app/api/mcp/`, with no org
+  in it. Claude Code: `claude mcp add --transport http --scope user
+  dataspring https://dataspring.app/api/mcp/`, then `/mcp` → *Authenticate*
+  (`claude mcp login dataspring` with no browser); Claude.ai: *Customize →
+  Connectors* → *Add custom connector* with that URL. The person signs in
+  with their Forspring account and DataSpring's consent page names the org
+  the connection works in (their only one, or the one they choose); the
+  choice is bound to the connection. To work in two orgs, add two
+  connections; no tool moves a connection. With no person present (CI), the
+  same address takes `Authorization: Bearer ds_...` (a key made in the
+  console's connect page, under "Automation and CI"): the key acts in its
+  own org, and `?org=` may only repeat it.
 - **REST.** `Authorization: Bearer ds_...`; the key is the org.
 
 Never pick an org for the person. When the org is ambiguous you are refused
@@ -595,12 +602,12 @@ the reason, never on the prose, and pass the fix on verbatim.
 | Reason | CLI exit | What you do |
 |---|---|---|
 | `not_signed_in` | 4 | CLI: run `dataspring auth login` and hand the person its URL and code. MCP: reconnect and sign in. Never ask for a password or a key in chat. |
-| `org_required` | 2 | Several orgs, none named. Ask the person which one (the refusal lists them); then `--org`, `DATASPRING_ORG` or `.forspring.json`. Never guess. |
+| `org_required` | 2 | Several orgs, none named. Ask the person which one (the refusal lists them); then `--org`, `DATASPRING_ORG` or `.forspring.json`. MCP: they reconnect and choose it on the consent page. Never guess. |
 | `not_a_member` | 3 | Check the org id's spelling against the list. Otherwise only an owner or admin of that org can add the person, at the Forspring account; say so and stop. |
 | `product_off` | 4 | DataSpring is not switched on for this person in that org. Tell them who can switch it on (`contacts`, `fix_url`); do not retry. |
 | `org_suspended` | 4 | Billing stopped DataSpring for the whole org. Tell them an owner can restart it on the billing page; do not retry. |
 | `role_too_low` | 4 | Their role cannot do this. Offer what it can do (a personal preference or quick metric instead of an org-wide change), or name the role needed. |
-| `org_mismatch` | 4 | The key or connection is for another org than the one named. Use that org's key or URL, or drop the conflicting `--org` / `?org=`. |
+| `org_mismatch` | 4 | The key or connection (approved for one org) is for another org than the one named. Use that org's key or connection, or drop the conflicting `--org` / `?org=`. |
 | `account_unavailable` | 1 | Forspring's account did not answer, so access could not be checked. Retry once after a few seconds; nothing changed. |
 
 Other CLI exits: 0 success, 1 any other failure, 2 a usage error, 64 a