What authentication methods are supported?
API keys and username/password authentication.
@FynnianB
Basic information
Elasticsearch Integration with MCP - Multi-team and multi-environment support
No standard config provided
This server doesn't expose a parseable MCP config block in its README. See the repository for install instructions.
RepositoryTool list not available yet
This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.
We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.
It is a Model Context Protocol (MCP) server that integrates AI assistants with Elasticsearch, supporting multiple teams and environments. It enables searching exceptions, analyzing patterns, querying logs, and monitoring service health across teams in a secure, organized way.
Install with npm install, create a teams-config.json file based on the example, and set environment variables (LOG_LEVEL, TEAMS_CONFIG_PATH, PORT, HTTP_PATH_PREFIX). Run in STDIO mode with npm run dev or in HTTP mode with npm run start-http.
API keys and username/password authentication.
HTTP+SSE (for web interfaces) and STDIO (for MCP clients).
Create a `teams-config.json` file with separate team objects, each containing team ID, environments, index patterns, and allowed operations.
`maxSearchResults` defaults to 50; for `search_exceptions`, the `limit` parameter defaults to 20 and max is 100.
The default port is 3000, configurable via the `PORT` environment variable.

Model Context Protocol Servers
Universal MCP-Server for your Databases optimized for LLMs and AI-Agents.

Local database MCP server: your agent sees a migration's impact before it runs, for PostgreSQL, MySQL, SQL Server and SQLite, with no database credentials.
A Model Context Protocol (MCP) server implementation that provides database capabilities for Chroma

Model Context Protocol Servers
Comments