@florent-uzio/custody-mcp 0.1.0 → 0.1.2
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 +17 -9
- package/dist/custody-mcp.js +3 -3
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -10,38 +10,46 @@ The server speaks only the 2026-07-28 MCP protocol (the one `@mastra/mcp` 2.x se
|
|
|
10
10
|
|
|
11
11
|
## Use it from your MCP client
|
|
12
12
|
|
|
13
|
-
|
|
13
|
+
The server runs with `npx`, so there is nothing to clone or build. In Claude Code, add it for all your projects with:
|
|
14
|
+
|
|
15
|
+
```sh
|
|
16
|
+
claude mcp add custody --scope user -- npx -y @florent-uzio/custody-mcp@latest
|
|
17
|
+
```
|
|
18
|
+
|
|
19
|
+
For other clients, add it to the client's MCP config:
|
|
14
20
|
|
|
15
21
|
```json
|
|
16
22
|
{
|
|
17
23
|
"mcpServers": {
|
|
18
24
|
"custody": {
|
|
19
25
|
"command": "npx",
|
|
20
|
-
"args": ["-y", "@florent-uzio/custody-mcp"]
|
|
26
|
+
"args": ["-y", "@florent-uzio/custody-mcp@latest"]
|
|
21
27
|
}
|
|
22
28
|
}
|
|
23
29
|
}
|
|
24
30
|
```
|
|
25
31
|
|
|
32
|
+
`@latest` makes `npx` check npm each time the client starts the server, so you get new releases on your next client restart instead of a copy cached by `npx`. To stay on one version, pin it instead, e.g. `@florent-uzio/custody-mcp@0.1.0`.
|
|
33
|
+
|
|
26
34
|
The server needs at least one **Environment**: a Ripple Custody instance together with the credentials of your Custody user on it. Set one up with the setup CLI below.
|
|
27
35
|
|
|
28
36
|
## Setup CLI
|
|
29
37
|
|
|
30
38
|
The same `custody-mcp` command, run with a subcommand, manages your Environments. With no subcommand it starts the MCP server.
|
|
31
39
|
|
|
32
|
-
| Command
|
|
33
|
-
|
|
|
34
|
-
| `npx @florent-uzio/custody-mcp add-env <name>` | Sets up a new Environment, step by step. |
|
|
35
|
-
| `npx @florent-uzio/custody-mcp list-envs` | Shows every Environment and where its key is stored (never the key). |
|
|
36
|
-
| `npx @florent-uzio/custody-mcp remove-env <name>` | Removes an Environment from the config file. |
|
|
37
|
-
| `npx @florent-uzio/custody-mcp set-default <name>` | Makes an Environment the one read tools use when a call names none. |
|
|
40
|
+
| Command | What it does |
|
|
41
|
+
| --------------------------------------------------------- | -------------------------------------------------------------------- |
|
|
42
|
+
| `npx @florent-uzio/custody-mcp@latest add-env <name>` | Sets up a new Environment, step by step. |
|
|
43
|
+
| `npx @florent-uzio/custody-mcp@latest list-envs` | Shows every Environment and where its key is stored (never the key). |
|
|
44
|
+
| `npx @florent-uzio/custody-mcp@latest remove-env <name>` | Removes an Environment from the config file. |
|
|
45
|
+
| `npx @florent-uzio/custody-mcp@latest set-default <name>` | Makes an Environment the one read tools use when a call names none. |
|
|
38
46
|
|
|
39
47
|
Changes take effect straight away: the server re-reads the config file on every tool call, so you do not need to restart your AI client.
|
|
40
48
|
|
|
41
49
|
### `add-env <name>`
|
|
42
50
|
|
|
43
51
|
```sh
|
|
44
|
-
npx @florent-uzio/custody-mcp add-env dev
|
|
52
|
+
npx @florent-uzio/custody-mcp@latest add-env dev
|
|
45
53
|
```
|
|
46
54
|
|
|
47
55
|
It walks you through these steps:
|