Meilisearch MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MEILI_HTTP_ADDR | No | Default Meilisearch URL | http://localhost:7700 |
| MEILI_MASTER_KEY | No | Optional: Default Meilisearch API key |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get-connection-settingsB | Get current Meilisearch connection settings |
| update-connection-settingsC | Update Meilisearch connection settings |
| health-checkB | Check Meilisearch server health |
| get-versionB | Get Meilisearch version information |
| get-statsC | Get database statistics |
| create-indexC | Create a new Meilisearch index |
| list-indexesB | List all Meilisearch indexes |
| delete-indexC | Delete a Meilisearch index |
| get-documentsC | Get documents from an index |
| add-documentsC | Add documents to an index |
| get-settingsC | Get current settings for an index |
| update-settingsC | Update settings for an index |
| searchB | Search through Meilisearch indices. If indexUid is not provided, it will search across all indices. |
| get-taskC | Get information about a specific task |
| get-tasksC | Get list of tasks with optional filters |
| cancel-tasksC | Cancel tasks based on filters |
| get-keysC | Get list of API keys |
| create-keyC | Create a new API key |
| delete-keyC | Delete an API key |
| get-health-statusB | Get comprehensive health status of Meilisearch |
| get-index-metricsC | Get detailed metrics for an index |
| get-system-infoC | Get system-level information |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 22 tools
Most tools have distinct purposes targeting specific resources like indexes, documents, tasks, keys, or settings, with clear boundaries. However, get-health-status and health-check could cause confusion as they both relate to health monitoring, though their descriptions differ slightly (comprehensive vs. basic check).
Tool names follow a consistent verb-noun pattern with hyphens throughout, such as create-index, get-documents, and update-settings. There are no deviations in style or convention, making the set predictable and easy to parse.
With 22 tools, the count is on the higher side but reasonable for a comprehensive Meilisearch server covering indexes, documents, tasks, keys, settings, and system info. It feels slightly heavy but not excessive, as each tool serves a specific function in the domain.
The tool set provides complete CRUD/lifecycle coverage for Meilisearch operations, including index management (create, delete, list), document handling (add, get, search), task monitoring (get, cancel), key management (create, delete, get), and settings (get, update). No obvious gaps are present for the server's purpose.