Blumira MCP

Blumira + 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 Blumira

API. Not affiliated with, endorsed by, or sponsored by Blumira, Inc..

▶ Watch the 30-second demo - demo data is simulated; every command shown exists in the real CLI.

Every Blumira finding, detection, and agent across your direct org and every MSP sub-account - in one offline-searchable store with cross-account triage and over-time trends no single API call can answer. 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

Security note (until this connector is reprinted). Do not put this

connector behind the supergateway bridge or any other stdio-to-HTTP bridge,

not even on localhost. The bridge adds no password, so anyone who can reach

its port can use the MCP tools with your credentials. Use the default stdio

transport. If you set up a bridge or a tunnel for a remote agent, shut it

down. A fix is on the way.

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

The ChatGPT desktop app runs blumira-mcp locally and shares MCP configuration with Codex (OpenAI). ChatGPT on the web needs a remote (HTTP) server. This connector speaks stdio only, and the bridge it would need is paused until it is reprinted (see the security note in mcp-install.md), so msp-skills does not support it 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 blumira-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 BLUMIRA_CLI_PATH to an existing binary). Details: #331.

Download Blumira MCP (.mcpb) - then open Claude Desktop > Settings > Extensions and select the file. One click, no JSON, no shell. (Browse every Blumira 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 blumira@msp-skills

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

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

Install the Blumira 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/blumira/install.sh). If it uses Windows PowerShell, run iwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/blumira/install.ps1 | iex. Then authenticate per the README and run blumira-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/blumira/install.ps1 | iex

macOS / Linux:

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

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

Verify:

blumira-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/blumira/install.sh)

Windows (PowerShell):

iwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/blumira/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 blumira@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/blumira --force

Inside a Hermes chat session:

/skills install servosity/msp-skills/skills/blumira --force

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

Install for OpenClaw

Tell your OpenClaw agent (copy this):

Install the blumira skill from https://github.com/servosity/msp-skills/tree/main/skills/blumira. The skill defines how its required CLI (blumira-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 Blumira portal):

BLUMIRA_API_TOKEN=<value> BLUMIRA_CLIENT_ID=<value> BLUMIRA_CLIENT_SECRET=<value> blumira-cli doctor

doctor confirms the credentials work before you run anything that touches data. 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 Blumira 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 "how many open critical findings sit across all 30 client accounts right now, and which three accounts own most of them."

This skill syncs Blumira 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 triage, coverage, and velocity join findings against detection rules and agent check-ins across every account at once - work a stateless API wrapper can't do.

The pain this closes

Blumira is sold as detection-and-response that doesn't need a full SOC, and r/msp threads weighing it against the other MDR/SIEM options keep landing on the same operational catch: the product is easy to deploy, but the day-two work is triage, and the partner portal makes you do that triage one account at a time. Switch the active organization, sort the open findings, note the worst, switch again. Across a book of clients there's no single screen that joins findings, detection coverage, and agent health, so "which accounts are behind on coverage" or "which domain controllers went dark this week" becomes a manual sweep you hold in your head.

This skill closes that with cross-account reads off a local mirror:

• `blumira-cli triage --status open` - one globally-ranked open-findings queue across every client account.
• `blumira-cli coverage --against basis` - detection rules missing or disabled versus your basis ruleset, per account.
• `blumira-cli exposure --flag-dc-stale` - domain controllers that went stale or unprotected, surfaced first.
• **`bl