immybot-mcp
An MCP server for ImmyBot IT automation platform, enabling management of computers, deployments, software, and maintenance sessions through ImmyBot's API.
README
@wyre-technology/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
- š§ Decision Tree Navigation - Organized tool discovery by domain
- š» 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)
docker run -d \
--name immybot-mcp \
-p 8080:8080 \
-e AUTH_MODE=gateway \
-e MCP_HTTP_PORT=8080 \
-e LOG_LEVEL=info \
ghcr.io/wyre-technology/immybot-mcp:latest
Direct Installation
npm install @wyre-technology/immybot-mcp
npx @wyre-technology/immybot-mcp
Navigation
The server uses decision-tree navigation to organize tools by domain:
- Start ā
immybot_navigateā Choose domain - Domain tools ā Domain-specific operations
- Return ā
immybot_backā Main navigation
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
| Field | Description | Example |
|---|---|---|
instanceSubdomain |
ImmyBot instance subdomain | acmemsp |
tenantId |
Microsoft Entra tenant ID | 12345678-1234-1234-1234-123456789abc |
clientId |
Application (client) ID | 87654321-4321-4321-4321-cba987654321 |
clientSecret |
Client secret value | your-client-secret |
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. Navigate to Computers Domain
// Start navigation
await callTool('immybot_navigate', { domain: 'computers' });
// List computers
await callTool('immybot_computers_list', {
tenantId: 1,
isOnline: true
});
// Get computer details
await callTool('immybot_computers_get', { computerId: 123 });
2. Software Management
// Navigate to software domain
await callTool('immybot_navigate', { domain: 'software' });
// Search for software
await callTool('immybot_software_search', { query: 'Chrome' });
// Install software (stages for maintenance session)
await callTool('immybot_software_install', {
softwareId: 456,
computerIds: [123, 124, 125],
autoUpdate: true
});
3. Maintenance Sessions
// Navigate to maintenance sessions
await callTool('immybot_navigate', { domain: 'maintenance_sessions' });
// Start maintenance session (reconciles deployments)
await callTool('immybot_maintenance_sessions_start', {
computerId: 123,
sessionType: 'Manual'
});
// Check session status
await callTool('immybot_maintenance_sessions_get', { sessionId: 789 });
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
// Step 1: Stage software installation
await callTool('immybot_software_install', {
softwareId: 123,
computerIds: [456]
});
// ā This creates a deployment, does NOT install immediately
// Step 2: Reconcile state
await callTool('immybot_maintenance_sessions_start', {
computerId: 456
});
// ā This runs the maintenance session to actually install software
Environment Variables
Gateway Mode (Docker)
| Variable | Default | Description |
|---|---|---|
AUTH_MODE |
direct |
Set to gateway for WYRE MCP Gateway |
MCP_TRANSPORT |
stdio |
Transport mode (http or stdio) |
MCP_HTTP_PORT |
8080 |
HTTP server port |
LOG_LEVEL |
info |
Logging level (debug, info, warn, error) |
Direct Mode (CLI)
| Variable | Required | Description |
|---|---|---|
IMMYBOT_INSTANCE_SUBDOMAIN |
ā | ImmyBot instance subdomain |
IMMYBOT_TENANT_ID |
ā | Microsoft Entra tenant ID |
IMMYBOT_CLIENT_ID |
ā | Application client ID |
IMMYBOT_CLIENT_SECRET |
ā | Client secret |
Tools Reference
Navigation Tools
| Tool | Description |
|---|---|
immybot_navigate |
Navigate to domain |
immybot_status |
Show current state |
immybot_back |
Return to main menu |
Computers Tools
| Tool | Description |
|---|---|
immybot_computers_list |
List computers with filtering |
immybot_computers_get |
Get computer details |
immybot_computers_search |
Search computers by name |
immybot_computers_inventory |
Get hardware/software inventory |
immybot_computers_create |
Create computer record |
immybot_computers_deployments |
List computer deployments |
immybot_computers_trigger_checkin |
Force agent check-in |
Software Tools
| Tool | Description |
|---|---|
immybot_software_list_global |
List global software packages |
immybot_software_list |
List all software (global + tenant) |
immybot_software_get |
Get software details |
immybot_software_search |
Search software by name |
immybot_software_versions |
List software versions |
immybot_software_latest_version |
Get latest version |
immybot_software_categories |
List categories |
immybot_software_publishers |
List publishers |
immybot_software_install |
Stage software installation |
immybot_software_stats |
Get installation statistics |
Error Handling
The server provides structured error responses:
{
"content": [{"type": "text", "text": "Error: Authentication failed"}],
"isError": true
}
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
git clone https://github.com/wyre-technology/immybot-mcp.git
cd immybot-mcp
npm install
npm run build
npm start
Testing
npm test
Docker Build
docker build -t immybot-mcp --build-arg NODE_AUTH_TOKEN=$GITHUB_TOKEN .
Support
License
Apache-2.0 - see LICENSE for details.
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.