grain-tools 0.10.8 → 0.10.11

package/README.md

@@ -105,38 +105,41 @@ named connection profile when you open **Grain: Show Welcome Guide** or
 
 ## Quick Start: MCP Agents
 
-### One command
+### Install once, then connect every client
 
 ```
-npx -y grain-tools --stdio
+grain --stdio
 ```
 
-That is the command every MCP client is given, on every platform. There is no
-second setup path.
+This is the normal command for an installed Grain setup on every platform. It
+attaches to the shared local Grain service when that service is available, so
+connections and result tabs stay shared. If the service cannot be reached, the
+bridge reports isolated mode and its sessions do not appear in the editor.
 
 1. Run **Grain: Manage Connections** and confirm your active connection.
 2. Open the Grain settings panel and **enable the MCP server** (`grain.mcpEnabled`).
    This is required and ships **off** — the daemon serves no MCP surface until you turn it on.
 3. Keep safe mode enabled unless you explicitly want agents to run mutating SQL.
 4. Give your client the command:
-   - **Claude Code**: `claude mcp add grain -- npx -y grain-tools --stdio`
+   - **Claude Code**: `claude mcp add grain -- grain --stdio`
    - **Cursor**: Settings → MCP Servers → Add new MCP server, type `command`,
-     command `npx -y grain-tools --stdio`
-   - **VS Code**: open the Extensions view, search `@mcp Grain`, and install it
-     into your user profile or the current workspace — the gallery entry carries
-     the command
+     command `grain --stdio`
+   - **VS Code**: add `grain --stdio` through **MCP: Open User Configuration**;
+     VS Code uses a `servers` key rather than `mcpServers`
    - **Claude Desktop and other file-configured clients**: see
      [the setup guide](docs/engineering/guides/mcp-client-setup.md), which
      transcribes the same command into that client's config file
 
-This bridges to the daemon the VS Code extension is already running, so agent
-queries and sessions show up in the results grid alongside anything you run from
-the editor. It works with every MCP client — including ones that cannot send
+This bridges to the shared Grain service, so agent queries and sessions show up
+in the results grid alongside anything you run from the editor. It works with
+every MCP client — including ones that cannot send
 custom HTTP headers, such as Claude Desktop — and it needs no credential in your
 config, because the bridge reads the daemon's access token itself.
 
-`-y` is not decoration: an MCP client starts the server with no terminal
-attached, so npm's install prompt would have nobody to answer it.
+To try Grain without installing it, use `npx -y grain-tools --stdio`. This
+requires Node.js and may run in isolated mode when no shared Grain service is
+available, so it is a trial and headless path rather than the recommended
+desktop setup.
 
 Enabling `grain.mcpEnabled` in the Grain settings panel is required
 for this stdio bridge too. Launching the bridge without it produces a clear
@@ -199,7 +202,7 @@ command carries its own connection profiles through the environment:
 
 ```bash
 GRAIN_CONNECTIONS='[{"id":"analytics","name":"Analytics","type":"postgres","host":"localhost","port":5432,"user":"analyst","database":"warehouse","password":"YOUR_PASSWORD"}]' \
-  npx -y grain-tools --stdio
+  grain --stdio --embedded
 ```
 
 The same variable goes in an `env` block for a file-configured client; see