@snokam/mcp-api 0.111.0 → 0.111.1

package/dist/index.js

@@ -111,13 +111,13 @@ const resetUrlToolDef = {
 const SWITCH_DOMAIN_TOOL_NAME = "SwitchDomain";
 const switchDomainToolDef = {
     name: SWITCH_DOMAIN_TOOL_NAME,
-    description: "Point all Snokam API calls at a specific business's API domain, so the same MCP can serve any tenant. Pass the business's API domain (custom, e.g. api.acme.com, or its snosky fallback, e.g. api.acme.snosky.no); calls then go to {service}.{domain}. Pass an empty string to reset to the environment default (snokam).",
+    description: "Point all Snokam API calls at a specific business's API domain, so the same MCP can serve any tenant. Pass the business's API domain (custom, e.g. api.acme.com, or its snosky fallback, e.g. api.acme.snosky.no); calls then go to {service}.{domain}. Pass an empty string to reset to the platform-wide snosky default.",
     inputSchema: {
         type: "object",
         properties: {
             domain: {
                 type: "string",
-                description: "The business's API base domain (e.g. api.acme.com). Empty string resets to the snokam default.",
+                description: "The business's API base domain (e.g. api.acme.com). Empty string resets to the platform-wide snosky default.",
             },
         },
         required: ["domain"],

package/dist/openapi-loader.d.ts

@@ -1,10 +1,11 @@
 /**
  * Fetch OpenAPI specs from live Snokam APIs and produce tool definitions.
  *
- * Each backend function is available at `{service}.api.snokam.no` (prod)
- * or `{service}.api.test.snokam.no` (test). The loader fetches `/swagger.json`
- * from each, extracts endpoints, parameters, and OAuth scopes to generate
- * MCP-compatible tool metadata.
+ * Backends are reached on the platform-wide snosky domain, which is uniform
+ * across every business (no per-customer hostname): `{service}.api.snosky.no`
+ * (prod) or `{service}.api.test.snosky.no` (test). A specific business domain
+ * can still be targeted at runtime via the SwitchDomain tool. The loader
+ * extracts endpoints, parameters, and OAuth scopes for MCP tool metadata.
  */
 export interface ApiEndpoint {
     service: string;

package/dist/openapi-loader.js

@@ -1,10 +1,11 @@
 /**
  * Fetch OpenAPI specs from live Snokam APIs and produce tool definitions.
  *
- * Each backend function is available at `{service}.api.snokam.no` (prod)
- * or `{service}.api.test.snokam.no` (test). The loader fetches `/swagger.json`
- * from each, extracts endpoints, parameters, and OAuth scopes to generate
- * MCP-compatible tool metadata.
+ * Backends are reached on the platform-wide snosky domain, which is uniform
+ * across every business (no per-customer hostname): `{service}.api.snosky.no`
+ * (prod) or `{service}.api.test.snosky.no` (test). A specific business domain
+ * can still be targeted at runtime via the SwitchDomain tool. The loader
+ * extracts endpoints, parameters, and OAuth scopes for MCP tool metadata.
  */
 // ---------------------------------------------------------------------------
 // Service discovery - reads from bundled specs directory at runtime
@@ -30,8 +31,8 @@ async function discoverServices(environment) {
 // ---------------------------------------------------------------------------
 // Environment-aware URL resolution
 // ---------------------------------------------------------------------------
-const PROD_DOMAIN = "api.snokam.no";
-const TEST_DOMAIN = "api.test.snokam.no";
+const PROD_DOMAIN = "api.snosky.no";
+const TEST_DOMAIN = "api.test.snosky.no";
 function getBaseDomain(environment) {
     return environment === "test" ? TEST_DOMAIN : PROD_DOMAIN;
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@snokam/mcp-api",
-  "version": "0.111.0",
+  "version": "0.111.1",
   "description": "MCP server exposing Snokam backend APIs as tools for Claude Code and other MCP clients",
   "type": "module",
   "bin": {