openobserve-community-mcp
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.
README
OpenObserve MCP
stdio MCP server for OpenObserve Community Edition, using only the regular REST API.
This package is designed for local MCP clients such as Claude and Codex.
<!-- mcp-name: io.github.alilxxey/openobserve-community-mcp -->
What it is:
stdioonly- Community Edition only
- read-only only
- regular OpenObserve REST API only
- no native
/mcpendpoint
The server can boot without an active OpenObserve configuration so hosted MCP platforms can start it,
but every tool call still requires a reachable external OpenObserve instance configured via OO_BASE_URL
and credentials.
Quick Start
1. Create a config file
uvx --from openobserve-community-mcp openobserve-mcp init-config
This creates a sample config at:
~/.config/openobserve-mcp/config.env
Edit it:
vim ~/.config/openobserve-mcp/config.env
Example:
OO_BASE_URL=https://openobserve.example.com
# Optional if the credentials have access to exactly one organization.
# OO_ORG_ID=default
OO_AUTH_MODE=basic
OO_USERNAME=your_username
OO_PASSWORD=your_password
OO_TIMEOUT_SECONDS=20
OO_VERIFY_SSL=true
2. Add it to Claude
claude mcp add -s user openobserve-community -- uvx --from openobserve-community-mcp openobserve-mcp
3. Add it to Codex
codex mcp add openobserve-community -- uvx --from openobserve-community-mcp openobserve-mcp
Docker / Glama
This repository also publishes a container image for Docker-based MCP clients and Glama deployments:
docker run --rm -i \
-e OO_BASE_URL \
-e OO_ORG_ID \
-e OO_AUTH_MODE \
-e OO_USERNAME \
-e OO_PASSWORD \
-e OO_TOKEN \
-e OO_TIMEOUT_SECONDS \
-e OO_VERIFY_SSL \
ghcr.io/alilxxey/openobserve-community-mcp:latest
OO_ORG_ID is optional when the credentials only have access to one organization.
Use OO_USERNAME and OO_PASSWORD for basic auth, or OO_TOKEN for bearer auth.
The container can start without these values for hosted MCP platforms, but tool calls will fail until
you configure a real external OpenObserve instance.
Configuration
Default config path:
~/.config/openobserve-mcp/config.env
Supported settings:
OO_BASE_URLOO_ORG_IDoptionalOO_AUTH_MODEOO_USERNAMEandOO_PASSWORDfor basic authOO_TOKENfor bearer authOO_TIMEOUT_SECONDSOO_VERIFY_SSLOO_CONFIG_FILEoptional explicit path to a config file
Config precedence:
- explicit
OO_CONFIG_FILE ~/.config/openobserve-mcp/config.env- legacy
.env.localin the current directory - process environment overrides file values
You can also pass config directly via MCP client env settings.
Claude with inline env
claude mcp add -s user openobserve-community \
-e OO_BASE_URL=https://openobserve.example.com \
-e OO_AUTH_MODE=basic \
-e OO_USERNAME=your_username \
-e OO_PASSWORD=your_password \
-- uvx --from openobserve-community-mcp openobserve-mcp
Codex with inline env
codex mcp add openobserve-community \
--env OO_BASE_URL=https://openobserve.example.com \
--env OO_AUTH_MODE=basic \
--env OO_USERNAME=your_username \
--env OO_PASSWORD=your_password \
-- uvx --from openobserve-community-mcp openobserve-mcp
Tools
list_streamsget_stream_schemasearch_logssearch_aroundsearch_valueslist_dashboardsget_dashboardget_latest_traces
Optional Local Install
If you prefer a persistent local binary instead of uvx:
uv tool install openobserve-community-mcp
This installs the openobserve-mcp command into your user-level uv tools directory.
Add To Claude With Global Install
claude mcp add -s user openobserve-community -- openobserve-mcp
Add To Codex With Global Install
codex mcp add openobserve-community -- openobserve-mcp
You can also run the server directly:
openobserve-mcp
This mode may require ~/.local/bin to be present in your PATH.
If openobserve-mcp is not found, either:
- add
~/.local/binto yourPATH; or - use the recommended
uvx --from openobserve-community-mcp openobserve-mcplaunch mode instead.
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.