alilxxey/openobserve-community-mcp
only MCP server for OpenObserve Community Edition via REST API. Search logs, traces, stream schemas, and dashboards without requiring the Enterprise license.
Ask AI about alilxxey/openobserve-community-mcp
Powered by Claude · Grounded in docs
I know everything about alilxxey/openobserve-community-mcp. Ask me about installation, configuration, usage, or troubleshooting.
0/500
Reviews
Documentation
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.
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
4. Add it to OpenCode
OpenCode configures MCP servers under mcp in its config file. According to the official docs,
you can add MCP servers in your global config at ~/.config/opencode/opencode.json or in a
project-level opencode.json.
See:
If you created the sample config with openobserve-mcp init-config, you can point OpenCode to it:
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"openobserve-community": {
"type": "local",
"command": ["uvx", "--from", "openobserve-community-mcp", "openobserve-mcp"],
"enabled": true,
"environment": {
"OO_CONFIG_FILE": "/absolute/path/to/config.env"
}
}
}
}
You can also inline the OpenObserve settings directly in the OpenCode MCP config:
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"openobserve-community": {
"type": "local",
"command": ["uvx", "--from", "openobserve-community-mcp", "openobserve-mcp"],
"enabled": true,
"environment": {
"OO_BASE_URL": "https://openobserve.example.com",
"OO_AUTH_MODE": "basic",
"OO_USERNAME": "your_username",
"OO_PASSWORD": "your_password"
}
}
}
}
OpenCode's MCP docs also support optional enabled, environment, and timeout fields for local
servers if you want to tune startup behavior.
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
OpenCode with inline env
If you prefer to keep everything in OpenCode config instead of a separate config.env, use:
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"openobserve-community": {
"type": "local",
"command": ["uvx", "--from", "openobserve-community-mcp", "openobserve-mcp"],
"enabled": true,
"environment": {
"OO_BASE_URL": "https://openobserve.example.com",
"OO_AUTH_MODE": "basic",
"OO_USERNAME": "your_username",
"OO_PASSWORD": "your_password"
}
}
}
}
Official OpenCode references:
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.
