run_query runs read-only by default and points at MANTICORE_ALLOW_WRITE_ACCESS as the switch, with the server's own permissions still sitting above that — so an agent holding this tool cannot alter an index by accident. The documentation side is shaped around cost rather than completeness: the manual's file list is cached locally so filtering is instant, the listing tool asks explicitly for one call using pipe alternation rather than several, and get_documentation then fetches only the file and the context around what matched.
A Manticore Search client: SQL execution, schema inspection, and a searchable copy of the Manticore manual.
- run_query, which executes SQL against Manticore Search in read-only mode by default.
- list_tables for the available tables and indexes with their types, and describe_table for one table's schema.
- list_documentation, which filters the manual's file list — the list is cached, so filtering is instant and local — and takes regex alternation so several topics are found in a single call.
- get_documentation, which fetches a manual file with before and after context around matched content.
MANTICORE_HOST and MANTICORE_PORT for the Manticore server. MANTICORE_ALLOW_WRITE_ACCESS set to true if you want DDL and DML statements, and a Manticore server that permits them; without it, queries run read-only.
One command — uvx mcp-manticore