
ImmyBot
io.github.WYRE-AI由 GitHub 账号 WYRE-AI 发布v2.0.0更新于 Nov 21, 2026
MCP server for ImmyBot — Windows software deployment, maintenance, tenants, deployments.
概览
把助手接入 ImmyBot,用于 Windows 终端管理:列出计算机、暂存软件安装、运行维护会话并查看任务。
- 可以做什么
- 列出、搜索、查看和创建计算机,查看硬件软件清单与部署记录,并强制代理签入
- 浏览、搜索和查看软件包、版本、分类与发布者,并暂存安装
- 启动并查询维护会话,把期望状态同步到设备
- 管理租户、PowerShell 脚本和后台任务
- 查看服务器状态与工具分组
- 适用场景
- 适合在 ImmyBot 中管理 Windows 终端的 MSP 或 IT 管理员,希望助手在不打开网页控制台的情况下查询设备、规划软件推送,或触发并跟踪维护会话。
- 运行要求
- 以本地进程(npm 包或容器镜像)通过 stdio 运行,或作为 HTTP 服务供网关托管。直连模式需要来自 Microsoft Entra ID 应用注册的 IMMYBOT_INSTANCE_SUBDOMAIN、IMMYBOT_TENANT_ID、IMMYBOT_CLIENT_ID 和 IMMYBOT_CLIENT_SECRET,且该应用需具备 ImmyBot API 权限。HTTP 模式还需 CONDUIT_S2S_SECRET 与 X-Gateway-S2S 签名;网关模式要求每次请求携带四个 X-ImmyBot-* 请求头。
安装
在 SourceWeft 中
- 打开 控制台中的 ImmyBot,将其添加到工作区。
- 为需要使用其工具的对话启用该服务。
Desktop only,通过 STDIO。 STDIO 服务会启动本地进程,因此需要 SourceWeft 桌面宿主。
其他 MCP 客户端
参照 仓库 中的启动说明。
README
@wyre-ai/immybot-mcp
MCP server for ImmyBot - Windows endpoint management and software deployment automation.
Features
- 🔐 OAuth 2.0 Authentication - Microsoft Entra ID client credentials
- 🏢 Multi-tenant Support - Per-instance subdomain configuration
- 🧭 Flat Tool List - Every tool is listed and callable immediately
- 💻 Comprehensive Coverage - Computers, software, deployments, scripts, tenants, maintenance sessions, tasks
- ⚡ Gateway Ready - Stateless per-request operation for WYRE MCP Gateway
- 🚀 Docker Deployment - Container-ready with health checks
- 📊 Structured Logging - Detailed operation tracking
Quick Start
Docker (Recommended)
The image listens on 0.0.0.0 inside the container and defaults to AUTH_MODE=gateway. Publish the port on loopback and pass a real CONDUIT_S2S_SECRET. In gateway mode, ImmyBot credentials arrive on each request as headers; they are not read from the environment.
Compose refuses to start when CONDUIT_S2S_SECRET is unset. The gateway service does not set IMMYBOT_* variables or env_file, so a project .env cannot inject static vendor credentials. It publishes 127.0.0.1:8080:8080:
Direct Installation
Tools
Every tool is listed by tools/list and callable immediately. There is no
domain to enter first. The domains below are documentation groupings only.
Upgrading from 1.x?
immybot_navigateandimmybot_backare gone. Call the domain tools directly, for exampleimmybot_computers_list.immybot_statusstill works and now lists the tool groups.
Available Domains
- computers - Device and endpoint management
- software - Application and package management
- deployments - Software deployment configuration
- scripts - PowerShell script execution and management
- tenants - Client organization management
- maintenance_sessions - Device maintenance and state reconciliation
- tasks - Background operation monitoring
Authentication
ImmyBot uses OAuth 2.0 with Microsoft Entra ID:
Required Configuration
Setup Steps
- Register Enterprise Application in Microsoft Entra ID
- Grant ImmyBot API permissions to the application
- Create client secret for the application
- Configure application in ImmyBot settings
OAuth scope: api://{client_id}/.default
Usage Examples
1. Computers
2. Software Management
3. Maintenance Sessions
Two-Step Deployment Model
⚠️ Important: ImmyBot uses a two-step deployment workflow:
- Configure desired state - Software installations create deployments
- Reconcile via maintenance session - Sessions apply the desired state
Environment Variables
Copy .env.example and set the variables below.
Gateway Mode (Docker)
/health stays unauthenticated and does not read credentials. The stdio transport does not use CONDUIT_S2S_SECRET.
Direct Mode (CLI)
HTTP authentication
With MCP_TRANSPORT=http and CONDUIT_S2S_SECRET set, every /mcp request must include X-Gateway-S2S. The check is verifyS2sHeader in src/s2s-verify.ts: the header value is t=<unix seconds>,v1=<hex>, where the hex is HMAC-SHA256 of the literal string t=<unix seconds> keyed with CONDUIT_S2S_SECRET (64 lowercase hex characters). The timestamp must be within 300 seconds of the server clock. A missing or invalid header is HTTP 401, before vendor credentials are read.
In AUTH_MODE=gateway, those four X-ImmyBot-* headers are required. A request missing any of them gets HTTP 401 and does not fall back to IMMYBOT_* in the process environment. Direct mode (AUTH_MODE unset) still requires a valid X-Gateway-S2S header, then uses the IMMYBOT_* environment variables. Direct mode does not read the X-ImmyBot-* headers.
Local HTTP without a secret is development-only. It binds 127.0.0.1 and logs a warning. A non-loopback MCP_HTTP_HOST (including the image default 0.0.0.0) makes startup exit. Do not publish that port off loopback.
Tools Reference
Status Tool
Computers Tools
Software Tools
Error Handling
The server provides structured error responses:
Common error types:
- Authentication errors - Invalid credentials or expired tokens
- Not found errors - Resource doesn't exist
- Validation errors - Missing or invalid parameters
- Rate limit errors - Too many requests
- Server errors - Internal ImmyBot API issues
Development
Build from Source
Testing
Docker Build
The checked-in Compose file is gateway mode. It requires CONDUIT_S2S_SECRET and does not pass static IMMYBOT_* credentials.
Support
License
Apache-2.0 - see LICENSE for details.
来源:README.md,提交 dc8d0f0
工具
0版本历史
3- v2.0.0最新Nov 20, 2026
- v1.2.14Oct 14, 2026
- v1.2.13Sep 16, 2026
评分
已满足适用检查项的 40%
该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。
- 近 30 天内可连通25 分
请保持端点能够响应 MCP 握手;SourceWeft 每 30 天探测一次。
- 已声明认证方式10 分
请在注册中心条目中声明凭据请求头,或保持端点能够响应探测,以便判定其认证方式。
- 已列出工具15 分
请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。
- 描述必需15 分
- 图标10 分
- 文档15 分
- 许可证10 分
请在仓库或注册中心条目中声明许可证。