"Querying Elasticsearch (ES)" matching MCP servers:

Read/write Elasticsearch mcp server with many tools

Connects agents to Elasticsearch data using the Model Context Protocol, allowing natural language interaction with Elasticsearch indices through MCP Clients like Claude Desktop and Cursor.

This is an elasticsearch mcp server developed based on sprint ai.

Enables AI coding agents to fetch live MDN Web Docs pages, TypeScript handbook content, and npm package metadata as clean markdown, with local search, caching, and polite throttling.

Enables AI assistants to search Elasticsearch logs, retrieve log details, analyze service health, scan local codebases for APIs, and create Kibana dashboards.

A local MCP server for querying MQL5 documentation, including reference, algo book, and neural networks book, with tools for search, smart query, error diagnosis, and browsing.

MCP-Server from your Database optimized for LLMs and AI-Agents. Supports PostgreSQL, MySQL, ClickHouse, Snowflake, MSSQL, BigQuery, Oracle Database, SQLite, ElasticSearch, DuckDB

Provides a unified MCP server to interact with multiple middleware (Loki, MySQL, Redis, RocketMQ, Elasticsearch, MongoDB) through a desktop application for connection management and configuration export.

Provides CRUD tools for managing a database of Italian cities backed by Elasticsearch. It enables AI assistants to search, create, update, and delete city records through a standardized Model Context Protocol interface.

Enables querying a TypeScript codebase's graph for call flows, type relationships, and symbol locations without reading file bodies.

. A good description should be concise and describe what the server enables users to do, e.g. * Enables to interact with WordPress sites...' Then a huge block? Actually the user message includes the README content inside tags, then after the readme, there is a large block of text starting with '{

Enables AI agents to search and retrieve 1C:Enterprise 8.3 syntax documentation, including quick references, detailed syntax info, and object members, through MCP tools backed by an Elasticsearch index.

A template for creating MCP servers in Node.js/TypeScript with a modular architecture. It simplifies adding new tools and includes an example Elasticsearch search tool.

Provides read-only database access for AI agents across multiple databases (Postgres, MySQL, MongoDB, Elasticsearch) with enforced read-only guarantees and separate tools for prod and non-prod environments.

An MCP server for querying Grafana Loki directly with a discovery-first workflow — labels, values, series, and LogQL queries without requiring Grafana.

Lets AI agents scaffold modern npm packages, CLIs, HTTP services, and apps as a native tool. Three tools: inspect the full option/preset schema, preview the generated file tree for a config, and write the project to disk.

Read-only MCP server that exposes the agentic-os governance, SDLC, and Quality Engineering methodology to any MCP host. It never writes to your repository and never executes code — it serves the methodology, plans an install, and verifies it, handing any commands back to the host to run.

Provides TypeScript and JavaScript code refactoring operations using ts-morph, allowing AST-based symbol renaming, file/folder renaming, reference searching, and path alias removal when integrated with editor extensions like Cursor.

An MCP server that decompiles and inspects .NET assemblies to C# source, wrapping ILSpy. Enables querying .NET DLLs via natural language to decompile types, list members, and search symbols.

Enables read-only querying of AWS accounts, regions, and resources through a small fixed set of MCP tools backed by a YAML catalog of views.