@mushi-mushi/mcp 0.21.0 → 0.22.0

package/dist/server.d.ts

@@ -57,12 +57,25 @@ interface MushiServerConfig {
      * Explicit values are honoured as given — tests use small ones.
      */
     timeoutMs?: number;
+    /** Server instructions override — createSetupModeServer uses it. Defaults to MUSHI_SERVER_INSTRUCTIONS. */
+    instructions?: string;
+}
+declare function createMushiServer(config: MushiServerConfig): McpServer;
+/** Tools that work before an API key exists: they read only the public docs. */
+declare const SETUP_MODE_TOOLS: readonly ["search_mushi_docs", "get_mushi_doc", "diagnose_setup"];
+interface SetupModeServerConfig {
+    version: string;
+    /** Why there is no key, as printed to stderr (sources checked, config path). */
+    missingKeyReport: string;
+    fetch?: typeof fetch;
+    timeoutMs?: number;
 }
 /**
- * Build an MCP server instance pre-wired with every Mushi tool, resource,
- * and prompt. Does NOT call `server.connect()` — the caller binds whatever
- * transport they need (stdio for the CLI, InMemoryTransport for tests).
+ * The server stdio runs when no API key is configured. It used to exit 1, so
+ * a registry or directory installer (Smithery, Glama) saw a dead server and
+ * an agent saw nothing at all. Setup mode lists the docs tools plus a
+ * diagnose_setup that explains how to connect, and makes no API call.
  */
-declare function createMushiServer(config: MushiServerConfig): McpServer;
+declare function createSetupModeServer(config: SetupModeServerConfig): McpServer;
 
-export { MushiApiError, type MushiServerConfig, createMushiServer, resolveTimeoutMsFromEnv };
+export { MushiApiError, type MushiServerConfig, SETUP_MODE_TOOLS, type SetupModeServerConfig, createMushiServer, createSetupModeServer, resolveTimeoutMsFromEnv };