openobserve-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| O2_ORG | No | Organization id | default |
| O2_URL | No | Base URL of the OpenObserve instance | http://localhost:5080 |
| O2_USER | Yes | Login email | |
| O2_PASSWORD | Yes | Password |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_streamsA | List available streams (logs, metrics, traces) in OpenObserve |
| get_schemaA | Get the field names and types for a stream |
| get_org_summaryA | Get organization summary: stream count, storage, pipelines, alerts, dashboards |
| search_logsA | Search logs with an optional SQL WHERE clause, newest first |
| aggregate_logsA | Run an aggregation query (COUNT, AVG, SUM, GROUP BY). Write the table name as |
| search_tracesA | List recent traces with their root operation, duration, and participating services |
| get_traceA | Get every span of a single trace, ordered by start time |
| query_metricsA | Query metrics with PromQL over a time range (Prometheus query_range) |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Each tool targets a distinct aspect of OpenObserve: streams, schema, org summary, logs, traces, metrics. Search vs. aggregate vs. query are clearly differentiated by descriptions, and search_traces vs. get_trace are separate listing vs. detail operations.
All tool names use snake_case with a verb_noun structure (list_, get_, search_, aggregate_, query_). The verbs accurately reflect the operation, and the nouns denote the target resource. This is highly predictable.
With 8 tools covering streams, schema, logs, traces, and metrics, the surface is well-scoped without being bloated. Each tool fills a necessary role for an observability MCP server.
The set provides a comprehensive read-only query surface: listing streams, inspecting schemas, searching and aggregating logs, listing traces with details, and querying metrics. No obvious dead ends or missing critical operations for the core domain.