Action1 MCP

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

API. Not affiliated with, endorsed by, or sponsored by Action1 Corporation.

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

Every Action1 endpoint, plus fleet-wide patch and vulnerability views across all your organizations. 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 action1-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 action1-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 ACTION1_CLI_PATH to an existing binary). Details: #331.

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

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

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

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

macOS / Linux:

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

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

Verify:

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

Windows (PowerShell):

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

Inside a Hermes chat session:

/skills install servosity/msp-skills/skills/action1 --force

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

Install for OpenClaw

Tell your OpenClaw agent (copy this):

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

ACTION1_CLIENT_ID=<value> ACTION1_CLIENT_SECRET=<value> action1-cli doctor

PowerShell:

$env:ACTION1_CLIENT_ID = "<value>"; $env:ACTION1_CLIENT_SECRET = "<value>"; action1-cli doctor

For the EU or Australia data center also set ACTION1_BASE_URL (https://app.eu.action1.com/api/3.0 or https://app.au.action1.com/api/3.0); the token is minted from that same host.

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 Action1 integrations and MCP servers proxy each question into a live API call, one organization at a time. That's fine for one record. It dies at scale, when you're asking "which endpoint across all 40 of my clients is most behind on patches, and which CVE is on the most machines this quarter" - questions the org-siloed API cannot answer in a single call.

This skill syncs every organization into a local SQLite mirror with full-text search. Aggregate questions become one local query: instant, offline, and the AI sees the answer, not the raw data. Cross-org rollups like fleet patch-posture, fleet vuln-triage, and fleet org-scorecard join across every organization's endpoints, updates, and vulnerabilities at once - work a stateless API wrapper can't do.

The pain this closes

Patch-management threads on r/msp keep surfacing the same gap with multi-tenant patch tools: the console is organized one client organization at a time, but the questions an MSP owner has to answer are fleet-wide - "which endpoints are most behind?", "which CVE is everywhere?", "what posture number goes in this client's QBR?" In Action1 that means switching organizations one by one, or exporting per-org and merging spreadsheets. The data is there per client; it just doesn't roll up across every organization in one view.

This skill closes that gap:

• action1-cli fleet patch-posture - every endpoint, all orgs, ranked by missing updates.
• action1-cli fleet vuln-triage --kev-only - CVEs ranked by blast radius (CVSS + CISA KEV).
• action1-cli fleet org-scorecard - one posture row per client organization, the QBR number in a line.
• action1-cli fleet stale --days 14 - dark agents across every org, before they fall out of coverage.
• action1-cli fleet reboot-pending - the fleet-wide action queue that closes out a patch cycle.

See pain-point.md for the longer narrative.

Remote desktop through the MCP server

The MCP already exposes Action1's remote-session API. The API credential needs Remote Connect on the target endpoint's organization or endpoint group; permission to run scripts does not imply permiss