chore(mcp-server): remove the package from the monorepo

.changeset/config.json

@@ -2,7 +2,7 @@
   "$schema": "https://unpkg.com/@changesets/config@3.0.0/schema.json",
   "changelog": ["@changesets/changelog-github", { "repo": "hacker-cb/1c-odata" }],
   "commit": false,
-  "fixed": [["@1c-odata/client", "@1c-odata/metadata", "@1c-odata/cli", "@1c-odata/mcp", "@1c-odata/mcp-server"]],
+  "fixed": [["@1c-odata/client", "@1c-odata/metadata", "@1c-odata/cli", "@1c-odata/mcp"]],
   "linked": [],
   "access": "public",
   "baseBranch": "master",

.changeset/mcp-connection-source-seam.md

@@ -2,7 +2,7 @@
 "@1c-odata/mcp": minor
 ---
 
-Refactor `@1c-odata/mcp` for multi-tenant reuse (prep for `@1c-odata/mcp-server`).
+Refactor `@1c-odata/mcp` for multi-tenant reuse (prep for a remote multi-tenant host).
 
 - New `@1c-odata/mcp/internal` subpath exposing the reusable building blocks — `ConnectionPool`, the new `ConnectionSource`/`FileConnectionSource` seam, `ReadPool`, the read-only tool registrators (`registerSchemaTools`/`registerDataTools`/`registerServerInfoTool`), and the response-limit helpers. The connection-management tools stay off this surface (admin-only).
 - `ConnectionPool` now takes a `ConnectionSource` (where connections and secrets come from) instead of `{ dataDir }`; the local stdio server injects a `FileConnectionSource` (config.json + keychain) and is unchanged. The read-only tool registrators now accept a `ReadPool`.

.changeset/mcp-db-secret-source-and-verify-connectivity.md

@@ -2,7 +2,7 @@
 "@1c-odata/mcp": patch
 ---
 
-Prep `@1c-odata/mcp/internal` for a DB-backed multi-tenant host (`@1c-odata/mcp-server`). Additive only — no CLI, MCP-tool, on-disk, or local stdio behavior changed.
+Prep `@1c-odata/mcp/internal` for a DB-backed multi-tenant host. Additive only — no CLI, MCP-tool, on-disk, or local stdio behavior changed.
 
 - `SecretSource` gains a `'db'` variant so a DB-backed `ConnectionSource` can report the real password origin in `list_connections`. `SecretStore` itself never returns it (file/keychain/env only).
 - `@1c-odata/mcp/internal` now re-exports `verifyConnectivity` — the standalone `$metadata` reachability probe (no `dataDir` dependency), reused by a remote host to verify a base before saving it. The connection-management functions (`upsertConnection`/`removeConnection`/`updateConnectionCredentials`/`setConnectionLabel`) stay private — they are bound to the file-backed config.

.changeset/mcp-internal-reexports.md

@@ -0,0 +1,12 @@
+---
+"@1c-odata/mcp": patch
+---
+
+`@1c-odata/mcp/internal` re-exports for alternate hosts:
+
+- `assertValidConnectionName` / `isValidConnectionName`, so a DB-backed admin
+  write path enforces the same ASCII connection-name rule as the file-backed
+  store.
+- `InvalidArgumentError` (from `@1c-odata/client`), so a scoping wrapper throws
+  the pool's canonical not-found error without a new dependency — an ungranted
+  base is then byte-identical to a missing one.

.changeset/node-24-lts-floor.md

@@ -3,7 +3,6 @@
 '@1c-odata/metadata': minor
 '@1c-odata/cli': minor
 '@1c-odata/mcp': minor
-'@1c-odata/mcp-server': minor
 ---
 
 **Breaking:** the minimum supported Node version is now 24.18.0 (was 22.21.0).
@@ -13,9 +12,8 @@ the active LTS line and is supported until 2028-04-30. Installing on Node 22
 will now be refused or warned about by npm/pnpm, depending on your client.
 
 No source change accompanies this. The library does not yet use any API that
-Node 22 lacks — the floor moves so that the version CI exercises, the version
-the published container image runs, and the version the packages advertise are
-one and the same. Keeping the advertised floor below the tested one meant the
+Node 22 lacks — the floor moves so that the version CI exercises and the version
+the packages advertise are one and the same. Keeping the advertised floor below the tested one meant the
 promise was never actually verified, which is the defect this closes.
 
 `@types/node` is pinned to the matching major for the same reason: types