consult7 vs Elasticsearch MCP Server

Implements a BaseProvider interface abstraction layer that unifies three distinct LLM providers (OpenRouter, Google AI, OpenAI) into a single consultation API. Each provider implements provider-specific features (OpenRouter's reasoning mode with |thinking suffix, Google's native ThinkingConfig, OpenAI's O-series effort-based thinking) while exposing a common interface through the PROVIDERS registry in providers/__init__.py. This enables seamless switching between providers and models without changing client code.

Unique: Uses a modular BaseProvider interface with provider-specific reasoning mode support (OpenRouter |thinking suffix, Google ThinkingConfig, OpenAI effort-based thinking) rather than lowest-common-denominator abstraction, allowing clients to opt-in to advanced features while maintaining code portability across providers.

vs alternatives: Provides tighter integration with reasoning model features than generic LLM SDKs (like LangChain), enabling direct access to provider-specific thinking modes without wrapper overhead.

Processes file collections through file_processor.py with automatic wildcard pattern expansion (e.g., *.py, *_test.js), enforces safety limits (1MB per file, 4MB total collection), and auto-ignores sensitive paths (__pycache__, .env, secrets.py, .DS_Store, .git, node_modules). Requires absolute file paths starting with / for security. This enables safe, scalable analysis of large codebases without manual file enumeration or accidental inclusion of secrets.

Unique: Combines automatic pattern expansion with hardcoded safety patterns (auto-ignoring __pycache__, .env, secrets.py, .git, node_modules) and enforces absolute paths for security, rather than requiring users to manually exclude sensitive files or trust relative path resolution.

vs alternatives: Prevents accidental secret exposure more reliably than generic file collection tools by auto-ignoring common sensitive paths and requiring absolute paths, reducing the risk of misconfiguration in automated analysis pipelines.

Implements token_utils.py for pre-request token counting via estimate_tokens(), validates content fits within model context limits, manages thinking token budgets for reasoning modes, and dynamically retrieves context length from model metadata. This enables safe analysis of large files without exceeding model limits or wasting thinking tokens on models that don't support reasoning.

Unique: Combines pre-request token estimation with thinking-mode-aware budget allocation and dynamic context length retrieval, rather than treating token counting as a post-hoc concern. This enables proactive validation before expensive API calls and intelligent reasoning token allocation for O-series and Gemini models.

vs alternatives: Provides tighter integration with reasoning model token budgets than generic LLM clients, enabling explicit control over thinking token allocation rather than relying on provider defaults.

Implements a Model Context Protocol (MCP) server (src/consult7/server.py) that exposes consultation capabilities as MCP tools, enabling AI agents (like Claude) to invoke file analysis through standardized tool calls. The server handles MCP protocol marshalling, tool registration, and request routing to the consultation engine. This allows Claude and other MCP-compatible agents to analyze codebases as a native capability without custom integrations.

Unique: Implements a full MCP server rather than a simple HTTP API, enabling native integration with Claude and other MCP-compatible agents. This allows agents to invoke analysis as a first-class capability without custom HTTP handling or context switching.

vs alternatives: Provides deeper integration with Claude than REST API wrappers, enabling agents to invoke analysis natively through MCP tools without additional HTTP client code or context management overhead.

Enables analysis queries to leverage provider-specific reasoning modes: OpenRouter's |thinking suffix for extended reasoning, Google's native ThinkingConfig for Gemini models, and OpenAI's effort-based thinking for O-series models. The consultation engine routes reasoning requests to the appropriate provider and manages thinking token allocation. This allows complex codebase analysis to benefit from extended reasoning without manual prompt engineering.

Unique: Abstracts provider-specific reasoning modes (OpenRouter |thinking suffix, Google ThinkingConfig, OpenAI effort-based thinking) into a unified reasoning interface, allowing clients to request reasoning without knowing provider details. Manages thinking token budgets explicitly rather than relying on provider defaults.

vs alternatives: Provides unified access to reasoning modes across multiple providers, whereas most tools lock users into a single provider's reasoning implementation. Enables cost-aware reasoning token allocation rather than unlimited thinking.

Enables analysis of large codebases by leveraging models with 1M+ token context windows (Google Gemini 2.5 Pro, OpenAI GPT-5 400K, OpenRouter Claude Sonnet 4). The consultation engine formats file collections into a single context window and routes to appropriate high-context models. This allows comprehensive codebase analysis in a single query without chunking or multiple round-trips.

Unique: Specifically targets 1M+ token models and enforces collection limits (4MB) that align with these models' capabilities, rather than treating large-context analysis as a generic use case. Provides explicit routing to high-context models and token budget management for expensive queries.

vs alternatives: Enables single-query analysis of large codebases, whereas chunking-based approaches (like LangChain) require multiple queries and lose cross-file context. Provides explicit cost and latency management for high-context models rather than treating them as drop-in replacements.

Analyzes code and document collections to generate comprehensive documentation by leveraging large-context models. The consultation engine accepts file collections and documentation queries, formats them into a single context, and returns structured documentation output. This enables automated documentation generation that understands full codebase context rather than isolated files.

Unique: Leverages full-codebase context (up to 1M tokens) for documentation generation, enabling documentation that understands cross-file dependencies and architecture, rather than generating documentation from isolated files or limited context.

vs alternatives: Produces more comprehensive and architecturally-aware documentation than file-by-file tools because it analyzes entire codebases in a single context, capturing cross-file relationships and system design.

Enforces security constraints on file collection through absolute path requirements (/path/to/file), auto-ignores sensitive paths (.env, secrets.py, .git, node_modules), and validates file access permissions before inclusion. This prevents accidental exposure of API keys, credentials, or private configuration in analysis requests sent to external LLM providers.

Unique: Combines absolute path requirements with hardcoded auto-ignore patterns (.env, secrets.py, .git, node_modules) to prevent secret exposure, rather than relying on user configuration or manual exclusion lists. This shifts security burden from users to the tool.

vs alternatives: Prevents accidental secret exposure more reliably than generic file collection tools by making secret prevention the default behavior rather than an opt-in feature. Absolute path requirements reduce misconfiguration risk compared to relative path tools.

Exposes the _cat/indices Elasticsearch API through MCP to list all available indices with their metadata (size, document count, health status). The server acts as a protocol bridge that translates MCP tool calls into native Elasticsearch REST API requests, handling authentication and transport protocol abstraction (stdio, HTTP, SSE) transparently. This enables LLM clients to discover and inspect the data landscape before executing queries.

Unique: Rust-based MCP server bridges Elasticsearch _cat/indices API directly into Claude Desktop and other MCP clients without requiring custom API wrappers, supporting multiple transport protocols (stdio, HTTP, SSE) from a single binary

vs alternatives: Simpler than building custom REST API wrappers because it uses standardized MCP protocol that Claude Desktop natively understands, eliminating the need for separate authentication and transport layer management

Retrieves Elasticsearch field mappings via the _mapping API, exposing the complete schema (field names, data types, analyzers, nested structures) for one or more indices. The server translates MCP tool parameters into Elasticsearch mapping requests and returns structured field metadata that LLMs can use to understand data structure before constructing queries. Supports inspection of nested fields, keyword vs text analysis, and custom analyzer configurations.

Unique: Exposes Elasticsearch _mapping API through MCP protocol, allowing Claude and other LLM clients to introspect field schemas directly without requiring separate schema documentation or custom API endpoints

vs alternatives: More accurate than relying on LLM training data about Elasticsearch because it queries live mappings from the actual cluster, ensuring schema-aware query generation matches the current index structure

The project uses Renovate for automated dependency management, scanning Cargo.toml for outdated dependencies and submitting pull requests weekly. This ensures the Rust codebase stays current with security patches and bug fixes in upstream libraries (Elasticsearch client, MCP protocol, async runtime). The automation reduces manual maintenance burden and improves security posture by catching vulnerable dependencies automatically.

Unique: Renovate automation scans Cargo.toml weekly and submits pull requests for outdated dependencies, ensuring Elasticsearch MCP stays current with security patches without manual intervention

vs alternatives: More proactive than manual dependency updates because it automatically detects outdated packages; more reliable than ignoring updates because it catches security vulnerabilities before they become critical

Executes arbitrary Elasticsearch Query DSL queries via the _search API, supporting full-text search, filtering, aggregations, and complex boolean logic. The MCP server accepts Query DSL JSON payloads, translates them into Elasticsearch requests with proper authentication, and returns paginated results with hit counts and relevance scores. Supports all Elasticsearch query types (match, term, range, bool, aggregations) and handles response pagination through size/from parameters.

Unique: Rust MCP server directly proxies Elasticsearch Query DSL without query transformation or validation, allowing LLMs to construct and execute complex queries while maintaining full Elasticsearch semantics and performance characteristics

vs alternatives: More flexible than pre-built search templates because it accepts arbitrary Query DSL, enabling LLMs to generate context-specific queries; faster than REST API wrappers because it uses native Elasticsearch client libraries in Rust

Executes ES|QL (Elasticsearch SQL-like query language) queries via the _query API with ES|QL syntax support. The server translates ES|QL statements into Elasticsearch requests and returns tabular results. This capability bridges SQL-familiar users and LLMs to Elasticsearch by providing a SQL-like interface while leveraging Elasticsearch's distributed query engine. Supports ES|QL syntax including FROM, WHERE, GROUP BY, STATS, and other clauses.

Unique: Exposes Elasticsearch ES|QL API through MCP, enabling LLMs to generate SQL-like queries that execute against Elasticsearch clusters without requiring Query DSL knowledge or custom SQL-to-DSL translation layers

vs alternatives: More intuitive for SQL-familiar users and LLMs than Query DSL because ES|QL uses familiar SQL syntax; enables faster query generation because LLMs have stronger training data for SQL than for Elasticsearch-specific DSL

Retrieves shard allocation information via the _cat/shards API, exposing how data is distributed across cluster nodes. The server returns shard IDs, node assignments, shard state (STARTED, RELOCATING, etc.), and storage sizes. This capability enables visibility into cluster health, data distribution, and potential bottlenecks. Useful for understanding cluster topology before executing large queries or diagnosing performance issues.

Unique: Rust MCP server exposes _cat/shards API through standardized MCP protocol, allowing LLM clients and monitoring tools to inspect cluster topology without requiring custom Elasticsearch client libraries or REST API wrappers

vs alternatives: Simpler than building custom monitoring dashboards because it exposes raw shard data through MCP that any client can consume; more accessible than Elasticsearch Kibana because it works with any MCP-compatible client including Claude Desktop

The MCP server implements three transport protocols (stdio for desktop integration, HTTP for web services, SSE for real-time streaming) through a unified Rust architecture. The core MCP tool implementations are protocol-agnostic; transport is handled by a pluggable layer that translates between protocol-specific message formats and internal MCP structures. This allows the same server binary to be deployed in different environments (Claude Desktop, web services, containerized systems) without code changes.

Unique: Rust-based MCP server implements protocol abstraction layer that decouples tool implementations from transport, enabling single binary to support stdio (Claude Desktop), HTTP (web services), and SSE (streaming) without duplicating business logic

vs alternatives: More flexible than single-protocol servers because it supports multiple deployment patterns from one codebase; more maintainable than separate servers for each protocol because transport logic is centralized and tested once

The server supports three Elasticsearch authentication methods (API key via ES_API_KEY, basic auth via ES_USERNAME/ES_PASSWORD, and mTLS certificates) through environment variable configuration. Authentication is handled at the connection layer, transparently applied to all Elasticsearch API calls. The server also supports SSL/TLS configuration with optional certificate verification bypass via ES_SSL_SKIP_VERIFY for development environments. This abstraction allows deployment in different security contexts without code changes.

Unique: Rust MCP server abstracts Elasticsearch authentication at connection layer, supporting API keys, basic auth, and mTLS through environment variables without exposing credentials to MCP clients or requiring per-request authentication

vs alternatives: More secure than passing credentials through MCP messages because authentication is handled server-side; more flexible than hardcoded credentials because it supports multiple authentication methods through environment configuration