@vectros-ai/mcp-server 0.15.0 → 0.16.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 CHANGED
@@ -3,6 +3,23 @@
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.16.0 — 2026-08-27
7
+
8
+ ### Added
9
+
10
+ - **`record_batch_get`** — fetch several structured records by id (1-100) in one call, each with its
11
+ full payload, wrapping `POST /v1/records/batch-get` (0.41.0: previously a `501` stub, now live).
12
+ Complements `record_get`: use this instead of N single-id calls when you already hold several ids
13
+ (e.g. hydrating a page of `record_query`/`hybrid_search` results). The API silently omits any id you
14
+ can't access with no per-id existence signal; the response also carries `missingIds` — every
15
+ requested id not present in `data` — so a caller can tell a partial result from a complete one
16
+ without diffing it by hand. Same per-record payload-truncation guard as `record_get`.
17
+ - **Repinned to `@vectros-ai/sdk` 0.41.0** for the above. No other 0.41.0 surface change is consumed:
18
+ the issuer-update endpoint and the `roleIds` access-profile field are identity/access administration
19
+ this server's tools deliberately don't touch (`lookup_principal`'s own docstring: "identity CRUD
20
+ stays off the agent tool surface by design"); entity responses' new `contextId` field already flows
21
+ through `lookup_principal`'s pass-through JSON with no code change.
22
+
6
23
  ## 0.15.0
7
24
 
8
25
  ### Added
package/README.md CHANGED
@@ -169,7 +169,7 @@ Add `-e VECTROS_API_BASE_URL=https://api.staging.vectros.ai` for a non-productio
169
169
  environment. Reopen the project in Claude Code and the Vectros tools are
170
170
  available.
171
171
 
172
- ## Tools (21 tools)
172
+ ## Tools (22 tools)
173
173
 
174
174
  **Search & RAG**
175
175
 
@@ -186,6 +186,7 @@ available.
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
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
+ | `record_batch_get` | Fetch several records by id (1-100) in one call, each with its full payload. Returns `missingIds` for any requested id you can't access, since the API silently omits them. |
189
190
  | `record_create` | Create a record of a given type; idempotent by `externalId`; optional per-record `indexMode`. |
190
191
  | `record_update` | Patch a record's payload (deep-merged; `null` deletes a key); optimistic concurrency via `expectedVersion`. |
191
192
  | `record_delete` | Permanently delete a record by id (leaves a tombstone). |
@@ -217,7 +218,7 @@ available.
217
218
  | `lookup_principal` | Resolve a user, or an identity entity in a namespace (`org`/`client`/any namespace you registered), by your own `externalId` (→ its Vectros UUID, for the ownership filters) or by a schema lookup field. Pass `contextId` to target a specific app context for a context-owned namespace. Read-only. |
218
219
  | `version_history` | Read the audit/version trail (CREATE/UPDATE/DELETE, with actor + diff) for one record or document. Read-only. |
219
220
 
220
- All 21 tools wrap published Vectros HTTP API endpoints. JSON
221
+ All 22 tools wrap published Vectros HTTP API endpoints. JSON
221
222
  responses are what the agent sees as tool output. Per-call cost
222
223
  surfaces via the `usage` field on inference responses.
223
224