Skip to main content
Glama
OrionPotter

Meilisearch MCP Server

by OrionPotter

enable-vector-search

Activate vector search functionality in Meilisearch to enable semantic similarity-based document retrieval.

Instructions

Enable the vector search experimental feature in Meilisearch

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler function that enables the vector search experimental feature by posting to the Meilisearch /experimental-features endpoint with vectorStore: true, and returns the response or error.
      async () => {
        try {
          const response = await apiClient.post('/experimental-features', {
            vectorStore: true,
          });
          return {
            content: [{ type: "text", text: JSON.stringify(response.data, null, 2) }],
          };
        } catch (error) {
          return createErrorResponse(error);
        }
      }
    );
  • Registers the enable-vector-search tool on the MCP server with no input schema and the inline handler function.
    server.tool(
      "enable-vector-search",
      "Enable the vector search experimental feature in Meilisearch",
      {},
      async () => {
        try {
          const response = await apiClient.post('/experimental-features', {
            vectorStore: true,
          });
          return {
            content: [{ type: "text", text: JSON.stringify(response.data, null, 2) }],
          };
        } catch (error) {
          return createErrorResponse(error);
        }
      }
    );
  • src/index.ts:68-68 (registration)
    Registers all vector tools, including enable-vector-search, by calling registerVectorTools on the main MCP server instance.
    registerVectorTools(server);
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions enabling an 'experimental feature,' hinting at potential instability or changes, but fails to detail critical aspects like required permissions, side effects (e.g., if it affects other operations), rate limits, or what happens upon success/failure. This leaves significant gaps for a mutation tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, direct sentence that efficiently conveys the core action without any fluff or unnecessary words. It's front-loaded and wastes no space, making it highly concise and well-structured.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (a mutation with no parameters) and lack of annotations or output schema, the description is minimally complete. It states what the tool does but omits behavioral details like effects, permissions, or return values. For a mutation tool, this is adequate but leaves clear gaps, scoring as the minimum viable.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has 0 parameters, and schema description coverage is 100%, so no parameter documentation is needed. The description doesn't add parameter details, which is appropriate, but it could briefly note the lack of inputs. A baseline of 4 is applied as it adequately handles the zero-parameter case without redundancy.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Enable') and the resource ('vector search experimental feature in Meilisearch'), making the purpose specific and understandable. However, it doesn't explicitly differentiate from siblings like 'get-experimental-features' or 'vector-search', which would require a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives such as 'get-experimental-features' (to check status) or 'vector-search' (to use the feature). It lacks context about prerequisites, timing, or exclusions, offering minimal usage direction.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/OrionPotter/iflow-mcp_meilisearch-ts-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server