@ai-ecoverse/mcpcat 0.31.17 → 0.31.19
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/dist/host/mcpcat.mjs +327 -62
- package/dist/kernel/mcpcat.mjs +327 -62
- package/dist/skills/mcpcat/SKILL.md +1 -1
- package/package.json +5 -5
|
@@ -63,7 +63,7 @@ mcpcat import ~/.cursor/mcp.json
|
|
|
63
63
|
mcpcat login docs
|
|
64
64
|
```
|
|
65
65
|
|
|
66
|
-
`login` runs the OAuth sign-in for a server that needs one; `logout` removes its tokens. With slicc-jerk installed, tokens live in jerk: `mcp:<name>` for a server jerk lists from `mcp.json`, and `mcp:url:<url>` for a URL with jerk 0.19.0 or newer.
|
|
66
|
+
`login` runs the OAuth sign-in for a server that needs one; `logout` removes its tokens. With slicc-jerk installed, tokens live in jerk: `mcp:<name>` for a server jerk lists from `mcp.json`, and `mcp:url:<url>` for a URL with jerk 0.19.0 or newer. `login` uses jerk create only when jerk is ≥ 1.4.1; an older jerk falls back to mcpcat's own sign-in (pi's `mcp-auth.json`) while reads and `logout` still use jerk. Pass `--no-jerk` (or set `MCPCAT_NO_JERK=1`) to skip jerk for login and later commands. See `mcpcat login --help`.
|
|
67
67
|
|
|
68
68
|
In seven, `login` refuses: sign in under Settings › MCP servers. mcpcat never holds a token there: for a server with no `Authorization` header, root asks the vault for the placeholder on each request, and needs no jerk. Don't add that header to `mcp.json` yourself. Only root gets the placeholder of a Settings sign-in: as another user a 401 exits 4, the agent already has that server's tools, and a human can use it from a panel terminal as root. As root, a 401 with no placeholder exits 4 and points to Settings, unless the vault didn't answer, which the message says. If the vault holds several sign-ins for one server, mcpcat exits 4: keep one under Settings. jerk is optional: seven doesn't preinstall it. Where it's installed, it's asked with `jerk mcp:<name> get` by non-root users, and by root when the vault can't answer. A 401 after a placeholder went out exits 4 without a retry and doesn't mean you must sign in: the vault fills the placeholder in when the request is forwarded, so either that forwarding isn't active in this seven yet or the server rejected the credential. Try again from the Settings page's Connect, or ask whoever runs seven. A 403 points to Settings too, with the required scope if the server names one. If the request carries its own `Authorization` header, the message says the server rejected it.
|
|
69
69
|
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@ai-ecoverse/mcpcat",
|
|
3
|
-
"version": "0.31.
|
|
3
|
+
"version": "0.31.19",
|
|
4
4
|
"description": "A curl for the Model Context Protocol",
|
|
5
5
|
"type": "module",
|
|
6
6
|
"license": "Apache-2.0",
|
|
@@ -58,16 +58,16 @@
|
|
|
58
58
|
"trust:dry": "npx fledgling sync --dry-run -y --skip-publish"
|
|
59
59
|
},
|
|
60
60
|
"devDependencies": {
|
|
61
|
-
"@ai-ecoverse/slicc-kernel": "1.
|
|
61
|
+
"@ai-ecoverse/slicc-kernel": "1.174.0",
|
|
62
62
|
"@ai-ecoverse/slicc-shared-web": "2.13.10",
|
|
63
|
-
"@ai-ecoverse/slicc-vault": "1.
|
|
63
|
+
"@ai-ecoverse/slicc-vault": "1.22.0",
|
|
64
64
|
"@biomejs/biome": "2.6.3",
|
|
65
65
|
"@earendil-works/pi-codemode": "1.4.0",
|
|
66
66
|
"@earendil-works/pi-mcp": "1.4.0",
|
|
67
|
-
"@types/node": "26.6.
|
|
67
|
+
"@types/node": "26.6.6",
|
|
68
68
|
"esbuild": "0.28.2",
|
|
69
69
|
"lefthook": "2.2.2",
|
|
70
|
-
"monocart-coverage-reports": "3.
|
|
70
|
+
"monocart-coverage-reports": "3.2.0",
|
|
71
71
|
"proper-lockfile": "4.1.2",
|
|
72
72
|
"quickjs-wasi": "3.6.3",
|
|
73
73
|
"semantic-release": "25.0.9",
|