@vectros-ai/mcp-server 0.15.0 → 0.16.1

package/CHANGELOG.md

@@ -3,6 +3,48 @@
 All notable changes to `@vectros-ai/mcp-server` are documented here.
 This project adheres to [Semantic Versioning](https://semver.org).
 
+## 0.16.1 — 2026-08-27
+
+### Fixed
+
+- **Claude Code setup docs: restart-to-load + Windows npx-resolution caveats.**
+  The "Configure manually (Claude Code)" section now covers three real
+  friction points found in dogfooding: a session already open when the
+  server is added needs a full quit + reopen (not just re-selecting the
+  tab); the `/mcp` panel shows the connector marketplace, not local stdio
+  servers, so it can't confirm the server loaded; and config resolves off
+  the git common root, so a linked worktree needs adding/opening from the
+  same project as its main repo. Also documents a Windows-specific trap: a
+  scoped-registry override for `@vectros-ai` in `.npmrc` can silently
+  resolve `npx -y @vectros-ai/mcp-server` to an unexpected internal build
+  that isn't guaranteed to run there — pin an explicit version if the
+  plain command fails to start.
+- **`current_identity`'s `granted_capabilities` note now lists all five named capabilities.**
+  The tool description and the `identity` resource both listed only four
+  (`member-lifecycle` / `forensic-read` / `context-directory-read` / `delegate-mint`); the
+  platform's fifth, `delegate-principal-stamp`, is now named alongside them.
+
+### Changed
+
+- Bundled `@vectros-ai/sdk` refreshed to the current release's staging build.
+
+## 0.16.0 — 2026-08-27
+
+### Added
+
+- **`record_batch_get`** — fetch several structured records by id (1-100) in one call, each with its
+  full payload, wrapping `POST /v1/records/batch-get` (0.41.0: previously a `501` stub, now live).
+  Complements `record_get`: use this instead of N single-id calls when you already hold several ids
+  (e.g. hydrating a page of `record_query`/`hybrid_search` results). The API silently omits any id you
+  can't access with no per-id existence signal; the response also carries `missingIds` — every
+  requested id not present in `data` — so a caller can tell a partial result from a complete one
+  without diffing it by hand. Same per-record payload-truncation guard as `record_get`.
+- **Repinned to `@vectros-ai/sdk` 0.41.0** for the above. No other 0.41.0 surface change is consumed:
+  the issuer-update endpoint and the `roleIds` access-profile field are identity/access administration
+  this server's tools deliberately don't touch (`lookup_principal`'s own docstring: "identity CRUD
+  stays off the agent tool surface by design"); entity responses' new `contextId` field already flows
+  through `lookup_principal`'s pass-through JSON with no code change.
+
 ## 0.15.0
 
 ### Added

package/README.md

@@ -166,10 +166,25 @@ claude mcp add vectros -e VECTROS_API_KEY=ssk_live_... -- npx -y @vectros-ai/mcp
 ```
 
 Add `-e VECTROS_API_BASE_URL=https://api.staging.vectros.ai` for a non-production
-environment. Reopen the project in Claude Code and the Vectros tools are
-available.
-
-## Tools (21 tools)
+environment.
+
+**Load it into a session by restarting.** A Claude Code session that was
+already open when you added the server won't pick it up mid-session — fully
+quit and reopen the project (not just re-select the tab). The `/mcp` panel
+shows the connector marketplace, not locally-configured stdio servers, so it
+won't confirm the server is loaded — ask the agent to call a Vectros tool
+instead. Config is keyed by the **git common root**, so a linked worktree
+resolves to its main repo's `.mcp.json` — add and open from the same project.
+
+> **Windows note:** if your `.npmrc` (or a global npm config) points the
+> `@vectros-ai` scope at a private registry, a bare `npx -y @vectros-ai/mcp-server`
+> can resolve an unexpected internal build there instead of the public
+> release — and an internal build is not guaranteed to run on Windows. If the
+> command above fails to start, either remove the scoped-registry override
+> for a plain `npx` run, or pin an explicit version (`npx -y
+> @vectros-ai/mcp-server@<version>`) known to work.
+
+## Tools (22 tools)
 
 **Search & RAG**
 
@@ -186,6 +201,7 @@ available.
 | `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. |
 | `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. |
 | `record_get` | Fetch one record by id, including its full payload (large payloads truncated to protect the agent context window). |
+| `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. |
 | `record_create` | Create a record of a given type; idempotent by `externalId`; optional per-record `indexMode`. |
 | `record_update` | Patch a record's payload (deep-merged; `null` deletes a key); optimistic concurrency via `expectedVersion`. |
 | `record_delete` | Permanently delete a record by id (leaves a tombstone). |
@@ -213,11 +229,11 @@ available.
 
 | Tool | What it does |
 |---|---|
-| `current_identity` | Describe the credential: tenantId, environment, principalType, principalKeyId, principalLabel, and (for scoped credentials) allowedActions + dataScope. Does **not** yet include `granted_capabilities` (`member-lifecycle` / `forensic-read` / `context-directory-read` / `delegate-mint`) — a separate reach dimension a scope clause can carry as of API 0.40.0 that `/v1/ping` doesn't report yet, so allowedActions + dataScope may understate a credential's true reach. Also reports this server's own version and the bundled SDK version (`mcpServerVersion`, `sdkVersion`). |
+| `current_identity` | Describe the credential: tenantId, environment, principalType, principalKeyId, principalLabel, and (for scoped credentials) allowedActions + dataScope. Does **not** yet include `granted_capabilities` (`member-lifecycle` / `forensic-read` / `context-directory-read` / `delegate-mint`, as of API 0.40.0, joined by `delegate-principal-stamp` in 0.42.0) — a separate reach dimension a scope clause can carry that `/v1/ping` doesn't report yet, so allowedActions + dataScope may understate a credential's true reach. Also reports this server's own version and the bundled SDK version (`mcpServerVersion`, `sdkVersion`). |
 | `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. |
 | `version_history` | Read the audit/version trail (CREATE/UPDATE/DELETE, with actor + diff) for one record or document. Read-only. |
 
-All 21 tools wrap published Vectros HTTP API endpoints. JSON
+All 22 tools wrap published Vectros HTTP API endpoints. JSON
 responses are what the agent sees as tool output. Per-call cost
 surfaces via the `usage` field on inference responses.