@groundfloorcloud/mcp 0.1.4 → 0.1.5

package/README.md

@@ -7,6 +7,9 @@ They are not replacements. Sign in with `gf`; the MCP reads that session and
 docs so the agent knows *what is in the workspace* and *which `gf` command to
 run*.
 
+Use this package (`@groundfloorcloud/mcp`). Do **not** install
+`@groundfloor/coderunner-mcp` — it is not published and is not the product MCP.
+
 ## How the MCP gets context
 
 | Source | What it answers |
@@ -18,11 +21,11 @@ run*.
 
 Switch workspace: `gf workspaces use <uuid>` (then MCP sees it). Expired session: `gf login` again.
 
-## Cursor config
+## Config
 
 `gf` must be on `PATH` and you must have run `gf login` (and usually `gf workspaces use`).
 
-Clients that spawn a real Node (Claude Code, some IDEs) can use:
+Clients that spawn a real Node (Claude Code, Codex, many IDEs) can use:
 
 ```json
 {
@@ -35,6 +38,8 @@ Clients that spawn a real Node (Claude Code, some IDEs) can use:
 }
 ```
 
+The Shell starter-kit ships this as `.mcp.json`.
+
 **Cursor on macOS:** do not use bare `npx`. Cursor runs npm with its bundled Node, which then looks for `Cursor.app/.../resources/lib` and fails with `ENOENT`. Install the package with *your* Node, then point MCP at that binary:
 
 ```bash

package/dist/index.js

@@ -841,7 +841,7 @@ async function resolveCoderunnerId(apiUrl, workspaceId, idOrSlug) {
 }
 var server = new McpServer({
   name: "groundfloor",
-  version: "0.1.4"
+  version: "0.1.5"
 });
 server.tool(
   "whoami",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@groundfloorcloud/mcp",
-  "version": "0.1.4",
+  "version": "0.1.5",
   "description": "Groundfloor MCP — inspect workspace state and docs; take actions with the gf CLI.",
   "type": "module",
   "bin": {