ImmyBot MCP

ImmyBot + AI - for Claude, the ChatGPT desktop app, GitHub Copilot, Gemini CLI, and any agent that speaks MCP

Unofficial. Community-built Claude Code Skill and MCP server for the ImmyBot

API. Not affiliated with, endorsed by, or sponsored by ImmyBot, LLC..

Full skill page - install, outcomes, safety model.

Every ImmyBot endpoint typed, plus a local SQLite mirror that answers the cross-tenant questions the web UI cannot. Works with the AI you already use - ChatGPT (desktop app), Claude Desktop, Codex, Claude Code, Claude Cowork, and GitHub Copilot - plus Gemini CLI. Free, open source, runs on your laptop. Built for MSP owners. No code required.

Works with your agent

The six agents MSP owners actually use (self-serve, works today):

The ChatGPT desktop app runs immybot-mcp locally and shares MCP configuration with Codex (OpenAI). ChatGPT on the web needs a remote server, which msp-skills does not support yet. If your team works there, a hosted gateway is the better pick; check that your AI app is on the gateway's setup list.

Also for the Microsoft and Google stacks

Big install base, but an honest heads-up: Gemini CLI runs the local binary you just installed, while Microsoft 365 Copilot and the Gemini app need a remote server, which msp-skills does not support yet.

Skill-native agents (also covered): Hermes and OpenClaw read this skill's SKILL.md directly *and* speak MCP - see their install sections below. Also works with Cursor, Windsurf, Cline, Continue.dev, and Zed via MCP. Full per-tool wire-up: [docs/which-agent.md](../../docs/which-agent.md).

Run more than one agent? Install across all 51+ supported agents in one command: npx skills add Servosity/msp-skills@latest (requires Node.js, then run the per-skill installer for the CLI/MCP binaries). See docs/which-agent.md.

Install in 60 seconds

Fastest for Claude Desktop - one-click .mcpb

Claude Desktop bundle: the .mcpb launches on macOS (Intel and Apple Silicon), Windows x64 and Linux x64. Every tool shells out to the companion immybot-cli. Releases cut from 2026-09-18 on ship that CLI inside the bundle; older bundles contain only the MCP server, so if yours lacks the companion, run the Path A or Path B installer below first (or set IMMYBOT_CLI_PATH to an existing binary). Details: #331.

Download ImmyBot MCP (.mcpb) - then open Claude Desktop > Settings > Extensions and select the file. One click, no JSON, no shell. (Browse every ImmyBot release on the releases page.)

Prefer the Claude Code plugin? Add the marketplace once, then install - works immediately, no directory listing required:

/plugin marketplace add Servosity/msp-skills

/plugin install immybot@msp-skills

Path A - paste one prompt into your AI agent (recommended)

Copy this into Claude Code, Codex CLI, or Claude Cowork:

Install the ImmyBot Skill and MCP server from Servosity/msp-skills in this agent workspace. If this workspace uses a POSIX shell (macOS, Linux, WSL, or Bash), run bash <(curl -fsSL https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/immybot/install.sh). If it uses Windows PowerShell, run iwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/immybot/install.ps1 | iex. Then authenticate per the README and run immybot-cli --help to explore.

The same prompt works in any agent that can run shell.

Path B - run the installer yourself

Windows (PowerShell):

iwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/immybot/install.ps1 | iex

macOS / Linux:

bash <(curl -fsSL https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/immybot/install.sh)

The installer drops both immybot-cli (the CLI) and immybot-mcp (the MCP server) into your user bin path. Claude Code, Codex, and Cowork discover the Skill via SKILL.md in this directory.

Verify:

immybot-cli --version

Upgrade to the latest version

The installer always fetches the current release - re-run it to upgrade:

macOS / Linux:

bash <(curl -fsSL https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/immybot/install.sh)

Windows (PowerShell):

iwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/immybot/install.ps1 | iex

Claude Desktop .mcpb users: download the latest .mcpb (top of this section) and re-select it in Settings > Extensions. Claude Code plugin users: /plugin update immybot@msp-skills.

Add to Claude Desktop, the ChatGPT desktop app, GitHub Copilot, Gemini CLI, or another MCP client

After the installer runs, see [mcp-install.md](./mcp-install.md) and [docs/which-agent.md](../../docs/which-agent.md) for the per-agent wire-up - one section per agent, including the GitHub Copilot servers key and the ChatGPT desktop app. Claude Desktop's Settings > Extensions panel is the simplest path; the MCP config block (for users who prefer editing JSON) is documented in mcp-install.md.

Install for Hermes

From the Hermes CLI:

hermes skills install servosity/msp-skills/skills/immybot --force

Inside a Hermes chat session:

/skills install servosity/msp-skills/skills/immybot --force

Hermes speaks MCP natively, so it can also use the immybot-mcp server directly - same install path, same env vars.

Install for OpenClaw

Tell your OpenClaw agent (copy this):

Install the immybot skill from https://github.com/servosity/msp-skills/tree/main/skills/immybot. The skill defines how its required CLI (immybot-cli) can be installed via the openclaw: frontmatter block.

OpenClaw isn't generally available yet; the frontmatter wiring is pre-shipped and will activate the moment OpenClaw launches.

Authenticate

Set the credentials the CLI needs (from your ImmyBot portal):

export IMMYBOT_SUBDOMAIN=acme          # the "acme" in acme.immy.bot

export IMMYBOT_TENANT_ID= export IMMYBOT_CLIENT_ID= export IMMYBOT_CLIENT_SECRET= immybot-cli doctor

ImmyBot issues no API key of its own. You register an app in Microsoft Entra ID, create a client secret, then add that Enterprise Application's object ID as an admin person inside ImmyBot (Show More > People > New > AD External ID). IMMYBOT_SUBDOMAIN is required: it derives the OAuth scope, and without it the token request falls back to a scope naming your own app registration and Entra rejects it.

doctor checks config, paths, and API reachability, then verifies the credential itself with one authenticated read against /auth/me: it reports valid, invalid (HTTP 401), or scope-limited (HTTP 403). It exits 0 even when the credential is rejected, so scripts should add --fail-on error.

What this skill does

Full command reference: guide.md. For the AI-agent operating contract (--agent, --dry-run, when to confirm before mutating), see AGENTS.md.

What makes this different

Most ImmyBot integrations and MCP servers proxy each question into a live API call. That's fine for one record. It dies at scale, when you're asking which of your 40 clients are still running a Chrome build below 140, because that is one API call per tenant per title and ImmyBot keeps no history to compare against.

This skill syncs ImmyBot into a local SQLite mirror with full-text search. Aggregate questions become one local SQL join: instant, offline, and the AI sees the answer, not the raw data. Compound commands like session-triage, version-spread and assignment-explain join across maintenance sessions, actions, computers, tenants, software inventory and target assignments - work a stateless API wrapper can't do.

The pain this closes

ImmyBot's own community threads and the r/msp deployment discussions circle the same shape: the platform is excellent at putting software on machines and unhelpful the morning after. A maintenance window runs across hundreds of endpoints, a slice of it fails, and the console shows you the same error text once per machine with no grouping, no root cause, and no way to ask "is this one broken package or forty broken agents?". The neighbouring questions are worse, because they are cross-tenant: which clients are still below a version floor, why one machine did not match a deployment when its neighbour did, and what changed overnight. ImmyBot keeps no history to diff against, so the honest answer today is a spreadsheet.

• `session-triage --since 24h` - collapses a night of failed actions into distinct root causes, so you read the failure once instead of forty times.
• `version-spread "Google Chrome" --min-version 140` -