Can I use Meilisearch as a CLI?

Yes. KosmoKrator exposes a Meilisearch CLI through kosmo integrations:call and the provider shortcut command. Commands can return JSON for scripts, CI, and coding agents.

Can I expose Meilisearch through MCP?

Yes. The KosmoKrator MCP gateway can expose selected Meilisearch tools to clients such as Claude Code, Cursor, Codex, and other MCP-compatible tools.

Where are Meilisearch credentials stored?

Meilisearch credentials are configured in KosmoKrator's local integration settings and reused by CLI, Lua, and MCP gateway surfaces.

Can I deny write access for Meilisearch MCP tools?

Yes. Start the gateway with --write=deny for read-only clients, or use ask/allow only for trusted workspaces.

other

Meilisearch CLI for Headless Automation

Use the Meilisearch CLI for headless automation with headless JSON commands, schema discovery, credentials, and permission controls.

7 functions 5 read 2 write API key auth

Submit Meilisearch feedback View package source

Meilisearch CLI for Headless Automation

Use KosmoKrator as a non-interactive integration runtime for local automations and wrappers.

Use headless automation when another tool needs a stable local command surface. The Meilisearch CLI uses the same integration registry as the TUI, Lua runtime, and MCP gateway, but returns predictable command output for automation.

Command Shape

# Meilisearch CLI for Headless Automation
kosmokrator integrations:configure meilisearch --set api_key="$MEILISEARCH_API_KEY" --enable --read allow --write ask --json
kosmo integrations:call meilisearch.meilisearch_list_indexes '{"limit":1,"offset":1}' --json

Discovery Before Execution

Agents and scripts can inspect Meilisearch docs and schemas before choosing a function.

kosmo integrations:docs meilisearch --json
kosmo integrations:docs meilisearch.meilisearch_list_indexes --json
kosmo integrations:schema meilisearch.meilisearch_list_indexes --json
kosmo integrations:search "Meilisearch" --json
kosmo integrations:list --json

Useful Meilisearch CLI Functions

Function	Type	Parameters	Description
`meilisearch.meilisearch_list_indexes`	Read	limit, offset	List all indexes in the Meilisearch instance. Returns index UIDs, primary keys, and creation dates.
`meilisearch.meilisearch_get_index`	Read	uid	Get detailed information about a specific Meilisearch index, including its UID, primary key, and stats.
`meilisearch.meilisearch_create_index`	Write	uid, primary_key	Create a new index in Meilisearch. Returns a task object that can be used to track the creation progress.
`meilisearch.meilisearch_search_documents`	Read	index_uid, q, limit, offset, filter, sort	Search for documents in a Meilisearch index. Supports full-text search with filters, sorting, and pagination.
`meilisearch.meilisearch_add_documents`	Write	index_uid, documents, primary_key	Add or replace documents in a Meilisearch index. Sends an array of document objects to be indexed. Returns a task object to track progress.
`meilisearch.meilisearch_get_document`	Read	index_uid, doc_id	Retrieve a single document from a Meilisearch index by its primary key value.
`meilisearch.meilisearch_get_health`	Read	none	Check the health status of the Meilisearch instance. Returns whether the server is available and operational.

Automation Notes

Use --json for machine-readable output.
Keep credentials out of argv by using environment variables or stored KosmoKrator configuration.
Configure read/write policy before unattended runs; use --force only for trusted automation.
Use the MCP gateway instead when the agent needs dynamic tool discovery inside a conversation.

Related Meilisearch CLI Pages

CI Meilisearch CLI for CI. Cron Jobs Meilisearch CLI for cron jobs. Shell Scripts Meilisearch CLI for shell scripts. Coding Agents Meilisearch CLI for coding agents.