Skip to main content
Glama
observe-mcp

observe-mcp

by staffdill

observe-mcp

An MCP server for querying Observe.com logs using OPAL. Compatible with Claude Desktop, Claude Code, and any MCP client.

Tools

Tool

Description

observe_query

Run a raw OPAL pipeline query against any dataset

list_datasets

Discover available datasets in your Observe tenant

inspect_dataset

Live-sample a dataset to see available fields

get_dataset_schema

Return cached field schema (instant, no API call)

search_service_logs

Search logs for a named service

search_entity_logs

Search logs by any field/value pair (userId, requestId, deviceId, etc.)

observe_docs

OPAL language reference and query examples

Related MCP server: openobserve-community-mcp

Configuration

Variable

Required

Description

OBSERVE_CUSTOMER_ID

Yes

Your Observe tenant ID (numeric). Found in your Observe URL: https://<id>.observeinc.com

OBSERVE_TOKEN

Yes

Observe bearer token. Generate at: Observe UI → Settings → API Tokens

OBSERVE_DEFAULT_DATASET

No

Default dataset path used when dataset_path is not passed

Usage with Claude Code

claude mcp add observe docker run -i --rm \
  -e OBSERVE_CUSTOMER_ID=<your-id> \
  -e OBSERVE_TOKEN=<your-token> \
  staffdill/observe-mcp

Usage with Claude Desktop

Add to your claude_desktop_config.json:

{
  "mcpServers": {
    "observe": {
      "command": "docker",
      "args": [
        "run", "-i", "--rm",
        "-e", "OBSERVE_CUSTOMER_ID=<your-id>",
        "-e", "OBSERVE_TOKEN=<your-token>",
        "staffdill/observe-mcp"
      ]
    }
  }
}

Schema Cache

get_dataset_schema returns instant results from a local cache file (data/fields.json). This file is tenant-specific and not included in the image. If the cache is absent, use inspect_dataset for a live field sample instead.

License

MIT

Available Tools

7 tools
get_dataset_schemaA

Return cached field names, example values, and suggested OPAL filter snippets for a dataset. Instant — no API call. Call this before writing any OPAL query. Generate the cache by running the discover script externally.

Inputs: dataset_path.

inspect_datasetA

Sample a dataset to discover available field names and example values. Call this before writing OPAL queries so you know exactly which fields to filter on.

Inputs: pipeline, sample_size, dataset_path.

list_datasetsA

List all datasets in Observe, optionally filtered by name keyword. Use this to discover dataset paths before running queries.

Inputs: filter.

observe_docsA

Show OPAL query language reference and examples for writing Observe queries. Call this before writing OPAL pipelines.

Inputs: no named parameters.

observe_queryB

Run a raw OPAL pipeline query against Observe. Returns up to rowCount rows.

Inputs: pipeline (required), end_time, raw_json, row_count, +2 more.

search_entity_logsA

Search Observe logs filtered by a specific field value — useful for correlating logs to a particular entity such as a user ID, request ID, device ID, or any other identifier.

Inputs: field_name (required), field_value (required), limit, service, +2 more.

search_service_logsB

Search Observe logs for a specific service. Convenience wrapper around OPAL.

Inputs: service (required), level, limit, keyword, +2 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.6/5.0

    Scored across 7 tools

    Disambiguation4/5

    Tools have distinct purposes overall, but get_dataset_schema and inspect_dataset both deal with field discovery, potentially causing confusion. search_entity_logs and search_service_logs are similarly structured but target different scopes.

    Naming Consistency3/5

    Most tools use snake_case with verb-first naming, but observe_docs and observe_query break the pattern by using the server name prefix instead of a verb. get_dataset_schema and inspect_dataset share 'dataset' but use different verbs, causing slight inconsistency.

    Tool Count5/5

    Seven tools is well-scoped for a query-focused Observe MCP server, covering dataset discovery, schema inspection, query execution, and log searching without being overwhelming.

    Completeness4/5

    The tool surface covers core querying tasks: listing datasets, inspecting schemas, running queries, and searching logs. Missing might be dataset creation or alert management, but these are outside the apparent query-focused scope.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      Not graded
      maintenance
      A Model Context Protocol server that provides access to Observe API functionality, enabling LLMs to execute OPAL queries, manage datasets/monitors, and leverage vector search for documentation and troubleshooting runbooks.
      1
      -
    • A
      license
      B
      quality
      D
      maintenance
      A read-only MCP server for OpenObserve Community Edition that works over the REST API. Provides tools for searching logs, traces, stream schemas, and dashboards - no Enterprise license required.
      8
      73 PyPI
      16
      GPL 3.0
    • A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for interacting with the Opal Security platform, enabling operations like managing access rules, apps, and bundles via natural language.
      29 npm
      4
      Apache 2.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that enables AI assistants to query and explore your OpenObserve observability data. Provides read-only access to logs, metrics, and traces for analysis and troubleshooting.
      5
      MIT