官方说明10 个来源MCP 服务8 天前
alilxxey/openobserve-community-mcp
在 GitHub 查看 ↗直链 · 无中转页
配置模板（请按你的客户端调整）
claude mcp add openobserve-community-mcp -- npx -y openobserve-community-mcp
这是根据仓库名生成的可粘贴骨架，命令行参数与包名请以该项目 README 为准。
- ★ 数取值
- 16 ★ · alilxxey/openobserve-community-mcp · 取自 GitHub 搜索 API · （2026-10-16 20:00:20 核对）
- 来源明细
- 收录自 punkpeye/awesome-mcp-servers 榜单（我们从中收集的条目之一） · 条目类型：MCP 服务
- 收录与活跃
- 收录于 2026-10-09 · 最近见到 2026-10-16 · 共见到 32 次 · 被 10 个来源列出
- 评分构成
- 综合分 1,003 · 16 ★ · 10 个来源 · mcp
常见问题（答案都来自我们的记录）
怎么安装？
我们【没有】从该仓库取到安装命令（我们的 install 覆盖率只有约 4%）。请看它的 README 或 releases 页。
它适合谁 / 用来做什么？
我们把它归在这些标签下: MCP 服务。标签来自条目自身，不是我们强加的分类。
谁维护它、还在更新吗？
仓库
alilxxey/openobserve-community-mcp；我们收录于 2026-10-09；最近见到 2026-10-16。这里没有"官方认证"或"质量评级"——我们只记录来源与时间。第三方质量标记
OpenObserve MCP
以下摘录自该仓库的 README（片段） · 在 GitHub 读完整 README →
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:
- stdio only
- Community Edition only
- read-only only
- regular OpenObserve REST API only
- no native /mcp endpoint
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
This creates a sample config at:
Edit it:
Example:
2. Add it to Claude
3. Add it to Codex
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:
- OpenCode MCP servers docs
- OpenCode config docs
If you created the sample config with openobserve-mcp init-config, you can point OpenCode to it:
You can also inline the OpenObserve settings directly in the OpenCode MCP config:
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:
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:
Supported settings:
- OO_BASE_URL
- OO_ORG_ID optional
- OO_AUTH_MODE
- OO_USERNAME and OO_PASSWORD for basic auth
- OO_TOKEN for bearer auth
- OO_TIMEOUT_SECONDS
- OO_VERIFY_SSL
- OO_CONFIG_FILE optional explicit path to a config file
Config precedence:
1. explicit OO_CONFIG_FILE
2. ~/.config/openobserve-mcp/config.env
3. legacy .env.local in the current directory
4. process environment overrides file values
You can also pass config directly via MCP client env settings.
Claude with inline env
Codex with inline env
OpenCode with inline env
If you prefer to keep everything in OpenCode config instead of a separate config.env, use:
Official OpenCode references:
- Config locations and precedence
- Local MCP server configuration
Tools
- list_streams
This package is designed for local MCP clients such as Claude and Codex.
What it is:
- stdio only
- Community Edition only
- read-only only
- regular OpenObserve REST API only
- no native /mcp endpoint
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
This creates a sample config at:
Edit it:
Example:
2. Add it to Claude
3. Add it to Codex
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:
- OpenCode MCP servers docs
- OpenCode config docs
If you created the sample config with openobserve-mcp init-config, you can point OpenCode to it:
You can also inline the OpenObserve settings directly in the OpenCode MCP config:
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:
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:
Supported settings:
- OO_BASE_URL
- OO_ORG_ID optional
- OO_AUTH_MODE
- OO_USERNAME and OO_PASSWORD for basic auth
- OO_TOKEN for bearer auth
- OO_TIMEOUT_SECONDS
- OO_VERIFY_SSL
- OO_CONFIG_FILE optional explicit path to a config file
Config precedence:
1. explicit OO_CONFIG_FILE
2. ~/.config/openobserve-mcp/config.env
3. legacy .env.local in the current directory
4. process environment overrides file values
You can also pass config directly via MCP client env settings.
Claude with inline env
Codex with inline env
OpenCode with inline env
If you prefer to keep everything in OpenCode config instead of a separate config.env, use:
Official OpenCode references:
- Config locations and precedence
- Local MCP server configuration
Tools
- list_streams
- 来源
- awesome · https://github.com/alilxxey/openobserve-community-mcp
- 按领域浏览
- MCP 服务
- Traction
- 16 ★
- 收录于
- 昨天
更多MCP 服务
所属领域与标签
每个标签都能点进去看同类的全部条目。数字是当前库里的真实条数。