@astrivya/mcp 0.1.1 → 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
CHANGED
|
@@ -62,8 +62,8 @@ retained during the transition, it takes precedence over OIDC until it is remove
|
|
|
62
62
|
|
|
63
63
|
## Client config
|
|
64
64
|
|
|
65
|
-
This is
|
|
66
|
-
Code, Cursor, and Zed. It must be pointed at one vault file; it never guesses a
|
|
65
|
+
This is the standalone packaged server — a stdio MCP server for hosts such as
|
|
66
|
+
OpenCode, Codex, Claude Code, Cursor, and Zed. It must be pointed at one vault file; it never guesses a
|
|
67
67
|
default. If you do not have a vault yet, run `memnoth vault init` and
|
|
68
68
|
`memnoth vault status`, then copy the absolute vault file path shown by status.
|
|
69
69
|
Creating a new vault requires the Memnoth CLI once; after that, the packaged
|
|
@@ -161,11 +161,51 @@ For Zed, add the equivalent entry to its settings JSON:
|
|
|
161
161
|
}
|
|
162
162
|
```
|
|
163
163
|
|
|
164
|
-
|
|
165
|
-
|
|
166
|
-
|
|
167
|
-
|
|
168
|
-
|
|
164
|
+
## CLI-managed one-click registration
|
|
165
|
+
|
|
166
|
+
If the Memnoth CLI is installed, `mcp add --local` writes the same stdio entry
|
|
167
|
+
into each client's own config for you. It resolves the vault path, sets
|
|
168
|
+
`MEMNOTH_MCP_PROFILE`, and defaults to read-only; no account, token or network
|
|
169
|
+
access is needed. The client names advertised on the site are `claude`,
|
|
170
|
+
`cursor`, `codex` and `zed` (`opencode` is also accepted):
|
|
171
|
+
|
|
172
|
+
```sh
|
|
173
|
+
mn mcp add --local --clients claude,cursor,codex,zed
|
|
174
|
+
```
|
|
175
|
+
|
|
176
|
+
Flags that matter for the written entry:
|
|
177
|
+
|
|
178
|
+
- `--profile <name>` — tool profile. `--local` defaults to `memory`; a cloud
|
|
179
|
+
registration (`mcp add` without `--local`) defaults to `full`. Valid names:
|
|
180
|
+
`micro`, `memory`, `coord`, `code`, `full`, `agent` (the last is HTTP-only).
|
|
181
|
+
- `--allow-writes` — launch with `MEMNOTH_MCP_READ_ONLY=0`. Without it the entry
|
|
182
|
+
sets `MEMNOTH_MCP_READ_ONLY=1` and the report says `writes read-only`.
|
|
183
|
+
- `--dry-run` — show the paths and entry that would be written; writes nothing.
|
|
184
|
+
- `--team <name>` — register a shared team vault instead of the personal one
|
|
185
|
+
(requires `--local`).
|
|
186
|
+
- `--db <path>` — name the vault file explicitly instead of the resolved default.
|
|
187
|
+
|
|
188
|
+
Examples:
|
|
189
|
+
|
|
190
|
+
```sh
|
|
191
|
+
mn mcp add --local --clients claude,cursor,codex --profile code
|
|
192
|
+
mn mcp add --local --clients cursor --allow-writes
|
|
193
|
+
mn mcp add --local --clients claude,cursor,codex,zed --dry-run
|
|
194
|
+
memnoth mcp add --local --clients opencode # OpenCode chooses the CLI-managed path
|
|
195
|
+
```
|
|
196
|
+
|
|
197
|
+
The written entry launches `<path-to-memnoth> mcp serve --db <absolute-vault>`
|
|
198
|
+
with `MEMNOTH_MCP_PROFILE` and `MEMNOTH_MCP_READ_ONLY` in its environment. Local
|
|
199
|
+
mode writes no token into the client config and reports `token_used: false` with
|
|
200
|
+
an empty `url`. The config files are `~/.claude.json` (Claude Code),
|
|
201
|
+
`~/.cursor/mcp.json` (Cursor), `~/.codex/config.toml` (Codex) and Zed's
|
|
202
|
+
`settings.json` (`~/.config/zed` on Linux/macOS, `%APPDATA%\Zed` on Windows).
|
|
203
|
+
Zed settings are JSON-with-comments; `mcp add` will not rewrite such a file and
|
|
204
|
+
prints a snippet for Zed's Command Palette instead.
|
|
205
|
+
|
|
206
|
+
Use one setup flow — the standalone npm entry above, or the CLI-managed
|
|
207
|
+
registration described here. Use one only: do not add both entries unless you
|
|
208
|
+
intentionally want two servers named `memnoth`.
|
|
169
209
|
|
|
170
210
|
## Protocol compatibility
|
|
171
211
|
|
|
@@ -192,11 +232,11 @@ The `--version` flag works completely offline without spawning the binary.
|
|
|
192
232
|
**The profile tool counts are generated by** `scripts/check_surface.py` **from** the standalone server's `server.json` metadata. Rust tests verify those counts against implemented server tools; the CLI's broader capability catalog may include tools unavailable in this binary.
|
|
193
233
|
| `MEMNOTH_MCP_PROFILE` | Tools | What it is for |
|
|
194
234
|
|---|---|---|
|
|
195
|
-
| `memory` |
|
|
196
|
-
| `code` |
|
|
235
|
+
| `memory` | 22 | The vault, the temporal quartet (`vault_history`, `vault_asof`, `vault_contradictions`, `vault_top`), the invariant gate (`vault_invariants`), vault hygiene (`mem_duplicates`), index health |
|
|
236
|
+
| `code` | 20 | Code-graph navigation, the filesystem/git toolbox, and local receipt verification |
|
|
197
237
|
| `coord` | 14 | Multi-agent claims, tasks, messaging |
|
|
198
238
|
| `micro` | 4 | Smallest useful set |
|
|
199
|
-
| `full` |
|
|
239
|
+
| `full` | 49 | Everything |
|
|
200
240
|
|
|
201
241
|
A tool you expected but cannot see is a profile setting, not a missing
|
|
202
242
|
capability — the server reports the active profile and its tool count in the
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@astrivya/mcp",
|
|
3
|
-
"version": "0.1.
|
|
3
|
+
"version": "0.1.2",
|
|
4
4
|
"description": "MCP server for memnoth: bi-temporal memory vault, code graph, and multi-agent coordination. This package is a launcher for the memnoth binary.",
|
|
5
5
|
"license": "Apache-2.0",
|
|
6
6
|
"bin": {
|
|
Binary file
|
|
Binary file
|
|
Binary file
|
|
Binary file
|
|
Binary file
|