Manticore Search MCP
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GITHUB_TOKEN | No | GitHub token for higher API rate limit | |
| MANTICORE_HOST | No | Manticore server host | localhost |
| MANTICORE_PORT | No | HTTP API port | 9308 |
| MANTICORE_USER | No | Username (optional) | |
| MANTICORE_PASSWORD | No | Password (optional) | |
| MANTICORE_ALLOW_DROP | No | Enable destructive operations (DROP, TRUNCATE) | false |
| MANTICORE_MCP_BIND_PORT | No | Bind port for HTTP transport | 8000 |
| MANTICORE_QUERY_TIMEOUT | No | Query timeout (seconds) | 30 |
| MANTICORE_MCP_AUTH_TOKEN | No | Secure token for HTTP transport authentication | |
| MANTICORE_CONNECT_TIMEOUT | No | Connection timeout (seconds) | 30 |
| MANTICORE_ALLOW_WRITE_ACCESS | No | Enable write operations (INSERT, UPDATE, DELETE) | false |
| MANTICORE_MCP_SERVER_TRANSPORT | No | MCP server transport (e.g., 'stdio' or 'http'). Defaults to 'stdio'. |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| run_queryA | 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. Args: query: The SQL query to execute (e.g., "SELECT * FROM my_index LIMIT 10") Returns: A dictionary containing: - columns: List of column names - rows: List of row values - total: Total number of results |
| list_tablesA | List available tables/indexes in Manticore Search. Returns: JSON string containing list of table names and their types |
| describe_tableA | Get the schema of a specific table/index in Manticore Search. Args: table_name: The name of the table/index to describe Returns: A dictionary containing column information including: - columns: List of column names and types |
| list_documentationA | 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. Args: search: Regex pattern to filter files (case-insensitive). Use OR patterns (|) to match multiple topics in ONE call: Returns: Filtered list of documentation files, grouped by category Examples: # List all documentation (no filter) list_documentation() |
| get_documentationA | Fetch documentation from Manticore Search manual. Use list_documentation() first to discover available files. Args: file_path: Path to documentation file (e.g., "Searching/KNN.md") content: Optional search term to filter content (returns only matching sections) before: Number of lines before match to include (default: 0) after: Number of lines after match to include (default: 0) Returns: Documentation content as markdown text Examples: get_documentation( "Searching/Full_text_matching/Operators.md", content="MATCH", before=2, after=2 ) |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| manticore_initial_prompt | Prompt for Manticore Search operations |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool has a distinct and non-overlapping purpose: describe_table for schema inspection, list_tables for inventory, run_query for data retrieval/manipulation, and two documentation tools (list_documentation and get_documentation) that work together as a clear pair. No ambiguity exists between tools.
All tools follow a consistent verb_noun naming pattern (describe_table, get_documentation, list_documentation, list_tables, run_query). The verbs are appropriate and predictable, with no mixing of conventions or styles.
Five tools is well-scoped for a search database server, covering core operations: schema inspection, table listing, query execution, and documentation access. Each tool serves a clear purpose without redundancy or bloat.
The toolset covers essential read operations and documentation access effectively. A minor gap exists in write operations (e.g., create/update/delete tables or documents), though run_query hints at DDL/DML capabilities with server permissions. For a search-focused server, this is reasonable but not fully comprehensive.