@subseam/mcp 0.3.1
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 +28 -0
- package/dist/main.js +45767 -0
- package/package.json +46 -0
package/README.md
ADDED
|
@@ -0,0 +1,28 @@
|
|
|
1
|
+
# @subseam/mcp
|
|
2
|
+
|
|
3
|
+
The subseam MCP server. It is published to the public npm registry and installed from
|
|
4
|
+
there like any other npm package.
|
|
5
|
+
|
|
6
|
+
## Install
|
|
7
|
+
|
|
8
|
+
```
|
|
9
|
+
packages/mcp/install.sh # into ~/.subseam/mcp
|
|
10
|
+
packages/mcp/install.sh <dir> <version>
|
|
11
|
+
```
|
|
12
|
+
|
|
13
|
+
The script runs `npm install @subseam/mcp@<version>` in the host directory and prints the
|
|
14
|
+
`claude mcp add-json` line to register the server. Then `claude mcp list` shows
|
|
15
|
+
`subseam ... Connected`.
|
|
16
|
+
|
|
17
|
+
The equivalent by hand:
|
|
18
|
+
|
|
19
|
+
```
|
|
20
|
+
npm install @subseam/mcp@0.3.1
|
|
21
|
+
claude mcp add-json --scope user subseam '{"command":"node","args":["<dir>/node_modules/@subseam/mcp/dist/main.js"],"env":{"SUBSEAM_URL":"https://api.example.subseam.com","SUBSEAM_TENANT":"<your tenant id>"}}'
|
|
22
|
+
```
|
|
23
|
+
|
|
24
|
+
No credential is needed to install: the package is public. `SUBSEAM_URL` above is a
|
|
25
|
+
placeholder — use your own subseam API URL and tenant id.
|
|
26
|
+
|
|
27
|
+
If the install fails, npm's own error is what you see: an `E404` means that version is not
|
|
28
|
+
on the registry, and `install.sh` stops there rather than continuing.
|