Elasticsearch MCP Server

Created By
FynnianBa year ago
Elasticsearch Integration with MCP - Multi-team and multi-environment support
Overview

What is Elasticsearch MCP Server?

Elasticsearch MCP Server is a Model Context Protocol (MCP) server designed for integrating Elasticsearch with support for multiple teams and environments. It enables AI assistants to efficiently search exceptions, analyze patterns, and query logs across various teams in a secure manner.

How to use Elasticsearch MCP Server?

To use the server, install it via npm and configure the necessary environment variables and team settings in a JSON configuration file. You can run the server in either STDIO mode for MCP clients or HTTP mode for web interfaces.

Key features of Elasticsearch MCP Server?

  • Multi-team support with individual Elasticsearch clusters
  • Multi-environment support for development, staging, and production
  • Flexible exception search with filtering and sorting
  • Deep analysis of exceptions with suggested solutions
  • Trend analysis for exception patterns and service health
  • Log search capabilities with various filters
  • Connection testing for Elasticsearch clusters
  • Support for both HTTP and STDIO transport protocols

Use cases of Elasticsearch MCP Server?

  1. Investigating exceptions related to specific commits or pull requests.
  2. Monitoring service health by analyzing exception trends over time.
  3. Debugging application issues by searching logs for specific error messages.

FAQ from Elasticsearch MCP Server?

  • Can I configure multiple teams?

Yes! The server supports multiple teams, each with its own Elasticsearch cluster.

  • How do I install the server?

You can install it using npm with the command npm install.

  • What transport protocols does it support?

The server supports both HTTP+SSE and STDIO transport protocols.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
FynnianB
Star
0
Language
TypeScript
License
MIT license

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