@getdory/cli 0.1.0
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/LICENSE +201 -0
- package/README.md +258 -0
- package/dist/cli.js +1182414 -0
- package/package.json +67 -0
package/LICENSE
ADDED
|
@@ -0,0 +1,201 @@
|
|
|
1
|
+
Apache License
|
|
2
|
+
Version 2.0, January 2004
|
|
3
|
+
http://www.apache.org/licenses/
|
|
4
|
+
|
|
5
|
+
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
|
|
6
|
+
|
|
7
|
+
1. Definitions.
|
|
8
|
+
|
|
9
|
+
"License" shall mean the terms and conditions for use, reproduction,
|
|
10
|
+
and distribution as defined by Sections 1 through 9 of this document.
|
|
11
|
+
|
|
12
|
+
"Licensor" shall mean the copyright owner or entity authorized by
|
|
13
|
+
the copyright owner that is granting the License.
|
|
14
|
+
|
|
15
|
+
"Legal Entity" shall mean the union of the acting entity and all
|
|
16
|
+
other entities that control, are controlled by, or are under common
|
|
17
|
+
control with that entity. For the purposes of this definition,
|
|
18
|
+
"control" means (i) the power, direct or indirect, to cause the
|
|
19
|
+
direction or management of such entity, whether by contract or
|
|
20
|
+
otherwise, or (ii) ownership of fifty percent (50%) or more of the
|
|
21
|
+
outstanding shares, or (iii) beneficial ownership of such entity.
|
|
22
|
+
|
|
23
|
+
"You" (or "Your") shall mean an individual or Legal Entity
|
|
24
|
+
exercising permissions granted by this License.
|
|
25
|
+
|
|
26
|
+
"Source" form shall mean the preferred form for making modifications,
|
|
27
|
+
including but not limited to software source code, documentation
|
|
28
|
+
source, and configuration files.
|
|
29
|
+
|
|
30
|
+
"Object" form shall mean any form resulting from mechanical
|
|
31
|
+
transformation or translation of a Source form, including but
|
|
32
|
+
not limited to compiled object code, generated documentation,
|
|
33
|
+
and conversions to other media types.
|
|
34
|
+
|
|
35
|
+
"Work" shall mean the work of authorship, whether in Source or
|
|
36
|
+
Object form, made available under the License, as indicated by a
|
|
37
|
+
copyright notice that is included in or attached to the work
|
|
38
|
+
(an example is provided in the Appendix below).
|
|
39
|
+
|
|
40
|
+
"Derivative Works" shall mean any work, whether in Source or Object
|
|
41
|
+
form, that is based on (or derived from) the Work and for which the
|
|
42
|
+
editorial revisions, annotations, elaborations, or other modifications
|
|
43
|
+
represent, as a whole, an original work of authorship. For the purposes
|
|
44
|
+
of this License, Derivative Works shall not include works that remain
|
|
45
|
+
separable from, or merely link (or bind by name) to the interfaces of,
|
|
46
|
+
the Work and Derivative Works thereof.
|
|
47
|
+
|
|
48
|
+
"Contribution" shall mean any work of authorship, including
|
|
49
|
+
the original version of the Work and any modifications or additions
|
|
50
|
+
to that Work or Derivative Works thereof, that is intentionally
|
|
51
|
+
submitted to Licensor for inclusion in the Work by the copyright owner
|
|
52
|
+
or by an individual or Legal Entity authorized to submit on behalf of
|
|
53
|
+
the copyright owner. For the purposes of this definition, "submitted"
|
|
54
|
+
means any form of electronic, verbal, or written communication sent
|
|
55
|
+
to the Licensor or its representatives, including but not limited to
|
|
56
|
+
communication on electronic mailing lists, source code control systems,
|
|
57
|
+
and issue tracking systems that are managed by, or on behalf of, the
|
|
58
|
+
Licensor for the purpose of discussing and improving the Work, but
|
|
59
|
+
excluding communication that is conspicuously marked or otherwise
|
|
60
|
+
designated in writing by the copyright owner as "Not a Contribution."
|
|
61
|
+
|
|
62
|
+
"Contributor" shall mean Licensor and any individual or Legal Entity
|
|
63
|
+
on behalf of whom a Contribution has been received by Licensor and
|
|
64
|
+
subsequently incorporated within the Work.
|
|
65
|
+
|
|
66
|
+
2. Grant of Copyright License. Subject to the terms and conditions of
|
|
67
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
68
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
69
|
+
copyright license to reproduce, prepare Derivative Works of,
|
|
70
|
+
publicly display, publicly perform, sublicense, and distribute the
|
|
71
|
+
Work and such Derivative Works in Source or Object form.
|
|
72
|
+
|
|
73
|
+
3. Grant of Patent License. Subject to the terms and conditions of
|
|
74
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
75
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
76
|
+
(except as stated in this section) patent license to make, have made,
|
|
77
|
+
use, offer to sell, sell, import, and otherwise transfer the Work,
|
|
78
|
+
where such license applies only to those patent claims licensable
|
|
79
|
+
by such Contributor that are necessarily infringed by their
|
|
80
|
+
Contribution(s) alone or by combination of their Contribution(s)
|
|
81
|
+
with the Work to which such Contribution(s) was submitted. If You
|
|
82
|
+
institute patent litigation against any entity (including a
|
|
83
|
+
cross-claim or counterclaim in a lawsuit) alleging that the Work
|
|
84
|
+
or a Contribution incorporated within the Work constitutes direct
|
|
85
|
+
or contributory patent infringement, then any patent licenses
|
|
86
|
+
granted to You under this License for that Work shall terminate
|
|
87
|
+
as of the date such litigation is filed.
|
|
88
|
+
|
|
89
|
+
4. Redistribution. You may reproduce and distribute copies of the
|
|
90
|
+
Work or Derivative Works thereof in any medium, with or without
|
|
91
|
+
modifications, and in Source or Object form, provided that You
|
|
92
|
+
meet the following conditions:
|
|
93
|
+
|
|
94
|
+
(a) You must give any other recipients of the Work or
|
|
95
|
+
Derivative Works a copy of this License; and
|
|
96
|
+
|
|
97
|
+
(b) You must cause any modified files to carry prominent notices
|
|
98
|
+
stating that You changed the files; and
|
|
99
|
+
|
|
100
|
+
(c) You must retain, in the Source form of any Derivative Works
|
|
101
|
+
that You distribute, all copyright, patent, trademark, and
|
|
102
|
+
attribution notices from the Source form of the Work,
|
|
103
|
+
excluding those notices that do not pertain to any part of
|
|
104
|
+
the Derivative Works; and
|
|
105
|
+
|
|
106
|
+
(d) If the Work includes a "NOTICE" text file as part of its
|
|
107
|
+
distribution, then any Derivative Works that You distribute must
|
|
108
|
+
include a readable copy of the attribution notices contained
|
|
109
|
+
within such NOTICE file, excluding those notices that do not
|
|
110
|
+
pertain to any part of the Derivative Works, in at least one
|
|
111
|
+
of the following places: within a NOTICE text file distributed
|
|
112
|
+
as part of the Derivative Works; within the Source form or
|
|
113
|
+
documentation, if provided along with the Derivative Works; or,
|
|
114
|
+
within a display generated by the Derivative Works, if and
|
|
115
|
+
wherever such third-party notices normally appear. The contents
|
|
116
|
+
of the NOTICE file are for informational purposes only and
|
|
117
|
+
do not modify the License. You may add Your own attribution
|
|
118
|
+
notices within Derivative Works that You distribute, alongside
|
|
119
|
+
or as an addendum to the NOTICE text from the Work, provided
|
|
120
|
+
that such additional attribution notices cannot be construed
|
|
121
|
+
as modifying the License.
|
|
122
|
+
|
|
123
|
+
You may add Your own copyright statement to Your modifications and
|
|
124
|
+
may provide additional or different license terms and conditions
|
|
125
|
+
for use, reproduction, or distribution of Your modifications, or
|
|
126
|
+
for any such Derivative Works as a whole, provided Your use,
|
|
127
|
+
reproduction, and distribution of the Work otherwise complies with
|
|
128
|
+
the conditions stated in this License.
|
|
129
|
+
|
|
130
|
+
5. Submission of Contributions. Unless You explicitly state otherwise,
|
|
131
|
+
any Contribution intentionally submitted for inclusion in the Work
|
|
132
|
+
by You to the Licensor shall be under the terms and conditions of
|
|
133
|
+
this License, without any additional terms or conditions.
|
|
134
|
+
Notwithstanding the above, nothing herein shall supersede or modify
|
|
135
|
+
the terms of any separate license agreement you may have executed
|
|
136
|
+
with Licensor regarding such Contributions.
|
|
137
|
+
|
|
138
|
+
6. Trademarks. This License does not grant permission to use the trade
|
|
139
|
+
names, trademarks, service marks, or product names of the Licensor,
|
|
140
|
+
except as required for reasonable and customary use in describing the
|
|
141
|
+
origin of the Work and reproducing the content of the NOTICE file.
|
|
142
|
+
|
|
143
|
+
7. Disclaimer of Warranty. Unless required by applicable law or
|
|
144
|
+
agreed to in writing, Licensor provides the Work (and each
|
|
145
|
+
Contributor provides its Contributions) on an "AS IS" BASIS,
|
|
146
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
|
|
147
|
+
implied, including, without limitation, any warranties or conditions
|
|
148
|
+
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
|
|
149
|
+
PARTICULAR PURPOSE. You are solely responsible for determining the
|
|
150
|
+
appropriateness of using or redistributing the Work and assume any
|
|
151
|
+
risks associated with Your exercise of permissions under this License.
|
|
152
|
+
|
|
153
|
+
8. Limitation of Liability. In no event and under no legal theory,
|
|
154
|
+
whether in tort (including negligence), contract, or otherwise,
|
|
155
|
+
unless required by applicable law (such as deliberate and grossly
|
|
156
|
+
negligent acts) or agreed to in writing, shall any Contributor be
|
|
157
|
+
liable to You for damages, including any direct, indirect, special,
|
|
158
|
+
incidental, or consequential damages of any character arising as a
|
|
159
|
+
result of this License or out of the use or inability to use the
|
|
160
|
+
Work (including but not limited to damages for loss of goodwill,
|
|
161
|
+
work stoppage, computer failure or malfunction, or any and all
|
|
162
|
+
other commercial damages or losses), even if such Contributor
|
|
163
|
+
has been advised of the possibility of such damages.
|
|
164
|
+
|
|
165
|
+
9. Accepting Warranty or Additional Liability. While redistributing
|
|
166
|
+
the Work or Derivative Works thereof, You may choose to offer,
|
|
167
|
+
and charge a fee for, acceptance of support, warranty, indemnity,
|
|
168
|
+
or other liability obligations and/or rights consistent with this
|
|
169
|
+
License. However, in accepting such obligations, You may act only
|
|
170
|
+
on Your own behalf and on Your sole responsibility, not on behalf
|
|
171
|
+
of any other Contributor, and only if You agree to indemnify,
|
|
172
|
+
defend, and hold each Contributor harmless for any liability
|
|
173
|
+
incurred by, or claims asserted against, such Contributor by reason
|
|
174
|
+
of your accepting any such warranty or additional liability.
|
|
175
|
+
|
|
176
|
+
END OF TERMS AND CONDITIONS
|
|
177
|
+
|
|
178
|
+
APPENDIX: How to apply the Apache License to your work.
|
|
179
|
+
|
|
180
|
+
To apply the Apache License to your work, attach the following
|
|
181
|
+
boilerplate notice, with the fields enclosed by brackets "[]"
|
|
182
|
+
replaced with your own identifying information. (Don't include
|
|
183
|
+
the brackets!) The text should be enclosed in the appropriate
|
|
184
|
+
comment syntax for the file format. We also recommend that a
|
|
185
|
+
file or class name and description of purpose be included on the
|
|
186
|
+
same "printed page" as the copyright notice for easier
|
|
187
|
+
identification within third-party archives.
|
|
188
|
+
|
|
189
|
+
Copyright [yyyy] [name of copyright owner]
|
|
190
|
+
|
|
191
|
+
Licensed under the Apache License, Version 2.0 (the "License");
|
|
192
|
+
you may not use this file except in compliance with the License.
|
|
193
|
+
You may obtain a copy of the License at
|
|
194
|
+
|
|
195
|
+
http://www.apache.org/licenses/LICENSE-2.0
|
|
196
|
+
|
|
197
|
+
Unless required by applicable law or agreed to in writing, software
|
|
198
|
+
distributed under the License is distributed on an "AS IS" BASIS,
|
|
199
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
200
|
+
See the License for the specific language governing permissions and
|
|
201
|
+
limitations under the License.
|
package/README.md
ADDED
|
@@ -0,0 +1,258 @@
|
|
|
1
|
+
# Dory CLI / Dory Headless Runtime
|
|
2
|
+
|
|
3
|
+
`@getdory/cli` runs Dory without the desktop client. It is the standalone entrypoint for MCP servers, automation, and direct Dory Action execution.
|
|
4
|
+
|
|
5
|
+
## Requirements
|
|
6
|
+
|
|
7
|
+
- Node.js 20 or newer.
|
|
8
|
+
- Linux, macOS, or Windows with npm available.
|
|
9
|
+
- Network access during install for native database driver packages.
|
|
10
|
+
|
|
11
|
+
This beta ships the full Dory database driver set. Install can compile or download native packages for PGlite, DuckDB, SQLite, Oracle, MySQL, and Postgres support. If install fails, confirm your Node version first, then check whether your platform has the build tools required by the failing native package.
|
|
12
|
+
|
|
13
|
+
## Install
|
|
14
|
+
|
|
15
|
+
Run without installing globally:
|
|
16
|
+
|
|
17
|
+
```sh
|
|
18
|
+
npx -y @getdory/cli --help
|
|
19
|
+
```
|
|
20
|
+
|
|
21
|
+
Install globally when running Dory as a long-lived server:
|
|
22
|
+
|
|
23
|
+
```sh
|
|
24
|
+
npm install -g @getdory/cli
|
|
25
|
+
dory --help
|
|
26
|
+
```
|
|
27
|
+
|
|
28
|
+
## Quick Start
|
|
29
|
+
|
|
30
|
+
Standalone mode stores Dory state under `~/.dory` and is the default mode for Linux servers, CI, and shared automation hosts.
|
|
31
|
+
|
|
32
|
+
```sh
|
|
33
|
+
npx -y @getdory/cli init --data standalone
|
|
34
|
+
npx -y @getdory/cli doctor --data standalone
|
|
35
|
+
npx -y @getdory/cli mcp token create --data standalone --name "server"
|
|
36
|
+
npx -y @getdory/cli mcp serve --stdio --data standalone
|
|
37
|
+
```
|
|
38
|
+
|
|
39
|
+
Run a local HTTP MCP endpoint:
|
|
40
|
+
|
|
41
|
+
```sh
|
|
42
|
+
npx -y @getdory/cli mcp serve \
|
|
43
|
+
--http \
|
|
44
|
+
--host 127.0.0.1 \
|
|
45
|
+
--port 3318 \
|
|
46
|
+
--data standalone
|
|
47
|
+
```
|
|
48
|
+
|
|
49
|
+
Run Dory Actions directly:
|
|
50
|
+
|
|
51
|
+
```sh
|
|
52
|
+
npx -y @getdory/cli action list --data standalone
|
|
53
|
+
npx -y @getdory/cli action connection.list --data standalone --projection mcp --json '{}'
|
|
54
|
+
```
|
|
55
|
+
|
|
56
|
+
## Connect Local Codex Agent
|
|
57
|
+
|
|
58
|
+
Dory Web can run Codex on this device through the CLI. Run this once on the device where Codex CLI is installed:
|
|
59
|
+
|
|
60
|
+
```sh
|
|
61
|
+
npx -y @getdory/cli agent codex install --url https://your-dory-host
|
|
62
|
+
```
|
|
63
|
+
|
|
64
|
+
The command authorizes Dory, installs a background Dory Codex Agent service, and starts it. When Dory sends a job to the service, it runs `codex exec` with Dory MCP tools enabled.
|
|
65
|
+
|
|
66
|
+
Manage the background service:
|
|
67
|
+
|
|
68
|
+
```sh
|
|
69
|
+
dory agent codex status
|
|
70
|
+
dory agent codex restart
|
|
71
|
+
dory agent codex stop
|
|
72
|
+
dory agent codex uninstall
|
|
73
|
+
```
|
|
74
|
+
|
|
75
|
+
For troubleshooting, run the worker in the foreground:
|
|
76
|
+
|
|
77
|
+
```sh
|
|
78
|
+
dory agent codex run --url https://your-dory-host
|
|
79
|
+
```
|
|
80
|
+
|
|
81
|
+
The Dory MCP bearer token is passed through an environment variable and is not written into the Codex command arguments.
|
|
82
|
+
|
|
83
|
+
## Data Modes
|
|
84
|
+
|
|
85
|
+
- `standalone`: independent Dory app storage under `~/.dory`. This is the recommended headless server mode.
|
|
86
|
+
- `desktop`: read Dory Desktop local data without opening Electron. Do not use it while the desktop app is running unless concurrent PGlite access has been validated.
|
|
87
|
+
- `self-hosted`: use a self-hosted Dory Web Postgres app database.
|
|
88
|
+
|
|
89
|
+
Use `doctor` before serving MCP to confirm the selected storage path, secrets, migrations, identity, token count, and connection count:
|
|
90
|
+
|
|
91
|
+
```sh
|
|
92
|
+
npx -y @getdory/cli doctor --data standalone
|
|
93
|
+
```
|
|
94
|
+
|
|
95
|
+
Self-hosted mode must use the same secrets as the Web deployment:
|
|
96
|
+
|
|
97
|
+
```sh
|
|
98
|
+
DS_SECRET_KEY="same-as-web" \
|
|
99
|
+
BETTER_AUTH_SECRET="same-as-web" \
|
|
100
|
+
npx -y @getdory/cli mcp serve \
|
|
101
|
+
--stdio \
|
|
102
|
+
--data self-hosted \
|
|
103
|
+
--database-url "$DATABASE_URL"
|
|
104
|
+
```
|
|
105
|
+
|
|
106
|
+
If `DS_SECRET_KEY` or `BETTER_AUTH_SECRET` do not match the Web deployment, encrypted connection secrets and auth-backed data will not be readable.
|
|
107
|
+
|
|
108
|
+
## HTTP Security
|
|
109
|
+
|
|
110
|
+
HTTP MCP listens on `127.0.0.1` by default and requires bearer token authentication. Create a token first:
|
|
111
|
+
|
|
112
|
+
```sh
|
|
113
|
+
npx -y @getdory/cli mcp token create --data standalone --name "mcp-http"
|
|
114
|
+
```
|
|
115
|
+
|
|
116
|
+
Remote binds require an existing token and an explicit opt-in:
|
|
117
|
+
|
|
118
|
+
```sh
|
|
119
|
+
npx -y @getdory/cli mcp serve \
|
|
120
|
+
--http \
|
|
121
|
+
--host 0.0.0.0 \
|
|
122
|
+
--port 3318 \
|
|
123
|
+
--allow-remote \
|
|
124
|
+
--token "$DORY_MCP_TOKEN" \
|
|
125
|
+
--data standalone
|
|
126
|
+
```
|
|
127
|
+
|
|
128
|
+
Do not expose the plain HTTP server directly to the public internet. Put it behind TLS.
|
|
129
|
+
|
|
130
|
+
Nginx example:
|
|
131
|
+
|
|
132
|
+
```nginx
|
|
133
|
+
server {
|
|
134
|
+
listen 443 ssl;
|
|
135
|
+
server_name dory-mcp.example.com;
|
|
136
|
+
|
|
137
|
+
ssl_certificate /etc/letsencrypt/live/dory-mcp.example.com/fullchain.pem;
|
|
138
|
+
ssl_certificate_key /etc/letsencrypt/live/dory-mcp.example.com/privkey.pem;
|
|
139
|
+
|
|
140
|
+
location / {
|
|
141
|
+
proxy_pass http://127.0.0.1:3318;
|
|
142
|
+
proxy_set_header Host $host;
|
|
143
|
+
proxy_set_header X-Forwarded-Proto https;
|
|
144
|
+
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
|
|
145
|
+
}
|
|
146
|
+
}
|
|
147
|
+
```
|
|
148
|
+
|
|
149
|
+
Caddy example:
|
|
150
|
+
|
|
151
|
+
```caddy
|
|
152
|
+
dory-mcp.example.com {
|
|
153
|
+
reverse_proxy 127.0.0.1:3318
|
|
154
|
+
}
|
|
155
|
+
```
|
|
156
|
+
|
|
157
|
+
## Linux Server Deployment
|
|
158
|
+
|
|
159
|
+
systemd example:
|
|
160
|
+
|
|
161
|
+
```ini
|
|
162
|
+
[Unit]
|
|
163
|
+
Description=Dory Headless MCP Runtime
|
|
164
|
+
After=network-online.target
|
|
165
|
+
Wants=network-online.target
|
|
166
|
+
|
|
167
|
+
[Service]
|
|
168
|
+
Type=simple
|
|
169
|
+
User=dory
|
|
170
|
+
Environment=HOME=/var/lib/dory
|
|
171
|
+
ExecStart=/usr/bin/env npx -y @getdory/cli mcp serve --http --data standalone --host 127.0.0.1 --port 3318
|
|
172
|
+
Restart=always
|
|
173
|
+
RestartSec=5
|
|
174
|
+
|
|
175
|
+
[Install]
|
|
176
|
+
WantedBy=multi-user.target
|
|
177
|
+
```
|
|
178
|
+
|
|
179
|
+
Docker example:
|
|
180
|
+
|
|
181
|
+
```Dockerfile
|
|
182
|
+
FROM node:22-bookworm-slim
|
|
183
|
+
ENV HOME=/data
|
|
184
|
+
ENV DORY_MCP_TOKEN=replace-with-an-existing-token
|
|
185
|
+
VOLUME ["/data/.dory"]
|
|
186
|
+
EXPOSE 3318
|
|
187
|
+
CMD ["sh", "-lc", "npx -y @getdory/cli mcp serve --http --data standalone --host 0.0.0.0 --port 3318 --allow-remote --token \"$DORY_MCP_TOKEN\""]
|
|
188
|
+
```
|
|
189
|
+
|
|
190
|
+
Run it:
|
|
191
|
+
|
|
192
|
+
```sh
|
|
193
|
+
docker build -t dory-headless .
|
|
194
|
+
docker run --rm -v dory-data:/data/.dory -e HOME=/data node:22-bookworm-slim \
|
|
195
|
+
npx -y @getdory/cli mcp token create --data standalone --name docker
|
|
196
|
+
docker run --rm -p 3318:3318 -v dory-data:/data/.dory -e DORY_MCP_TOKEN="$DORY_MCP_TOKEN" dory-headless
|
|
197
|
+
```
|
|
198
|
+
|
|
199
|
+
For public Docker deployments, terminate TLS in front of the container instead of exposing cleartext HTTP directly.
|
|
200
|
+
|
|
201
|
+
## Desktop Data Source
|
|
202
|
+
|
|
203
|
+
Use Desktop data only when you want the CLI to read connections, tabs, saved queries, and tokens already stored by Dory Desktop:
|
|
204
|
+
|
|
205
|
+
```sh
|
|
206
|
+
npx -y @getdory/cli doctor --data desktop
|
|
207
|
+
npx -y @getdory/cli mcp serve --stdio --data desktop
|
|
208
|
+
```
|
|
209
|
+
|
|
210
|
+
Desktop mode points at the Dory Desktop PGlite database. Avoid running Desktop and the CLI against the same PGlite data directory at the same time until concurrent access has been validated for your deployment.
|
|
211
|
+
|
|
212
|
+
## Hosted Dory Bridge
|
|
213
|
+
|
|
214
|
+
For hosted Dory Web MCP endpoints, use:
|
|
215
|
+
|
|
216
|
+
```sh
|
|
217
|
+
npx -y @getdory/cli mcp login --url https://your-dory-host
|
|
218
|
+
npx -y @getdory/cli mcp status --url https://your-dory-host
|
|
219
|
+
npx -y @getdory/cli mcp bridge --url https://your-dory-host
|
|
220
|
+
```
|
|
221
|
+
|
|
222
|
+
## Update and Uninstall
|
|
223
|
+
|
|
224
|
+
Update a global install:
|
|
225
|
+
|
|
226
|
+
```sh
|
|
227
|
+
npm install -g @getdory/cli@latest
|
|
228
|
+
```
|
|
229
|
+
|
|
230
|
+
Uninstall a global install:
|
|
231
|
+
|
|
232
|
+
```sh
|
|
233
|
+
npm uninstall -g @getdory/cli
|
|
234
|
+
```
|
|
235
|
+
|
|
236
|
+
Remove standalone data only when you no longer need local Dory state:
|
|
237
|
+
|
|
238
|
+
```sh
|
|
239
|
+
rm -rf ~/.dory
|
|
240
|
+
```
|
|
241
|
+
|
|
242
|
+
## Troubleshooting
|
|
243
|
+
|
|
244
|
+
- `Unsupported engine`: install Node.js 20 or newer.
|
|
245
|
+
- `crypto is not defined`: the process is running on an unsupported Node.js version. Upgrade to Node.js 20 or newer.
|
|
246
|
+
- Native package install failure: install platform build tools, upgrade Node.js, or retry on Node.js 22.
|
|
247
|
+
- `--data self-hosted requires DS_SECRET_KEY`: export the same `DS_SECRET_KEY` and `BETTER_AUTH_SECRET` used by your Dory Web deployment.
|
|
248
|
+
- `No desktop auth snapshot`: open Dory Desktop once, or pass `--user-data-dir` for the active Desktop profile.
|
|
249
|
+
|
|
250
|
+
## Release Smoke
|
|
251
|
+
|
|
252
|
+
Before publishing:
|
|
253
|
+
|
|
254
|
+
```sh
|
|
255
|
+
yarn workspace @getdory/cli pack:smoke
|
|
256
|
+
```
|
|
257
|
+
|
|
258
|
+
The smoke test builds the package, packs it, installs it into a clean temporary npm project, checks `dory --help`, runs `action list --data standalone`, starts stdio MCP, and verifies `tools/list`.
|