@subseam/mcp 0.4.14 → 0.4.15

package/README.md

@@ -13,7 +13,7 @@ and the rest. It runs on your machine and talks to the subseam service over HTTP
 
 - Node.js 22 or later, and npm.
 - A GitHub account, and a subseam organization that someone has added you to.
-- The subseam API URL: `https://subseam.theconstructory.com/subseam`.
+- The subseam URL: `https://subseam.theconstructory.com`.
 
 ## 1. Sign in
 
@@ -23,27 +23,17 @@ owner your GitHub login so they can add you.
 
 ## 2. Get a token
 
-The MCP server authenticates with a token tied to your account. There is no token page yet, so
-you mint one with your browser session:
-
-1. In the browser where you signed in, open the developer tools, then Application (Storage in
-   Firefox) → Cookies → `https://subseam.theconstructory.com`, and copy the value of
-   `__Host-subseam_session`.
-2. Run, pasting that value:
+The MCP server authenticates with a token tied to your account. Open
+<https://subseam.theconstructory.com/settings>, signed in as in step 1, name the token after the
+machine it is for, and create it. The page shows the token once: copy it, then run
 
 ```
-S='<the cookie value>'; C=$(openssl rand -hex 16)
-mkdir -p ~/.subseam && curl -s -X POST https://subseam.theconstructory.com/tokens \
-  -H "cookie: __Host-subseam_session=$S; subseam_csrf=$C" -H "x-csrf-token: $C" \
-  -H 'content-type: application/json' -d '{"label":"my-machine"}' \
-  | node -e 'let b="";process.stdin.on("data",d=>b+=d).on("end",()=>{let t;try{t=JSON.parse(b).token}catch{}if(typeof t==="string")process.stdout.write(t);else{console.error("subseam refused the token request: "+b);process.exit(1)}})' > ~/.subseam/token
-chmod 600 ~/.subseam/token
+mkdir -p ~/.subseam && umask 077 && printf '%s' '<the token>' > ~/.subseam/token
 ```
 
-`~/.subseam/token` now holds one line starting `cpt_`. If the command prints "subseam refused the
-token request" with the server's answer, the session cookie was wrong or expired: sign in again and
-repeat. The server also accepts the token in the
-`SUBSEAM_TOKEN` environment variable instead of the file.
+`~/.subseam/token` now holds one line starting `cpt_`. The server also accepts the token in the
+`SUBSEAM_TOKEN` environment variable instead of the file. The same page lists your tokens and
+revokes one you no longer use.
 
 ## 3. Install
 
@@ -57,7 +47,7 @@ npm install @subseam/mcp
 For Claude Code:
 
 ```
-claude mcp add-json --scope user subseam '{"command":"node","args":["'"$HOME"'/.subseam/mcp/node_modules/@subseam/mcp/dist/main.js"],"env":{"SUBSEAM_URL":"https://subseam.theconstructory.com/subseam"}}'
+claude mcp add-json --scope user subseam '{"command":"node","args":["'"$HOME"'/.subseam/mcp/node_modules/@subseam/mcp/dist/main.js"],"env":{"SUBSEAM_URL":"https://subseam.theconstructory.com"}}'
 ```
 
 `claude mcp list` should show `subseam ... Connected`. Any other MCP host: run

package/dist/main.js

@@ -24036,7 +24036,7 @@ function requireEnv(env, name, purpose) {
 function loadConfig2(env = process.env, sources = realTokenSources()) {
   return Object.freeze({
     get url() {
-      return requireEnv(env, "SUBSEAM_URL", "to reach the hosted service, e.g. https://subseam.theconstructory.com/subseam");
+      return requireEnv(env, "SUBSEAM_URL", "to reach the hosted service, e.g. https://subseam.theconstructory.com");
     },
     get tenantId() {
       const value = env["SUBSEAM_TENANT"];
@@ -48341,7 +48341,7 @@ var workReadTools = createWorkReadToolProviders({ capability: "work" });
 var bundledProviders = [src_default2, src_default, tension_default, ...defineTools, ...decisionTools, ...captureTools, ...buildTools, secureTool, ...workTools, ...workReadTools];
 
 // package.json
-var version2 = "0.4.14";
+var version2 = "0.4.15";
 
 // src/server.ts
 var SERVER_VERSION = version2;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@subseam/mcp",
-  "version": "0.4.14",
+  "version": "0.4.15",
   "private": false,
   "type": "module",
   "bin": {