What OpenTelemetry data does this server work with?
It works with traces, metrics, and logs—the three pillars of OpenTelemetry—stored in Elasticsearch or OpenSearch.
@shiftyp
Basic information
No overview available yet
Add this server to your MCP-compatible client using the configuration below.
{
"mcpServers": {
"otel-mcp-server": {
"command": "npx",
"args": [
"-y",
"otel-mcp-server"
],
"env": {
"OPENSEARCH_URL": "http://localhost:9200",
"USERNAME": "elastic",
"PASSWORD": "changeme",
"OPENAI_API_KEY": "sk-..."
}
}
}
}Tool 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.
Fetch the live tool list by running this server in a temporary sandbox using the button above.
This MCP server bridges AI assistants with OpenTelemetry data stored in Elasticsearch/OpenSearch, enabling natural language queries on traces, metrics, and logs. It is for developers, SREs, and anyone needing conversational access to observability data without writing query languages.
Add the server to your MCP settings for Windsurf/Claude Desktop using environment variables like OPENSEARCH_URL, USERNAME, PASSWORD, and optionally OPENAI_API_KEY. For developers, clone the repo, install dependencies, configure .env, build, and integrate with your MCP client via a direct node command to dist/server.js.
It works with traces, metrics, and logs—the three pillars of OpenTelemetry—stored in Elasticsearch or OpenSearch.
You need either `ELASTICSEARCH_URL` or `OPENSEARCH_URL` with credentials, and optionally an `OPENAI_API_KEY` for ML-powered features. The server runs via `npx` or a local Node.js build.
The AI automatically correlates traces, metrics, and logs when answering questions, providing context such as error propagation, latency patterns, and service dependencies.
The server uses standard MCP configuration with environment variable-based authentication (`USERNAME`, `PASSWORD`) for the data store. No other transports are mentioned in the README.
The README does not list explicit known limits; however, it notes that data must be in Elasticsearch/OpenSearch, and it requires an AI assistant (MCP client) to interpret natural language.

Know when your AI agents, cron jobs and CI pipelines fail, stall or go quiet. Your agent sets up monitors from a plain description, tells you what is broken and why, reads run history and traces, and writes notes on inci

Layro connects your AI coding tool (Cursor, Claude Code, VS Code, Windsurf, Codex, Gemini CLI) to 112 production React, TypeScript and Tailwind CSS components. Your agent can search the library, read each component's pro

Modelglass turns "which model should I use?" into a lookup instead of a guess. Seven tools give your agent live pricing across image, language, video, and audio models. Sourced and versioned, not scraped once and forgott

The tools your AI needs to make your games. Turn prompts into production-ready game assets — animated characters with their weapons attached, seamless textures, terrain, VFX, HUDs — and playable game kits Unity, Godot, U
Comments