observe-mcp
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@observe-mcp search logs for service 'api-gateway' with status 500"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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 |
| Run a raw OPAL pipeline query against any dataset |
| Discover available datasets in your Observe tenant |
| Live-sample a dataset to see available fields |
| Return cached field schema (instant, no API call) |
| Search logs for a named service |
| Search logs by any field/value pair (userId, requestId, deviceId, etc.) |
| OPAL language reference and query examples |
Related MCP server: openobserve-community-mcp
Configuration
Variable | Required | Description |
| Yes | Your Observe tenant ID (numeric). Found in your Observe URL: |
| Yes | Observe bearer token. Generate at: Observe UI → Settings → API Tokens |
| No | Default dataset path used when |
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-mcpUsage 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 toolsget_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
Scored across 7 tools
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.
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.
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.
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
Related MCP Connectors
An MCP server that provides tools to discover and retrieve podcast episodes transcripts.
MCP observability: analyse MCP server usage, investigate sessions, and instrument MCP servers.
MCP server for querying and analyzing data from ad platforms, analytics tools, and spreadsheets
An MCP server giving access to Grafana dashboards, data and more.
Related MCP Servers
- AlicenseNot gradedqualityNot gradedmaintenanceA 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-
- AlicenseBqualityDmaintenanceA 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.873 PyPI16GPL 3.0

opal-mcpofficial
AlicenseNot gradedqualityDmaintenanceMCP server for interacting with the Opal Security platform, enabling operations like managing access rules, apps, and bundles via natural language.29 npm4Apache 2.0- AlicenseNot gradedqualityCmaintenanceAn 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.5MIT