Manticore Search

Created By
manticoresoftware3 months ago
MCP server for Manticore Search — enables AI assistants to query and manage Manticore Search databases directly. Supports full-text search, KNN vector search, fuzzy search, and real-time data access.
Overview

Manticore Search MCP Server

Enable AI assistants to query and manage Manticore Search databases directly through the Model Context Protocol (MCP).

Features

  • SQL Query Execution - Run SELECT, SHOW, DESCRIBE queries
  • Full-Text Search - Leverage Manticore's powerful full-text search capabilities
  • KNN Vector Search - Perform vector similarity searches
  • Fuzzy Search - Handle typos and approximate matches
  • Real-time Data Access - Live database queries from AI assistants
  • Documentation Access - Built-in Manticore documentation fetcher

Installation

# Install with uvx (recommended)
uvx mcp-manticore

# Or with pip
pip install mcp-manticore

Configuration

Add to your MCP client configuration:

{
  "mcpServers": {
    "manticore": {
      "command": "uvx",
      "args": ["mcp-manticore"],
      "env": {
        "MANTICORE_HOST": "localhost",
        "MANTICORE_PORT": "9308"
      }
    }
  }
}

Environment Variables

VariableDefaultDescription
MANTICORE_HOSTlocalhostManticore server host
MANTICORE_PORT9308HTTP API port
MANTICORE_USER-Username (optional)
MANTICORE_PASSWORD-Password (optional)
MANTICORE_ALLOW_WRITE_ACCESSfalseEnable write operations
MANTICORE_ALLOW_DROPfalseEnable destructive operations
Project Info
Created At
3 months ago
Updated At
3 months ago
Author Name
manticoresoftware
Star
-
Language
-
License
-
Category

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago