LinuxServer.io MCP Registry
Enables searching LinuxServer.io images, auditing Docker Compose and run commands against documentation-derived conventions, and searching open/closed image requests to prepare drafts without submission.
README
LinuxServer.io MCP Registry
Community MCP server and registry UI for LinuxServer.io image discovery, documentation-derived container audits, open and closed image request search, and image request preparation.
Provided by Blackout Secure and sponsored by Blackout Secure for the LinuxServer.io community.
Audit results are derived from public LinuxServer.io documentation and are intended as community guidance. They are not an official LinuxServer.io certification, support decision, or approval decision.
What this project does
This project helps users and AI assistants:
- Search LinuxServer.io images and inspect normalized metadata.
- Audit Docker Compose and
docker runtext against documented LinuxServer.io-style conventions. - Search open and closed LinuxServer.io Image Requests before creating duplicates.
- Prepare image request drafts without submitting them.
- Surface known issues, status, support, documentation, and donation links.
- Publish an MCP server through the GitHub MCP Registry ecosystem.
Features
The monorepo contains a TypeScript MCP stdio package, a Hono Cloudflare Worker with Streamable HTTP and REST routes, and a React Cloudflare Pages registry UI. All external lookups are best effort and retain source links. GitHub access is read-only.
MCP tools
| Tool | Purpose |
|---|---|
lsio.search_images |
Search current image metadata. |
lsio.get_image |
Fetch one normalized image record. |
lsio.audit_image |
Audit an image and optional Compose or run text. |
lsio.audit_compose |
Parse Compose YAML and audit LinuxServer.io services. |
lsio.list_categories |
List categories, counts, and examples. |
lsio.get_known_issues |
Return known-issue and service-status context. |
lsio.search_image_requests |
Search open, closed, or all Image Requests. |
lsio.pending_image_requests |
Search open Image Requests. |
lsio.closed_image_requests |
Search closed Image Requests. |
lsio.recommended_new_images |
Compare inventory and request history for possible gaps. |
lsio.prepare_image_request |
Prepare a Markdown draft without posting it. |
lsio.image_pipeline |
Run the complete inventory/request/issue decision workflow. |
lsio.get_support_links |
Return useful LinuxServer.io community links. |
How image request search works
The server searches GitHub's public Image Requests category. When GITHUB_TOKEN is available it uses the backing repository's read-only GraphQL discussion connection for richer metadata. Without a token it parses the public open and closed category pages and returns a clear best-effort notice. A token is never required for basic image, request-search, or audit functionality.
Search is read-only. The project never comments, reacts, submits, or plus-ones a discussion.
Why closed requests are searched
Closed discussions can document a duplicate, rejection, accepted request, superseded proposal, or an image that was added later. The pipeline checks both open and closed requests before describing a new request as potentially reasonable.
How audits work
Compose YAML is parsed with a safe YAML parser and docker run commands are inspected as plain text. Neither is executed. Results describe whether input passes this project's checks; they never claim a container is secure or officially approved.
Audit rubric
Checks cover image existence, /config persistence, host-to-container volume direction, PUID/PGID, TZ, Compose restart policy, port exposure, privileged mode, Docker socket and broad host mounts, host networking, possible inline secrets, ambiguous tags, Docker Mods, custom init/services, branding review, update guidance, and support readiness.
Data sources
- LinuxServer.io
- API documentation
- Image catalog
- Images by category
- Image Requests
- Known issues
- Status dashboard
- Support
- Donate
Local development
Requirements: Node.js 22 or later and npm.
npm ci
npm run build
npm test
npm run dev
Run the Worker separately with npm run dev --workspace=@blackoutsecure/linuxserver-mcp-worker. The web dev server proxies /api to Worker port 8787. VS Code can launch the stdio MCP package using .vscode/mcp.json.
Cloudflare deployment
- Replace the placeholder KV IDs in wrangler.toml.
- Store any optional
GITHUB_TOKENwithwrangler secret put GITHUB_TOKEN. - Deploy the Worker with
npx wrangler deploy. - Build
apps/weband deployapps/web/distto Cloudflare Pages withVITE_API_BASE_URLset to the Worker origin.
MCP Registry publishing
server.json contains the MCP namespace, npm package, repository, and remote transport metadata. Validate the npm package and remote endpoint before enabling the publish workflow placeholder.
GitHub Copilot organization registry support
The Worker implements:
GET /v0.1/serversGET /v0.1/servers/{serverName}/versions/latestGET /v0.1/servers/{serverName}/versions/{version}
These endpoints allow GET and OPTIONS cross-origin requests with Authorization and Content-Type headers.
Environment variables
| Variable | Default | Use |
|---|---|---|
LSIO_API_BASE_URL |
https://api.linuxserver.io |
Image metadata API origin. |
GITHUB_TOKEN |
unset | Optional richer read-only discussion search. |
CACHE_TTL_SECONDS |
3600 |
External lookup cache lifetime. |
LOG_LEVEL |
info |
Runtime logging threshold. |
Tokens are never stored or printed and are not used for discussion mutations.
Security model
All tool inputs are validated with Zod. User-provided Compose, Docker, and shell-like text is never executed. Public write-like endpoints are rate limited. Secrets are neither persisted nor logged. Drafts are shown to the caller only and are never submitted automatically. See SECURITY.md.
Rate limiting and caching
Audit, pipeline, draft, and MCP POST routes use per-client in-memory rate limiting. External image, request, issue, and status responses are cached in-process and in the configured Cloudflare KV namespace. Multi-isolate production deployments should move rate-limit counters to a durable Cloudflare service.
Contributing
Read CONTRIBUTING.md, follow CODE_OF_CONDUCT.md, and include focused tests for behavior changes.
Support boundaries
Use this repository's issue tracker for project bugs. Use LinuxServer.io's own documentation and support channels for container support. Blackout Secure does not speak for LinuxServer.io, and this project cannot approve or reject image requests.
License
MIT. See LICENSE.
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
mcp-server-qdrant
这个仓库展示了如何为向量搜索引擎 Qdrant 创建一个 MCP (Managed Control Plane) 服务器的示例。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器