describe_table
Get the schema of a specific table/index in Manticore Search.
LABSCO SUMMARY
Writing is off until you turn it on, and the tool names the variable that turns it on.
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.
What it is
A Manticore Search client: SQL execution, schema inspection, and a searchable copy of the Manticore manual.
What you get
- 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.
Requirements
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.
Setup effort
One command — uvx mcp-manticore
USE CASES
01
Getting oriented in an unfamiliar Manticore instance
The tables and their types come back first, then one table's schema, and a read-only query answers what the schema alone cannot — all without any ability to alter an index.
02
Writing a query against Manticore's own syntax
The manual is searchable from the same session, with the file list cached so filtering is instant and several topics found in one call using pipe alternation, and only the matched file and its surrounding context fetched.
5 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
get_documentation
Fetch documentation from Manticore Search manual.
Use list_documentation() first to discover available files.
list_documentation
List available documentation files from Manticore Search manual.
IMPORTANT: Make ONE call with regex OR patterns to find multiple topics at once. DO NOT make multiple calls - use pipe (|) to combine patterns.
The file list is cached, so filtering is instant and local.
list_tables
List available tables/indexes in Manticore Search.
Returns: JSON string containing list of table names and their types
run_query
Execute a SQL query against Manticore Search.
Queries run in read-only mode by default. Set MANTICORE_ALLOW_WRITE_ACCESS=true to allow DDL and DML statements when your Manticore server permits them.
BEFORE YOU INSTALL
What to know first
Tools you get
5 tools when we connected. Writes are blocked by default: set MANTICORE_ALLOW_WRITE_ACCESS=true for INSERT, UPDATE and DELETE, and MANTICORE_ALLOW_DROP=true for DROP and TRUNCATE. The same tools appear either way; run_query refuses the blocked SQL.
Requires
uvx on PATH
Where it runs
All 9 documented clients run the server on your machine.
CONTEXT COST
Light Standing cost
Rated by the size of the 5 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
TERMINAL
uvx mcp-manticoreMCP Clients
Claude Code, Cursor, Windsurf, Gemini CLI, Cline, Roo Code, Claude Desktop
JSON
{
"mcpServers": {
"manticore": {
"command": "uvx",
"args": [
"mcp-manticore"
],
"env": {
"MANTICORE_HOST": "localhost",
"MANTICORE_PORT": "9308"
}
}
}
}Codex
CODEX · TOML
[mcp_servers.manticore]
command = "uvx"
args = ["mcp-manticore"]
[mcp_servers.manticore.env]
MANTICORE_HOST = "localhost"
MANTICORE_PORT = "9308"VS Code
VS CODE · JSON
{
"servers": {
"manticore": {
"type": "stdio",
"command": "uvx",
"args": [
"mcp-manticore"
],
"env": {
"MANTICORE_HOST": "localhost",
"MANTICORE_PORT": "9308"
}
}
}
}
