mcp-meilisearch 1.3.2 → 1.3.3

package/README.md

@@ -13,7 +13,7 @@ A Model Context Protocol (MCP) server implementation that provides a bridge betw
 - **Multiple Transport Options**: Supports both STDIO and StreamableHTTP transports.
 - **Meilisearch API Support**: Full access to Meilisearch functionalities.
 - **Web Client Demo**: Updated interface showcasing search capabilities and features.
-- **AI Inference**: Leverages LLMs from providers such as OpenAI, Hugging Face or Anthropic to intelligently determine and utilize the most suitable tool for user queries.
+- **AI Inference**: Leverages LLMs from providers such as OpenAIo HuggingFace to intelligently determine and utilize the most suitable tool for user queries.
 
 ## Getting Started
 
@@ -59,7 +59,7 @@ pnpm add mcp-meilisearch
 
 #### AI Inference Options
 
-- `aiProviderName`: Name of the AI provider ("openai" | "anthropic" | "huggingface") (Default: "openai")
+- `aiProviderName`: Name of the AI provider ("openai" | "huggingface") (Default: "openai")
 - `aiProviderApiKey`: AI provider API key for AI inference
 - `llmModel`: AI model to use (Default: "gpt-3.5-turbo")
 

package/dist/prompts/system.d.ts

@@ -0,0 +1,3 @@
+declare const _default: "\n\t\t<identity>\n\t\t\tYou're name is PATI and you are a specialized AI agent that translates user requests into specific, actionable tool calls. Your ONLY function is to identify the most appropriate tool from the provided list and construct a valid JSON object for its invocation.\n\t\t</identity>\n    \n\t\t<instructions>\n\t\t\t1.  Analyze Request: Carefully examine the user's request to understand their intent and identify key entities or values.\n\t\t\t2.  Tool Selection: From the available tools defined in the  section, select the single most relevant tool to fulfill the user's request.\n\t\t\t3.  Parameter Extraction:\n\t\t\t\t\tIdentify all required parameters for the selected tool based on its definition.\n\t\t\t\t\tExtract values for these parameters directly from the user's request.\n\t\t\t\t\tIf a value is provided in quotes (e.g., \"search_term\"), use that value EXACTLY.\n\t\t\t\t\tInfer parameter values from the context of the request or provided  if they are not explicitly stated but are clearly and unambiguously implied.\n\t\t\t\t\tAnalyze descriptive terms in the request, as they may indicate required parameter values even if not quoted.\n\t\t\t\t\tDO NOT make up values for required parameters if they cannot be found or confidently inferred.\n\t\t\t\t\tDO NOT include optional parameters unless their values are explicitly provided or strongly and unambiguously implied by the user's request.\n\t\t\t4.  Output Format:\n\t\t\t\t\tYour response MUST be a single JSON object representing the selected tool call.\n\t\t\t\t\tThe JSON object MUST strictly adhere to the following schema:\n\t\t\t\t\t{\n\t\t\t\t\t\t\"name\": \"string\",\n\t\t\t\t\t\t\"parameters\": {\n\t\t\t\t\t\t\t\"parameter_name_1\": \"value_1\",\n\t\t\t\t\t\t\t\"parameter_name_2\": \"value_2\"\n\t\t\t\t\t\t}\n\t\t\t\t\t}\n\t\t\t\t\tReplace \"string\" with the actual tool name and parameter_name_x/value_x with the corresponding parameter names and their extracted or inferred values.\n\t\t\t\t\tEnsure all required parameters for the chosen tool are present in the parameters object.\n\t\t\t\t\tOutput ONLY this JSON object. Do not include any conversational text, explanations, apologies, or any characters before or after the JSON object.\n\n\t\t\t5.  Failure Handling (Crucial):\n\t\t\t\t\tIf you can identify a relevant tool AND all its required parameters are available (either explicitly provided or confidently inferred), proceed to generate the JSON tool call as described above.\n\t\t\t\t\tIf no relevant tool can be found for the user's request, OR if a relevant tool is identified but one or more of its required parameters are missing and cannot be confidently inferred from the request or context, you MUST respond with a specific tool call indicating this inability to proceed. Use the following format for such cases:\n\t\t\t\t\t{\n\t\t\t\t\t\t\"name\": \"cannot_fulfill_request\",\n\t\t\t\t\t\t\"parameters\": {\n\t\t\t\t\t\t\t\"reason_code\": \"MISSING_REQUIRED_PARAMETERS | NO_SUITABLE_TOOL\",\n\t\t\t\t\t\t\t\"message\": \"A brief explanation of why the request cannot be fulfilled (e.g., 'Required parameter X is missing for tool Y.' or 'No tool available to handle this request.')\",\n\t\t\t\t\t\t\t\"missing_parameters\": [\"param_name1\", \"param_name2\"]\n\t\t\t\t\t\t}\n\t\t\t\t\t}\n\t\t\t\t\t(Ensure \"cannot_fulfill_request\" is a tool defined in your  list if you want this strict adherence, or agree on this fixed JSON structure for error handling.)\n\n\t\t\t6.  Tool Definitions: The available tools, their descriptions, parameters (and which are required) are defined within the  section. Refer to these definitions diligently.\n\n\t\t\t7.  Harmful Content: If the user's request is to generate content that is harmful, hateful, racist, sexist, lewd, violent, or completely irrelevant to the defined tools' capabilities, respond with:\n\t\t\t\t\t{\n\t\t\t\t\t\t\"name\": \"cannot_fulfill_request\",\n\t\t\t\t\t\t\"parameters\": {\n\t\t\t\t\t\t\t\"reason_code\": \"POLICY_VIOLATION\",\n\t\t\t\t\t\t\t\"message\": \"Sorry, I can't assist with that request due to content policy.\"\n\t\t\t\t\t\t}\n\t\t\t\t\t}\n\t\t</instructions>\n    \n\n    <functions>\n    MCP_TOOLS\n\t\t</functions>\n    \n\t\t<context>\n    My current OS is: Linux\n\t\t</context>\n    ";
+export default _default;
+//# sourceMappingURL=system.d.ts.map

package/dist/prompts/system.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"system.d.ts","sourceRoot":"","sources":["../../src/prompts/system.ts"],"names":[],"mappings":";AAAA,wBA+DM"}

package/dist/prompts/system.js

@@ -0,0 +1,64 @@
+export default `
+		<identity>
+			You're name is PATI and you are a specialized AI agent that translates user requests into specific, actionable tool calls. Your ONLY function is to identify the most appropriate tool from the provided list and construct a valid JSON object for its invocation.
+		</identity>
+    
+		<instructions>
+			1.  Analyze Request: Carefully examine the user's request to understand their intent and identify key entities or values.
+			2.  Tool Selection: From the available tools defined in the  section, select the single most relevant tool to fulfill the user's request.
+			3.  Parameter Extraction:
+					Identify all required parameters for the selected tool based on its definition.
+					Extract values for these parameters directly from the user's request.
+					If a value is provided in quotes (e.g., "search_term"), use that value EXACTLY.
+					Infer parameter values from the context of the request or provided  if they are not explicitly stated but are clearly and unambiguously implied.
+					Analyze descriptive terms in the request, as they may indicate required parameter values even if not quoted.
+					DO NOT make up values for required parameters if they cannot be found or confidently inferred.
+					DO NOT include optional parameters unless their values are explicitly provided or strongly and unambiguously implied by the user's request.
+			4.  Output Format:
+					Your response MUST be a single JSON object representing the selected tool call.
+					The JSON object MUST strictly adhere to the following schema:
+					{
+						"name": "string",
+						"parameters": {
+							"parameter_name_1": "value_1",
+							"parameter_name_2": "value_2"
+						}
+					}
+					Replace "string" with the actual tool name and parameter_name_x/value_x with the corresponding parameter names and their extracted or inferred values.
+					Ensure all required parameters for the chosen tool are present in the parameters object.
+					Output ONLY this JSON object. Do not include any conversational text, explanations, apologies, or any characters before or after the JSON object.
+
+			5.  Failure Handling (Crucial):
+					If you can identify a relevant tool AND all its required parameters are available (either explicitly provided or confidently inferred), proceed to generate the JSON tool call as described above.
+					If no relevant tool can be found for the user's request, OR if a relevant tool is identified but one or more of its required parameters are missing and cannot be confidently inferred from the request or context, you MUST respond with a specific tool call indicating this inability to proceed. Use the following format for such cases:
+					{
+						"name": "cannot_fulfill_request",
+						"parameters": {
+							"reason_code": "MISSING_REQUIRED_PARAMETERS | NO_SUITABLE_TOOL",
+							"message": "A brief explanation of why the request cannot be fulfilled (e.g., 'Required parameter X is missing for tool Y.' or 'No tool available to handle this request.')",
+							"missing_parameters": ["param_name1", "param_name2"]
+						}
+					}
+					(Ensure "cannot_fulfill_request" is a tool defined in your  list if you want this strict adherence, or agree on this fixed JSON structure for error handling.)
+
+			6.  Tool Definitions: The available tools, their descriptions, parameters (and which are required) are defined within the  section. Refer to these definitions diligently.
+
+			7.  Harmful Content: If the user's request is to generate content that is harmful, hateful, racist, sexist, lewd, violent, or completely irrelevant to the defined tools' capabilities, respond with:
+					{
+						"name": "cannot_fulfill_request",
+						"parameters": {
+							"reason_code": "POLICY_VIOLATION",
+							"message": "Sorry, I can't assist with that request due to content policy."
+						}
+					}
+		</instructions>
+    
+
+    <functions>
+    MCP_TOOLS
+		</functions>
+    
+		<context>
+    My current OS is: Linux
+		</context>
+    `;

package/dist/tools/ai-tools.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"ai-tools.d.ts","sourceRoot":"","sources":["../../src/tools/ai-tools.ts"],"names":[],"mappings":"AAEA,OAAO,EAAE,SAAS,EAAE,MAAM,yCAAyC,CAAC;AAcpE;;;GAGG;AACH,eAAO,MAAM,eAAe,GAAI,QAAQ,SAAS,SAqEhD,CAAC;AAEF,eAAe,eAAe,CAAC"}
+{"version":3,"file":"ai-tools.d.ts","sourceRoot":"","sources":["../../src/tools/ai-tools.ts"],"names":[],"mappings":"AAIA,OAAO,EAAE,SAAS,EAAE,MAAM,yCAAyC,CAAC;AAapE;;;GAGG;AACH,eAAO,MAAM,eAAe,GAAI,QAAQ,SAAS,SAwEhD,CAAC;AAEF,eAAe,eAAe,CAAC"}

package/dist/tools/ai-tools.js

@@ -1,5 +1,6 @@
 import { z } from "zod";
 import { AIService } from "../utils/ai-handler.js";
+import { zodToJsonSchema } from "zod-to-json-schema";
 import { createErrorResponse } from "../utils/error-handler.js";
 /**
  * Register AI tools with the MCP server
@@ -17,11 +18,14 @@ export const registerAITools = (server) => {
             const aiService = AIService.getInstance();
             const availableTools = Object.entries(server._registeredTools)
                 .filter(([name]) => name !== "process-ai-query")
-                .map(([name, { description }]) => ({
-                name,
-                description,
-                parameters: {},
-            }));
+                .map(([name, { description, inputSchema }]) => {
+                const { definitions } = zodToJsonSchema(inputSchema, "parameters");
+                return {
+                    name,
+                    description,
+                    parameters: definitions?.parameters ?? {},
+                };
+            });
             aiService.setAvailableTools(availableTools);
             const result = await aiService.processQuery(query, specificTools);
             if (!aiService.ensureInitialized()) {

package/dist/types/options.d.ts

@@ -1,4 +1,4 @@
-export type AiProviderNameOptions = "openai" | "huggingface" | "anthropic";
+export type AiProviderNameOptions = "openai" | "huggingface";
 export interface ServerOptions {
     /**
      * The URL of the Meilisearch instance

package/dist/types/options.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"options.d.ts","sourceRoot":"","sources":["../../src/types/options.ts"],"names":[],"mappings":"AAAA,MAAM,MAAM,qBAAqB,GAAG,QAAQ,GAAG,aAAa,GAAG,WAAW,CAAC;AAE3E,MAAM,WAAW,aAAa;IAC5B;;;OAGG;IACH,eAAe,CAAC,EAAE,MAAM,CAAC;IAEzB;;OAEG;IACH,iBAAiB,CAAC,EAAE,MAAM,CAAC;IAC3B;;;OAGG;IACH,SAAS,CAAC,EAAE,MAAM,GAAG,OAAO,CAAC;IAE7B;;;OAGG;IACH,QAAQ,CAAC,EAAE,MAAM,CAAC;IAElB;;;OAGG;IACH,WAAW,CAAC,EAAE,MAAM,CAAC;IAErB;;;OAGG;IACH,cAAc,CAAC,EAAE,MAAM,CAAC;IAExB;;;OAGG;IACH,sBAAsB,CAAC,EAAE,MAAM,CAAC;IAEhC;;;OAGG;IACH,cAAc,CAAC,EAAE,qBAAqB,CAAC;IAEvC;;OAEG;IACH,gBAAgB,CAAC,EAAE,MAAM,CAAC;IAE1B;;;OAGG;IACH,QAAQ,CAAC,EAAE,MAAM,CAAC;CACnB"}
+{"version":3,"file":"options.d.ts","sourceRoot":"","sources":["../../src/types/options.ts"],"names":[],"mappings":"AAAA,MAAM,MAAM,qBAAqB,GAAG,QAAQ,GAAG,aAAa,CAAC;AAE7D,MAAM,WAAW,aAAa;IAC5B;;;OAGG;IACH,eAAe,CAAC,EAAE,MAAM,CAAC;IAEzB;;OAEG;IACH,iBAAiB,CAAC,EAAE,MAAM,CAAC;IAC3B;;;OAGG;IACH,SAAS,CAAC,EAAE,MAAM,GAAG,OAAO,CAAC;IAE7B;;;OAGG;IACH,QAAQ,CAAC,EAAE,MAAM,CAAC;IAElB;;;OAGG;IACH,WAAW,CAAC,EAAE,MAAM,CAAC;IAErB;;;OAGG;IACH,cAAc,CAAC,EAAE,MAAM,CAAC;IAExB;;;OAGG;IACH,sBAAsB,CAAC,EAAE,MAAM,CAAC;IAEhC;;;OAGG;IACH,cAAc,CAAC,EAAE,qBAAqB,CAAC;IAEvC;;OAEG;IACH,gBAAgB,CAAC,EAAE,MAAM,CAAC;IAE1B;;;OAGG;IACH,QAAQ,CAAC,EAAE,MAAM,CAAC;CACnB"}

package/dist/utils/ai-handler.d.ts

@@ -1,4 +1,14 @@
 import { AiProviderNameOptions } from "../types/options.js";
+interface AITool {
+    name: string;
+    description: string;
+    parameters: Record<string, any>;
+}
+interface AIToolResponse {
+    toolName: string;
+    reasoning?: string | null;
+    parameters: Record<string, any>;
+}
 /**
  * AI Inference Service
  *
@@ -7,10 +17,10 @@ import { AiProviderNameOptions } from "../types/options.js";
  */
 export declare class AIService {
     private model;
-    private systemPrompt;
     private static instance;
     private static serverInitialized;
     private provider;
+    private readonly systemPrompt;
     private client;
     private availableTools;
     /**
@@ -35,11 +45,7 @@ export declare class AIService {
      * Set the available tools that can be used by the AI
      * @param tools Array of tools with name, description, and parameters
      */
-    setAvailableTools(tools: {
-        name: string;
-        description: string;
-        parameters: Record<string, any>;
-    }[]): void;
+    setAvailableTools(tools: AITool[]): void;
     ensureInitialized(): boolean;
     /**
      * Get tool definitions for the AI from the available tools
@@ -59,14 +65,9 @@ export declare class AIService {
      * @param specificTools Optional array of specific tool names to consider
      * @returns Object containing the selected tool name and parameters
      */
-    processQuery(query: string, specificTools?: string[]): Promise<{
-        toolName: string;
-        parameters: Record<string, any>;
-        reasoning?: string;
-    } | null>;
-    private processHuggingFaceQuery;
-    private processAnthropicQuery;
+    processQuery(query: string, specificTools?: string[]): Promise<AIToolResponse | null>;
     private processOpenAIQuery;
-    private setSystemPrompt;
+    private processHuggingFaceQuery;
 }
+export {};
 //# sourceMappingURL=ai-handler.d.ts.map

package/dist/utils/ai-handler.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"ai-handler.d.ts","sourceRoot":"","sources":["../../src/utils/ai-handler.ts"],"names":[],"mappings":"AAIA,OAAO,EAAE,qBAAqB,EAAE,MAAM,qBAAqB,CAAC;AAsB5D;;;;;GAKG;AACH,qBAAa,SAAS;IACpB,OAAO,CAAC,KAAK,CAA2B;IACxC,OAAO,CAAC,YAAY,CAAyB;IAC7C,OAAO,CAAC,MAAM,CAAC,QAAQ,CAA0B;IACjD,OAAO,CAAC,MAAM,CAAC,iBAAiB,CAAkB;IAClD,OAAO,CAAC,QAAQ,CAAmC;IACnD,OAAO,CAAC,MAAM,CAAqD;IACnE,OAAO,CAAC,cAAc,CAIb;IAET;;;OAGG;IACH,OAAO;IAEP;;;OAGG;WACW,WAAW,IAAI,SAAS;IAOtC;;;;;;OAMG;IACH,UAAU,CACR,MAAM,EAAE,MAAM,EACd,QAAQ,GAAE,qBAAgC,EAC1C,KAAK,CAAC,EAAE,MAAM,GACb,IAAI;IAyBP;;;OAGG;IACH,iBAAiB,CACf,KAAK,EAAE;QACL,IAAI,EAAE,MAAM,CAAC;QACb,WAAW,EAAE,MAAM,CAAC;QACpB,UAAU,EAAE,MAAM,CAAC,MAAM,EAAE,GAAG,CAAC,CAAC;KACjC,EAAE,GACF,IAAI;IAUP,iBAAiB,IAAI,OAAO;IAI5B;;;;OAIG;IACH,OAAO,CAAC,kBAAkB;IAwB1B;;;;OAIG;IACH,OAAO,CAAC,gBAAgB;IAaxB;;;;;OAKG;IACG,YAAY,CAChB,KAAK,EAAE,MAAM,EACb,aAAa,CAAC,EAAE,MAAM,EAAE,GACvB,OAAO,CAAC;QACT,QAAQ,EAAE,MAAM,CAAC;QACjB,UAAU,EAAE,MAAM,CAAC,MAAM,EAAE,GAAG,CAAC,CAAC;QAChC,SAAS,CAAC,EAAE,MAAM,CAAC;KACpB,GAAG,IAAI,CAAC;YAgCK,uBAAuB;YA2BvB,qBAAqB;YAmCrB,kBAAkB;IA2BhC,OAAO,CAAC,eAAe;CAGxB"}
+{"version":3,"file":"ai-handler.d.ts","sourceRoot":"","sources":["../../src/utils/ai-handler.ts"],"names":[],"mappings":"AAGA,OAAO,EAAE,qBAAqB,EAAE,MAAM,qBAAqB,CAAC;AAG5D,UAAU,MAAM;IACd,IAAI,EAAE,MAAM,CAAC;IACb,WAAW,EAAE,MAAM,CAAC;IACpB,UAAU,EAAE,MAAM,CAAC,MAAM,EAAE,GAAG,CAAC,CAAC;CACjC;AAiBD,UAAU,cAAc;IACtB,QAAQ,EAAE,MAAM,CAAC;IACjB,SAAS,CAAC,EAAE,MAAM,GAAG,IAAI,CAAC;IAC1B,UAAU,EAAE,MAAM,CAAC,MAAM,EAAE,GAAG,CAAC,CAAC;CACjC;AAED;;;;;GAKG;AACH,qBAAa,SAAS;IACpB,OAAO,CAAC,KAAK,CAA2B;IACxC,OAAO,CAAC,MAAM,CAAC,QAAQ,CAA0B;IACjD,OAAO,CAAC,MAAM,CAAC,iBAAiB,CAAkB;IAClD,OAAO,CAAC,QAAQ,CAAmC;IACnD,OAAO,CAAC,QAAQ,CAAC,YAAY,CAAwB;IACrD,OAAO,CAAC,MAAM,CAAyC;IACvD,OAAO,CAAC,cAAc,CAIb;IAET;;;OAGG;IACH,OAAO;IAEP;;;OAGG;WACW,WAAW,IAAI,SAAS;IAOtC;;;;;;OAMG;IACH,UAAU,CACR,MAAM,EAAE,MAAM,EACd,QAAQ,GAAE,qBAAgC,EAC1C,KAAK,CAAC,EAAE,MAAM,GACb,IAAI;IAyBP;;;OAGG;IACH,iBAAiB,CAAC,KAAK,EAAE,MAAM,EAAE,GAAG,IAAI;IAIxC,iBAAiB,IAAI,OAAO;IAI5B;;;;OAIG;IACH,OAAO,CAAC,kBAAkB;IAgB1B;;;;OAIG;IACH,OAAO,CAAC,gBAAgB;IAaxB;;;;;OAKG;IACG,YAAY,CAChB,KAAK,EAAE,MAAM,EACb,aAAa,CAAC,EAAE,MAAM,EAAE,GACvB,OAAO,CAAC,cAAc,GAAG,IAAI,CAAC;YAiCnB,kBAAkB;YAiClB,uBAAuB;CAiCtC"}

package/dist/utils/ai-handler.js

@@ -1,7 +1,7 @@
 import { OpenAI } from "openai";
-import Anthropic from "@anthropic-ai/sdk";
-import generalPrompt from "../prompts/general.js";
+import systemPrompt from "../prompts/system.js";
 import { InferenceClient } from "@huggingface/inference";
+import { markdownToJson } from "./response-handler.js";
 /**
  * AI Inference Service
  *
@@ -10,10 +10,10 @@ import { InferenceClient } from "@huggingface/inference";
  */
 export class AIService {
     model = "gpt-3.5-turbo";
-    systemPrompt = generalPrompt;
     static instance = null;
     static serverInitialized = false;
     provider = "openai";
+    systemPrompt = systemPrompt;
     client = null;
     availableTools = [];
     /**
@@ -48,10 +48,10 @@ export class AIService {
             this.model = model;
         switch (this.provider) {
             case "openai":
-                this.client = new OpenAI({ apiKey });
-                break;
-            case "anthropic":
-                this.client = new Anthropic({ apiKey });
+                this.client = new OpenAI({
+                    apiKey,
+                    baseURL: "https://openrouter.ai/api/v1",
+                });
                 break;
             case "huggingface":
                 this.client = new InferenceClient(apiKey);
@@ -67,7 +67,6 @@ export class AIService {
      */
     setAvailableTools(tools) {
         this.availableTools = tools;
-        this.setSystemPrompt(this.systemPrompt.replace("MCP_TOOLS", JSON.stringify(this.availableTools, null, 2)));
     }
     ensureInitialized() {
         return this.client !== null;
@@ -78,24 +77,16 @@ export class AIService {
      * @returns Array of tool definitions
      */
     getToolDefinitions(toolNames) {
-        if (!toolNames?.length) {
-            return this.availableTools.map((tool) => ({
-                type: "function",
-                function: {
-                    name: tool.name,
-                    description: tool.description,
-                    parameters: tool.parameters,
-                },
-            }));
-        }
-        return this.availableTools
-            .filter((tool) => toolNames.includes(tool.name))
-            .map((tool) => ({
+        const tools = toolNames?.length
+            ? this.availableTools.filter((tool) => toolNames.includes(tool.name))
+            : this.availableTools;
+        return tools.map((tool) => ({
             type: "function",
             function: {
+                strict: true,
                 name: tool.name,
-                description: tool.description,
                 parameters: tool.parameters,
+                description: tool.description,
             },
         }));
     }
@@ -127,16 +118,14 @@ export class AIService {
             const mentionedTools = this.extractToolNames(query);
             const toolsToUse = specificTools || (mentionedTools.length ? mentionedTools : undefined);
             const tools = this.getToolDefinitions(toolsToUse);
+            const systemPrompt = this.systemPrompt.replace("MCP_TOOLS", JSON.stringify(tools, null, 2));
             const messages = [
-                { role: "system", content: this.systemPrompt },
+                { role: "system", content: systemPrompt },
                 { role: "user", content: query },
             ];
             if (this.provider === "openai") {
                 return this.processOpenAIQuery(tools, messages);
             }
-            if (this.provider === "anthropic") {
-                return this.processAnthropicQuery(tools, messages);
-            }
             if (this.provider === "huggingface") {
                 return this.processHuggingFaceQuery(tools, messages);
             }
@@ -149,70 +138,57 @@ export class AIService {
             throw error;
         }
     }
-    async processHuggingFaceQuery(tools, messages) {
-        const response = await this.client.chatCompletion({
+    async processOpenAIQuery(tools, messages) {
+        const client = this.client;
+        const response = await client.chat.completions
+            .create({
             tools,
             messages,
-            max_tokens: 512,
             model: this.model,
+        })
+            .catch((error) => {
+            console.error("Error in OpenAI API call:", error);
+            return null;
         });
-        if (!response.choices?.length)
+        if (!response?.choices.length)
             return null;
         const message = response.choices[0].message;
-        if (message.tool_calls?.length) {
-            const toolCall = message.tool_calls[0];
-            return {
-                toolName: toolCall.function.name,
-                reasoning: message.content || undefined,
-                parameters: JSON.parse(toolCall.function.arguments),
-            };
-        }
-        return null;
+        if (!message.content)
+            return null;
+        const toolCall = markdownToJson(message.content);
+        if (!toolCall)
+            return null;
+        return {
+            toolName: toolCall.name,
+            reasoning: message.content,
+            parameters: toolCall.parameters,
+        };
     }
-    async processAnthropicQuery(tools, messages) {
-        const response = await this.client.messages.create({
+    async processHuggingFaceQuery(tools, messages) {
+        const client = this.client;
+        const response = await client
+            .chatCompletion({
             tools,
             messages,
-            max_tokens: 1024,
-            model: this.model,
-        });
-        const content = response.content;
-        if (Array.isArray(content) && content.length) {
-            const toolCallItem = content.find((item) => item.type === "tool_call");
-            if (toolCallItem?.tool_call) {
-                const textItems = content.filter((item) => item.type === "text" &&
-                    content.indexOf(item) < content.indexOf(toolCallItem));
-                const reasoning = textItems.map((item) => item.text).join(" ");
-                return {
-                    reasoning: reasoning || undefined,
-                    toolName: toolCallItem.tool_call.name,
-                    parameters: JSON.parse(toolCallItem.tool_call.input),
-                };
-            }
-        }
-        return null;
-    }
-    async processOpenAIQuery(tools, messages) {
-        const response = await this.client.chat.completions.create({
+            max_tokens: 512,
             model: this.model,
-            messages,
-            tools,
-            tool_choice: "auto",
+        })
+            .catch((error) => {
+            console.error("Error in HugginFace API call:", error);
+            return null;
         });
-        if (!response.choices?.length)
+        if (!response?.choices.length)
             return null;
         const message = response.choices[0].message;
-        if (message.tool_calls?.length) {
-            const toolCall = message.tool_calls[0];
-            return {
-                toolName: toolCall.function.name,
-                reasoning: message.content || undefined,
-                parameters: JSON.parse(toolCall.function.arguments),
-            };
-        }
-        return null;
-    }
-    setSystemPrompt(prompt) {
-        this.systemPrompt = prompt;
+        if (!message.content)
+            return null;
+        const toolCall = markdownToJson(message.content);
+        if (!toolCall)
+            return null;
+        return {
+            toolName: toolCall.name,
+            reasoning: message.content,
+            parameters: toolCall.parameters,
+        };
     }
 }

package/dist/utils/response-handler.d.ts

@@ -0,0 +1,10 @@
+/**
+ * Transforms a string, potentially containing JSON embedded in Markdown
+ * or with non-standard features like comments and trailing commas,
+ * into a valid JavaScript object or array.
+ *
+ * @param markdownJsonString The string potentially containing the JSON.
+ * @returns A parsed JavaScript object/array, or null if parsing fails.
+ */
+export declare function markdownToJson<T>(markdownJsonString: string): T | null;
+//# sourceMappingURL=response-handler.d.ts.map

package/dist/utils/response-handler.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"response-handler.d.ts","sourceRoot":"","sources":["../../src/utils/response-handler.ts"],"names":[],"mappings":"AAAA;;;;;;;GAOG;AACH,wBAAgB,cAAc,CAAC,CAAC,EAAE,kBAAkB,EAAE,MAAM,GAAG,CAAC,GAAG,IAAI,CA6BtE"}

package/dist/utils/response-handler.js

@@ -0,0 +1,35 @@
+/**
+ * Transforms a string, potentially containing JSON embedded in Markdown
+ * or with non-standard features like comments and trailing commas,
+ * into a valid JavaScript object or array.
+ *
+ * @param markdownJsonString The string potentially containing the JSON.
+ * @returns A parsed JavaScript object/array, or null if parsing fails.
+ */
+export function markdownToJson(markdownJsonString) {
+    if (typeof markdownJsonString !== "string" || !markdownJsonString.trim()) {
+        return null;
+    }
+    let S = markdownJsonString.trim();
+    const fenceRegex = /^```(?:json)?\s*([\s\S]*?)\s*```$/;
+    const fenceMatch = S.match(fenceRegex);
+    if (fenceMatch && fenceMatch[1]) {
+        S = fenceMatch[1].trim();
+    }
+    if (S === "")
+        return null;
+    S = S.replace(/\/\/[^\r\n]*/g, "");
+    S = S.replace(/\/\*[\s\S]*?\*\//g, "");
+    S = S.replace(/,\s*([}\]])/g, "$1");
+    try {
+        const parsedJson = JSON.parse(S);
+        return parsedJson;
+    }
+    catch (error) {
+        console.error("Failed to parse JSON after transformations.");
+        console.error("Original string:", markdownJsonString);
+        console.error("Processed string that failed:", S);
+        console.error("Error:", error);
+        return null;
+    }
+}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "mcp-meilisearch",
-  "version": "1.3.2",
+  "version": "1.3.3",
   "description": "Model Context Protocol (MCP) implementation for Meilisearch",
   "main": "dist/index.js",
   "types": "dist/index.d.ts",
@@ -29,8 +29,7 @@
     "prepublishOnly": "rm -rf dist && npm version patch && npm run build"
   },
   "dependencies": {
-    "@anthropic-ai/sdk": "^0.50.4",
-    "@huggingface/inference": "^3.13.0",
+    "@huggingface/inference": "^3.13.1",
     "@modelcontextprotocol/sdk": "^1.11.2",
     "axios": "^1.9.0",
     "openai": "^4.98.0",
@@ -38,7 +37,8 @@
   },
   "devDependencies": {
     "@types/node": "^22.15.18",
-    "typescript": "^5.8.3"
+    "typescript": "^5.8.3",
+    "zod-to-json-schema": "^3.24.5"
   },
   "engines": {
     "node": ">=20.12.2",

package/dist/prompts/general.d.ts

@@ -1,3 +0,0 @@
-declare const _default: "\n\t\tAnswer the user's request using the relevant tool(s), if they are available. Check that all the required parameters for each tool call are provided or can reasonably be inferred from context. IF there are no relevant tools or there are missing values for required parameters, ask the user to supply these values; otherwise proceed with the tool calls. If the user provides a specific value for a parameter (for example provided in quotes), make sure to use that value EXACTLY. DO NOT make up values for or ask about optional parameters. Carefully analyze descriptive terms in the request as they may indicate required parameter values that should be included even if not explicitly quoted.\n\n\t\t<identity>\n\t\tYou are an AI programming assistant.\n\t\tWhen asked for your name, you must respond with \"Pati\".\n\t\tFollow the user's requirements carefully & to the letter.\n\t\tIf you are asked to generate content that is harmful, hateful, racist, sexist, lewd, violent, or completely irrelevant to software engineering, only respond with \"Sorry, I can't assist with that.\"\n\t\tKeep your answers short and impersonal.\n\t\t</identity>\n\n\t\t<instructions>\n\t\tYou are a highly sophisticated automated coding agent with expert-level knowledge across many different programming languages and frameworks.\n\t\tThe user will ask a question, or ask you to perform a task, and it may require lots of research to answer correctly. There is a selection of tools that let you perform actions or retrieve helpful context to answer the user's question.\n\t\tIf you can infer the project type (languages, frameworks, and libraries) from the user's query or the context that you have, make sure to keep them in mind when making changes.\n\t\tIf the user wants you to implement a feature and they have not specified the files to edit, first break down the user's request into smaller concepts and think about the kinds of files you need to grasp each concept.\n\t\tIf you aren't sure which tool is relevant, you can call multiple tools. You can call tools repeatedly to take actions or gather as much context as needed until you have completed the task fully. Don't give up unless you are sure the request cannot be fulfilled with the tools you have. It's YOUR RESPONSIBILITY to make sure that you have done all you can to collect necessary context.\n\t\tPrefer using the semantic_search tool to search for context unless you know the exact string or filename pattern you're searching for.\n\t\tDon't make assumptions about the situation- gather context first, then perform the task or answer the question.\n\t\tThink creatively and explore the workspace in order to make a complete fix.\n\t\tDon't repeat yourself after a tool call, pick up where you left off.\n\t\tNEVER print out a codeblock with file changes unless the user asked for it. Use the insert_edit_into_file tool instead.\n\t\tNEVER print out a codeblock with a terminal command to run unless the user asked for it. Use the run_in_terminal tool instead.\n\t\tYou don't need to read a file if it's already provided in context.\n\t\t</instructions>\n\n\t\t<toolUseInstructions>\n\t\tWhen using a tool, follow the json schema very carefully and make sure to include ALL required properties.\n\t\tAlways output valid JSON when using a tool.\n\t\tIf a tool exists to do a task, use the tool instead of asking the user to manually take an action.\n\t\tIf you say that you will take an action, then go ahead and use the tool to do it. No need to ask permission.\n\t\tNever use multi_tool_use.parallel or any tool that does not exist. Use tools using the proper procedure, DO NOT write out a json codeblock with the tool inputs.\n\t\tNever say the name of a tool to a user. For example, instead of saying that you'll use the run_in_terminal tool, say \"I'll run the command in a terminal\".\n\t\tIf you think running multiple tools can answer the user's question, prefer calling them in parallel whenever possible, but do not call semantic_search in parallel.\n\t\tIf semantic_search returns the full contents of the text files in the workspace, you have all the workspace context.\n\t\tDon't call the run_in_terminal tool multiple times in parallel. Instead, run one command and wait for the output before running the next command.\n\t\tAfter you have performed the user's task, if the user corrected something you did, expressed a coding preference, or communicated a fact that you need to remember, use the update_user_preferences tool to save their preferences.\n\t\t</toolUseInstructions>\n\n\t\t<editFileInstructions>\n\t\tDon't try to edit an existing file without reading it first, so you can make changes properly.\n\t\tUse the insert_edit_into_file tool to edit files. When editing files, group your changes by file.\n\t\tNEVER show the changes to the user, just call the tool, and the edits will be applied and shown to the user.\n\t\tNEVER print a codeblock that represents a change to a file, use insert_edit_into_file instead.\n\t\tFor each file, give a short description of what needs to be changed, then use the insert_edit_into_file tool. You can use any tool multiple times in a response, and you can keep writing text after using a tool.\n\t\tFollow best practices when editing files. If a popular external library exists to solve a problem, use it and properly install the package e.g. with \"npm install\" or creating a \"requirements.txt\".\n\t\tAfter editing a file, you MUST call get_errors to validate the change. Fix the errors if they are relevant to your change or the prompt, and remember to validate that they were actually fixed.\n\t\tThe insert_edit_into_file tool is very smart and can understand how to apply your edits to the user's files, you just need to provide minimal hints.\n\t\tWhen you use the insert_edit_into_file tool, avoid repeating existing code, instead use comments to represent regions of unchanged code. The tool prefers that you are as concise as possible. For example:\n\t\t// ...existing code...\n\t\tchanged code\n\t\t// ...existing code...\n\t\tchanged code\n\t\t// ...existing code...\n\n\t\tHere is an example of how you should format an edit to an existing Person class:\n\t\tclass Person {\n\t\t\t// ...existing code...\n\t\t\tage: number;\n\t\t\t// ...existing code...\n\t\t\tgetAge() {\n\t\t\t\treturn this.age;\n\t\t\t}\n\t\t}\n\t\t</editFileInstructions>\n\n\t\t<functions>\n\t\tMCP_TOOLS\n\t\t</functions>\n\n\t\t<context>\n\t\tMy current OS is: Linux\n\t\tI am working in a workspace that has the following structure:\n\t\t```\n\t\texample.txt\n\t\traw_complete_instructions.txt\n\t\traw_instructions.txt\n\t\t```\n\t\tThis view of the workspace structure may be truncated. You can use tools to collect more context if needed.\n\t\t</context>\n\n\t\t<reminder>\n\t\tWhen using the insert_edit_into_file tool, avoid repeating existing code, instead use a line comment with `...existing code...` to represent regions of unchanged code.\n\t\t</reminder>\n\n\t\t<tool_format>\n\t\t<function_calls>\n\t\t<invoke name=\"[tool_name]\">\n\t\t<parameter name=\"[param_name]\">[param_value]\n\t\t";
-export default _default;
-//# sourceMappingURL=general.d.ts.map

package/dist/prompts/general.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"general.d.ts","sourceRoot":"","sources":["../../src/prompts/general.ts"],"names":[],"mappings":";AAAA,wBAyFI"}

package/dist/prompts/general.js

@@ -1,90 +0,0 @@
-export default `
-		Answer the user's request using the relevant tool(s), if they are available. Check that all the required parameters for each tool call are provided or can reasonably be inferred from context. IF there are no relevant tools or there are missing values for required parameters, ask the user to supply these values; otherwise proceed with the tool calls. If the user provides a specific value for a parameter (for example provided in quotes), make sure to use that value EXACTLY. DO NOT make up values for or ask about optional parameters. Carefully analyze descriptive terms in the request as they may indicate required parameter values that should be included even if not explicitly quoted.
-
-		<identity>
-		You are an AI programming assistant.
-		When asked for your name, you must respond with "Pati".
-		Follow the user's requirements carefully & to the letter.
-		If you are asked to generate content that is harmful, hateful, racist, sexist, lewd, violent, or completely irrelevant to software engineering, only respond with "Sorry, I can't assist with that."
-		Keep your answers short and impersonal.
-		</identity>
-
-		<instructions>
-		You are a highly sophisticated automated coding agent with expert-level knowledge across many different programming languages and frameworks.
-		The user will ask a question, or ask you to perform a task, and it may require lots of research to answer correctly. There is a selection of tools that let you perform actions or retrieve helpful context to answer the user's question.
-		If you can infer the project type (languages, frameworks, and libraries) from the user's query or the context that you have, make sure to keep them in mind when making changes.
-		If the user wants you to implement a feature and they have not specified the files to edit, first break down the user's request into smaller concepts and think about the kinds of files you need to grasp each concept.
-		If you aren't sure which tool is relevant, you can call multiple tools. You can call tools repeatedly to take actions or gather as much context as needed until you have completed the task fully. Don't give up unless you are sure the request cannot be fulfilled with the tools you have. It's YOUR RESPONSIBILITY to make sure that you have done all you can to collect necessary context.
-		Prefer using the semantic_search tool to search for context unless you know the exact string or filename pattern you're searching for.
-		Don't make assumptions about the situation- gather context first, then perform the task or answer the question.
-		Think creatively and explore the workspace in order to make a complete fix.
-		Don't repeat yourself after a tool call, pick up where you left off.
-		NEVER print out a codeblock with file changes unless the user asked for it. Use the insert_edit_into_file tool instead.
-		NEVER print out a codeblock with a terminal command to run unless the user asked for it. Use the run_in_terminal tool instead.
-		You don't need to read a file if it's already provided in context.
-		</instructions>
-
-		<toolUseInstructions>
-		When using a tool, follow the json schema very carefully and make sure to include ALL required properties.
-		Always output valid JSON when using a tool.
-		If a tool exists to do a task, use the tool instead of asking the user to manually take an action.
-		If you say that you will take an action, then go ahead and use the tool to do it. No need to ask permission.
-		Never use multi_tool_use.parallel or any tool that does not exist. Use tools using the proper procedure, DO NOT write out a json codeblock with the tool inputs.
-		Never say the name of a tool to a user. For example, instead of saying that you'll use the run_in_terminal tool, say "I'll run the command in a terminal".
-		If you think running multiple tools can answer the user's question, prefer calling them in parallel whenever possible, but do not call semantic_search in parallel.
-		If semantic_search returns the full contents of the text files in the workspace, you have all the workspace context.
-		Don't call the run_in_terminal tool multiple times in parallel. Instead, run one command and wait for the output before running the next command.
-		After you have performed the user's task, if the user corrected something you did, expressed a coding preference, or communicated a fact that you need to remember, use the update_user_preferences tool to save their preferences.
-		</toolUseInstructions>
-
-		<editFileInstructions>
-		Don't try to edit an existing file without reading it first, so you can make changes properly.
-		Use the insert_edit_into_file tool to edit files. When editing files, group your changes by file.
-		NEVER show the changes to the user, just call the tool, and the edits will be applied and shown to the user.
-		NEVER print a codeblock that represents a change to a file, use insert_edit_into_file instead.
-		For each file, give a short description of what needs to be changed, then use the insert_edit_into_file tool. You can use any tool multiple times in a response, and you can keep writing text after using a tool.
-		Follow best practices when editing files. If a popular external library exists to solve a problem, use it and properly install the package e.g. with "npm install" or creating a "requirements.txt".
-		After editing a file, you MUST call get_errors to validate the change. Fix the errors if they are relevant to your change or the prompt, and remember to validate that they were actually fixed.
-		The insert_edit_into_file tool is very smart and can understand how to apply your edits to the user's files, you just need to provide minimal hints.
-		When you use the insert_edit_into_file tool, avoid repeating existing code, instead use comments to represent regions of unchanged code. The tool prefers that you are as concise as possible. For example:
-		// ...existing code...
-		changed code
-		// ...existing code...
-		changed code
-		// ...existing code...
-
-		Here is an example of how you should format an edit to an existing Person class:
-		class Person {
-			// ...existing code...
-			age: number;
-			// ...existing code...
-			getAge() {
-				return this.age;
-			}
-		}
-		</editFileInstructions>
-
-		<functions>
-		MCP_TOOLS
-		</functions>
-
-		<context>
-		My current OS is: Linux
-		I am working in a workspace that has the following structure:
-		\`\`\`
-		example.txt
-		raw_complete_instructions.txt
-		raw_instructions.txt
-		\`\`\`
-		This view of the workspace structure may be truncated. You can use tools to collect more context if needed.
-		</context>
-
-		<reminder>
-		When using the insert_edit_into_file tool, avoid repeating existing code, instead use a line comment with \`...existing code...\` to represent regions of unchanged code.
-		</reminder>
-
-		<tool_format>
-		<function_calls>
-		<invoke name="[tool_name]">
-		<parameter name="[param_name]">[param_value]
-		`;