ImmyBot MCP Server

An MCP server for the ImmyBot API (v1), the endpoint setup and software maintenance automation platform MSPs use for Windows fleets. It lets an AI agent read tenants, computers and their inventory, deployments (target assignments) and their compliance, maintenance sessions with per-item results and logs, scripts and the software catalogs and, on explicit request with confirmation, start maintenance, install software, run a deployment or run a script on a computer.

• Transport: MCP Streamable HTTP at POST /mcp, health probe at GET /health

• Stateless and multi-tenant: credentials arrive on every request as HTTP headers and are never stored; every tool is listed from the first tools/list

• Python 3.12, uv, FastMCP, httpx

• License: Apache-2.0, Copyright 2026 MSPbots.ai

MSPbots Connector

The MCP Gateway built for MSPs: visible, controlled, and your data stays where it belongs.

Get started at connect.mspbots.ai →

MSPbots Connector gives your AI clients one MCP URL to reach your entire MSP stack (RMM, PSA, documentation, security, finance), and gives you control over who can call which tool and a record of everything that was called.

Hosted service: connect.mspbots.ai · Free to use.

Why Connector

Quick start

1. Sign up at connect.mspbots.ai.

2. Connect your vendors. Pick from 150+ connectors and authorize each one on the vendor's own page, or bring your own API keys. No extra vendor accounts needed.

3. Set access. Create roles and decide which tools each role may call. Nothing is allowed until you allow it.

4. Add your MCP URL to your AI client. Copy the URL from your Connector dashboard into Claude, ChatGPT, Cursor, VS Code, Gemini, Codex, or any MCP-capable client.

5. Ask your AI to do real work, and watch every call appear in the audit log.

Features

Unified gateway

• One MCP URL for all your AI clients

• 150+ connectors across the MSP stack

• Custom MCP servers supported, free

• Authorization happens on each vendor's own page; the AI never sees passwords or tokens

• Bring your own credentials: use the vendor API keys you already have

• Multiple accounts per app; connect once, reuse across AI clients

• Tool search: finds the right action for the task

• One sign-in; vendor credentials are injected behind the scenes and OAuth tokens refresh automatically

Visibility

• Audit log for every tool call (who, which vendor, when)

• Usage dashboard: call volume, top vendors, error rate, per-user activity

• Export audit logs to CSV, or stream to Loki, Graylog, or LogScale (SIEM)

• Optional recording of tool arguments and result summaries (off by default, enabled per organization)

Control

• Per-role, per-tool allowlist, deny by default

• owner / admin / member roles

• SCIM provisioning with Entra ID, Okta, JumpCloud, and Google Workspace

Security

• Credentials encrypted one record at a time (AES-256-GCM, per-record key)

• AI clients authenticate with OAuth 2.1 + PKCE

• Vendor responses are scanned for prompt-injection patterns and returned as structured data. This is one layer of defense, not a guarantee against every attack.

• Static egress IP for customer firewall and API allowlisting

Pricing

Free.

Links: connect.mspbots.ai · mspbots.ai

Related MCP server: ConnectWise Automate MCP Server

Authentication headers

Where to get them (per ImmyBot's API documentation): register an app in Microsoft Entra ID, create a client secret (copy its value), then in ImmyBot add the app's enterprise application object id as a person ("AD External ID") and make that user an admin.

How they are used: the server requests a token from https://login.microsoftonline.com/{tenant}/oauth2/v2.0/token with the client-credentials grant and scope https://{subdomain}.immy.bot/.default, then calls https://{subdomain}.immy.bot/api/v1/... with Authorization: Bearer. Tokens are cached in memory, keyed by a SHA-256 of the full credential set, and refreshed once on a 401.

A request to /mcp without all four headers gets HTTP 401 naming the missing ones; an invalid subdomain or tenant value gets HTTP 400.

Tools

All tools return a JSON string. write marks tools that change data; confirm marks tools that change endpoints and also need confirm: true; n/a marks tools kept for compatibility that have no ImmyBot API behind them (they return an invalid_argument error naming the tool to use instead).

Errors come back as a JSON envelope instead of an exception:

{"error": {"code": "unauthorized", "message": "Microsoft Entra rejected the client credentials (HTTP 401): invalid_client: AADSTS7000215: Invalid client secret provided.", "retryable": false}}

code is one of not_configured, unauthorized, not_found, invalid_argument, rate_limited, upstream_error. Reads are retried with backoff on 429, 5xx and network errors; writes only on 429.

Run locally

uv sync
uv run python -m immybot_mcp          # listens on 0.0.0.0:8080

or with Docker:

docker build --platform linux/amd64 -t immybot-mcp:dev .
docker run --rm -p 8080:8080 immybot-mcp:dev

Configuration (environment variables, all optional): MCP_HTTP_HOST (default 0.0.0.0), MCP_HTTP_PORT (default 8080), LOG_LEVEL (default INFO). Credentials are never read from the environment.

Testing example

# list tools
curl -s http://localhost:8080/mcp \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -H "X-Immybot-Instance-Subdomain: examplemsp" \
  -H "X-Immybot-Tenant-Id: 00000000-0000-0000-0000-000000000000" \
  -H "X-Immybot-Client-Id: 00000000-0000-0000-0000-000000000000" \
  -H "X-Immybot-Client-Secret: your-client-secret" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}'

# failed maintenance sessions
curl -s http://localhost:8080/mcp \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -H "X-Immybot-Instance-Subdomain: examplemsp" \
  -H "X-Immybot-Tenant-Id: 00000000-0000-0000-0000-000000000000" \
  -H "X-Immybot-Client-Id: 00000000-0000-0000-0000-000000000000" \
  -H "X-Immybot-Client-Secret: your-client-secret" \
  -d '{"jsonrpc":"2.0","id":2,"method":"tools/call","params":{"name":"immybot_maintenance_sessions_list","arguments":{"status":"Failed","limit":10}}}'

Unit tests (no network access needed):

uv run pytest

Delivery notes

• Tool count (68). Kept as is because the tool names are an existing contract.

• Token scope fixed. ImmyBot's Entra application uses the instance URL as its App ID URI, so the token scope is https://{subdomain}.immy.bot/.default. Older versions requested api://{client_id}/.default, a token ImmyBot does not accept.

• Routes follow the ImmyBot API. Deployments are /target-assignments; sessions are listed through the /maintenance-sessions/dx grid and their items through /maintenance-actions/dx; maintenance starts through /run-immy-service; scripts run through /scripts/run; scripts and software have separate local and global catalogs (ids can collide, so databaseType / softwareType can be passed; otherwise Local is tried, then Global). Older versions called many routes that do not exist.

• No API, kept for compatibility (21 tools). ImmyBot has no task queue (all 15 immybot_tasks_*), no API to create computers (agents register them), no pause for sessions, no stored script runs (_execution_history / _execution_result; immybot_scripts_run returns the output) and no software categories or publishers. These tools return an invalid_argument error that names the tool to use.

• Compliance and stats from real data. immybot_deployments_compliance reads the latest action per computer for the deployment, immybot_tenants_compliance the tenant's non-compliant actions, immybot_software_stats the success / failure counts per version.

• Parameters the API cannot honour were removed: status on computers / deployments / scripts lists, category / publisher / status on software lists and search, autoUpdate on install. New optional parameters: search / skip on computers, databaseType / softwareType, detectionOnly on maintenance start, allowReboot on install.

• Confirmation for endpoint changes. Starting maintenance, installing software, running a deployment and running a script take confirm: true and otherwise return a "not done" result describing the action.

• Secrets stay out of results. ImmyBot returns task parameter values in clear text; parameters whose names look secret (password, secret, token, API key ...) are masked, session job arguments are left out of immybot_maintenance_sessions_get, and logs omit script bodies and parameters.

• Result size exception (SOP 2.5). immybot_deployments_list, immybot_maintenance_sessions_list, immybot_scripts_list, immybot_software_list_global, immybot_software_list, immybot_tenants_list and immybot_tenants_computers have no paging in the API, so they keep a maximum of 500; immybot_maintenance_sessions_logs keeps a maximum of 1000 log lines. All default to 50, and results are still cut to 20,000 characters with a truncation notice. immybot_computers_list pages with skip and takes at most 200 per call.

• Script runs are synchronous; the wait is capped at 95 seconds (script timeout max 90) to stay inside the gateway's tool-call limit.

License

Apache License 2.0 - see LICENSE and NOTICE.