openobserve-community-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OO_TOKEN | No | Bearer token for authentication. | |
| OO_ORG_ID | No | Optional organization ID. Required if the credentials have access to more than one organization. | |
| OO_BASE_URL | No | Base URL of the OpenObserve server (e.g., https://openobserve.example.com) | |
| OO_PASSWORD | No | Password for basic authentication. | |
| OO_USERNAME | No | Username for basic authentication. | |
| OO_AUTH_MODE | No | Authentication mode to use ('basic' or 'bearer'). | |
| OO_VERIFY_SSL | No | Whether to verify SSL certificates (true/false). | true |
| OO_CONFIG_FILE | No | Optional explicit path to a config file (.env format). | |
| OO_TIMEOUT_SECONDS | No | Timeout for requests in seconds. | 20 |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_streamsC | List streams available in the current organization. |
| get_stream_schemaA | Get schema information for a specific stream. Use this first to confirm real field names before writing SQL; many log streams expose |
| search_logsA | Run a full SQL search against OpenObserve logs. Example row query: SELECT _timestamp, message FROM "my_stream" ORDER BY _timestamp DESC LIMIT 20. Example aggregate query: SELECT level, count(*) AS cnt FROM "my_stream" GROUP BY level ORDER BY cnt DESC LIMIT 20. Prefer double quotes around stream names in SQL when in doubt, and confirm actual field names with get_stream_schema instead of assuming a |
| search_aroundA | Fetch records around a specific log entry. key accepts Unix timestamps in seconds, milliseconds, microseconds, or nanoseconds for convenience, but the best input is the exact |
| search_valuesA | Get distinct field values for a stream over a time range. stream_name is the raw stream name path segment, for example my_stream; do not quote it like SQL. fields is a comma-separated field list. filter_query uses OpenObserve's _values filter syntax, e.g. kubernetes_pod_namespace=litellm. Simple SQL-like equality such as kubernetes_pod_namespace='litellm' is normalized automatically. start_time and end_time accept Unix timestamps in seconds, milliseconds, microseconds, or nanoseconds and are normalized to microseconds. In this tool, total means the number of field groups returned, not the total number of matching log records. |
| list_dashboardsC | List dashboards in the current organization. |
| get_dashboardB | Get a dashboard definition by id. |
| get_latest_tracesB | Get the latest trace data from a trace stream. start_time and end_time accept Unix timestamps in seconds, milliseconds, microseconds, or nanoseconds and are normalized to microseconds. |
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 has a distinct purpose, but search_logs and search_around both target log entries and could be confused without reading descriptions carefully. However, descriptions clearly differentiate them.
All tool names follow a consistent verb_noun pattern using snake_case, with verbs like get, list, search applied appropriately.
With 8 tools covering dashboards, streams, logs, traces, schema, and values, the count is well-suited for an observability MCP server.
The tool set covers key querying operations but lacks lifecycle management (create/update/delete) for dashboards and streams, and there is no dedicated search_traces tool beyond get_latest_traces.