@vectros-ai/mcp-server 0.11.0 → 0.13.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/CHANGELOG.md +66 -0
- package/README.md +2 -2
- package/dist/cli-http.js +211 -65
- package/dist/cli-http.js.map +1 -1
- package/dist/cli-http.mjs +211 -65
- package/dist/cli-http.mjs.map +1 -1
- package/dist/cli.js +211 -65
- package/dist/cli.js.map +1 -1
- package/dist/cli.mjs +211 -65
- package/dist/cli.mjs.map +1 -1
- package/dist/index.js +211 -65
- package/dist/index.js.map +1 -1
- package/dist/index.mjs +211 -65
- package/dist/index.mjs.map +1 -1
- package/package.json +2 -2
package/CHANGELOG.md
CHANGED
|
@@ -3,6 +3,72 @@
|
|
|
3
3
|
All notable changes to `@vectros-ai/mcp-server` are documented here.
|
|
4
4
|
This project adheres to [Semantic Versioning](https://semver.org).
|
|
5
5
|
|
|
6
|
+
## 0.13.0
|
|
7
|
+
|
|
8
|
+
### Added
|
|
9
|
+
|
|
10
|
+
- **`record_query` can now look up a record by several fields at once — for a
|
|
11
|
+
type whose schema declares a lookup over those fields together** (not any
|
|
12
|
+
two fields you pick; see the type's schema, e.g. via `list_schemas`). Pass
|
|
13
|
+
the comma-joined field names (e.g. `"status,area"`) with one value per field
|
|
14
|
+
in the new `values` array — or a single `value`, which is exactly a
|
|
15
|
+
one-element `values` (matches the first named field, grouping by the rest).
|
|
16
|
+
Supplying fewer values than the lookup declares — as long as they're a
|
|
17
|
+
leading run of its fields — returns records grouped by the fields left
|
|
18
|
+
unspecified; `from`/`to`/`prefix` are not valid on a composite field
|
|
19
|
+
(exact-match only). Also new: `sortFrom`/`sortTo` narrow an exact-match
|
|
20
|
+
(`value` or a full `values`) lookup to a window of the field's sort key
|
|
21
|
+
instead of paging the whole match. Record lookups only; document lookups
|
|
22
|
+
are unchanged.
|
|
23
|
+
- **`current_identity` (and the `identity` resource) now report `mcpServerVersion` and
|
|
24
|
+
`sdkVersion`**, so you can tell exactly which server build and bundled SDK version a
|
|
25
|
+
running instance is talking with.
|
|
26
|
+
|
|
27
|
+
### Fixed
|
|
28
|
+
|
|
29
|
+
- **`list_schemas` (and the `schemas` resource) no longer risk hanging on an unusual
|
|
30
|
+
empty-page response.** Draining the schema catalog now stops with a clear error
|
|
31
|
+
instead of paging forever if the backend ever returns an empty page alongside a
|
|
32
|
+
cursor that keeps claiming more remain.
|
|
33
|
+
|
|
34
|
+
### Changed
|
|
35
|
+
|
|
36
|
+
- **Dependency maintenance** — repinned the bundled `@vectros-ai/sdk` to `0.38.0`.
|
|
37
|
+
This pulls in a **Vectros API-side** pagination fix (distinct from the client-side
|
|
38
|
+
guard above): a listing or lookup could previously report itself complete while
|
|
39
|
+
results remained on a large page read; the API itself now always pages correctly,
|
|
40
|
+
and every tool here that pages already trusted the cursor rather than the page
|
|
41
|
+
size, so this is inherited automatically.
|
|
42
|
+
|
|
43
|
+
## 0.12.0
|
|
44
|
+
|
|
45
|
+
### Fixed
|
|
46
|
+
|
|
47
|
+
- **`document_get`/`document_update` selector errors now name the right parameter.**
|
|
48
|
+
Calling either tool with a bad or missing selector previously told you to
|
|
49
|
+
"provide `id`" — but their actual parameter is `documentId`; `id` isn't
|
|
50
|
+
recognized at all. A caller reasonably assuming symmetry with `record_get`
|
|
51
|
+
(which genuinely does use `id`) got an error message that appeared to confirm
|
|
52
|
+
the wrong fix. Both selector-validation messages now say `documentId`;
|
|
53
|
+
`record_get`/`record_update` are unchanged (their parameter really is `id`).
|
|
54
|
+
|
|
55
|
+
### Changed
|
|
56
|
+
|
|
57
|
+
- **`hybrid_search` results now carry `externalId` per hit, and the response
|
|
58
|
+
includes `hasMore`.** `externalId` lets you correlate a hit back to your own
|
|
59
|
+
record/document identity without a follow-up lookup (null if the item was
|
|
60
|
+
ingested without one, or indexed before this field existed). `hasMore` tells
|
|
61
|
+
you explicitly whether more results are available past the current page.
|
|
62
|
+
- **The `textLegEmpty` diagnostic no longer fires on every non-empty TEXT-mode
|
|
63
|
+
search.** It's based on each hit's keyword-relevance score, which the API
|
|
64
|
+
previously reported as `0` for every TEXT-mode result regardless of actual
|
|
65
|
+
relevance; TEXT-mode now returns a real, meaningful score, so the diagnostic
|
|
66
|
+
only fires when the keyword leg genuinely contributed nothing.
|
|
67
|
+
- **Dependency maintenance** — repinned the bundled `@vectros-ai/sdk` to `0.37.0`
|
|
68
|
+
(additive `basedOn` schema customization, `specificityRank` on namespaces, and
|
|
69
|
+
the search/RAG response fields above). The server bundles the SDK into its
|
|
70
|
+
published output, so this is a rebuild against the current SDK.
|
|
71
|
+
|
|
6
72
|
## 0.11.0
|
|
7
73
|
|
|
8
74
|
Refreshed to the 0.36.0 Vectros API, with clearer, more actionable errors and a
|
package/README.md
CHANGED
|
@@ -184,7 +184,7 @@ available.
|
|
|
184
184
|
| Tool | What it does |
|
|
185
185
|
|---|---|
|
|
186
186
|
| `list_schemas` | List the record-schema catalog the credential can see (filter by `surface` or resolve one by `recordType`). Makes `record_query` / `record_create` discoverable. |
|
|
187
|
-
| `record_query` | Query records by lookup field
|
|
187
|
+
| `record_query` | Query records by lookup field — equality (`value`), range, or prefix, with `asc`/`desc` ordering and an optional `sortFrom`/`sortTo` window — or list mode (filter by ownership + type). Also supports composite equality across 2-3 fields (`values`), but only against a lookup the *schema* declares over those fields together (see `list_schemas`) — not any two fields you pick. |
|
|
188
188
|
| `record_get` | Fetch one record by id, including its full payload (large payloads truncated to protect the agent context window). |
|
|
189
189
|
| `record_create` | Create a record of a given type; idempotent by `externalId`; optional per-record `indexMode`. |
|
|
190
190
|
| `record_update` | Patch a record's payload (deep-merged; `null` deletes a key); optimistic concurrency via `expectedVersion`. |
|
|
@@ -213,7 +213,7 @@ available.
|
|
|
213
213
|
|
|
214
214
|
| Tool | What it does |
|
|
215
215
|
|---|---|
|
|
216
|
-
| `current_identity` | Describe the credential: tenantId, environment, principalType, principalKeyId, and (for scoped credentials) allowedActions + dataScope. |
|
|
216
|
+
| `current_identity` | Describe the credential: tenantId, environment, principalType, principalKeyId, and (for scoped credentials) allowedActions + dataScope. Also reports this server's own version and the bundled SDK version (`mcpServerVersion`, `sdkVersion`). |
|
|
217
217
|
| `lookup_principal` | Resolve a user / org / client by your own `externalId` (→ its Vectros UUID, for the ownership filters) or by a schema lookup field. Read-only. |
|
|
218
218
|
| `version_history` | Read the audit/version trail (CREATE/UPDATE/DELETE, with actor + diff) for one record or document. Read-only. |
|
|
219
219
|
|