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.

[Action1 demo - animated preview]

_{▶ 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.

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 and 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 permission to connect to a desktop. An authorized administrator can add Remote Connect to the credential's existing role with the intended scope. A 403 is an access denial, not a missing MCP tool.

For code-orchestration clients:

1. Call action1_search with start remote session.

2. Call action1_execute with endpoint ID endpoints.managed-id-remote-sessions-post and these params:

   json

   {"orgId":"<organization-id>","endpointId":"<endpoint-id>","connection_type":"assistance"}

3. Take the returned id and call endpoints.managed-id-remote-sessions-session-id-get with orgId, endpointId, and sessionId. Poll with a bounded wait, for example every five seconds for up to one minute, stopping on an API error. A timeout means the connection was not verified; do not automatically create another session.

4. Once connected is yes, open the returned remote_session URL in a browser. Verify that the intended endpoint's desktop is visible before interacting. Keep this connection URL private.

The equivalent start command is:

action1-cli endpoints managed-id-remote-sessions-post <orgId> <endpointId> --connection-type assistance --json

The API currently supports assistance as the connection type. Starting the session does not itself automate desktop input; use the browser or your agent's authorized computer-use tools for the interactive part. See the Action1 remote-session API and API credential roles.

Software installer packages through the MCP server

The MCP already exposes Software Repository package and version reads and updates. API-key authorization is separate from browser/Entra SSO. A console sign-in failure does not establish that the package API is unavailable.

• orgId is a scope selector. An organization ID requests that organization's view; all requests Enterprise scope. Some Enterprise-shared packages are readable through an organization view, but this does not prove Enterprise write access. Use all for Enterprise-shared package updates.
• Reads require View Software Repository in the requested scope. Updates require Manage Software Repository in the package scope; it implicitly includes View. For version PATCH, approval_status instead requires Approve Updates, and EULA_accepted requires the API's accept_eula permission. Script actions also require the appropriate Use Scripts scope. Built-in package versions cannot be modified. An administrator can extend the credential's existing role when authorized; HTTP 403 is a permission/scope denial, not a missing MCP endpoint.
• versionId is the version object's id, not its displayed version. For example, id: "21.07.00.0_1640795090369" and version: "21.07.00.0" identify different fields. Always discover current IDs instead of guessing them.

For code-orchestration clients:

1. Call action1_search with installer to find the package and version tools.

2. Call action1_execute with endpoint ID software-repository.packages-all-package-id-get and these params:

   json

   {"orgId":"<organization-id-or-all>","packageId":"<package-id>","fields":"versions"}

3. Take the selected object's versions[].id. Read its configuration using software-repository.versions.packages-all-package-id-id-get with orgId, packageId, and that versionId.

4. Preserve the existing configuration and prepare the smallest authorized update. Package metadata uses software-repository.packages-all-package-id-patch; installer deployment configuration uses software-repository.versions.packages-all-package-id-id-patch. Pass the same identifiers plus only the edited, writable version properties to action1_execute. Put those properties directly in params, for example:

   json

   {"orgId":"<organization-id-or-all>","packageId":"<package-id>","versionId":"<returned-version-id>","silent_install_switches":"<reviewed silent-install switches>"}

   Use the Windows or Mac version PATCH schema in the vendor API reference for field names and types. Do not replay the entire GET response or nest the properties under body-json. That flag belongs to the equivalent CLI command, which accepts the update object via --body-json or --stdin.

5. Read back the package/version after updating. A successful write does not prove installation or deployment on an endpoint.

See extended package data and repository permissions.

Frequently asked questions

Does this work with ChatGPT?

Yes, in the ChatGPT desktop app. It runs MCP servers locally (STDIO), the way action1-mcp runs, and shares MCP configuration with Codex (OpenAI): add action1-mcp under Settings > MCP servers as a STDIO server, or add it once to Codex's ~/.codex/config.toml. ChatGPT on the web is not supported by msp-skills yet: it needs a remote server. If your team works there, a hosted gateway is the better pick; check that your AI app is on the gateway's setup list.

Does this work with Codex, Cursor, Windsurf, Cline, Copilot, or Gemini?

Yes - all of them speak MCP. Cross-tool install commands are in the matrix above and the deep-dive in docs/which-agent.md.

Do I need to know how to code?

No. The recommended install is to paste one sentence into Claude Code or Codex - your agent reads SKILL.md and does the install. The fallback is a one-line installer per OS (bash or PowerShell). Neither path requires writing code. You'll enter your Action1 credentials once.

Is my Action1 data safe?

Your data stays on your machine. The CLI and MCP server are local binaries. The SQLite mirror sits in a directory under your user account. The AI agent only sees what the CLI returns - typically a query result, not raw bulk data. Credentials are read from your environment or your agent's config; never bundled into this repo or transmitted anywhere by MSP Skills.

Which Action1 region and credentials do I need?

An API client (Client ID + Client Secret) from your Action1 console's API Credentials page, plus ACTION1_BASE_URL set to your data center (https://app.action1.com/api/3.0 is the default; EU is https://app.eu.action1.com/api/3.0, Australia https://app.au.action1.com/api/3.0) to match your console URL. The CLI POSTs them to /oauth2/token and mints and refreshes the bearer token for you. Scope the client to read-only permission templates if you only need reporting - see governance.md.

Does this replace the Action1 console?

No. The console stays your place to configure automations and approve patches interactively. This skill answers the cross-organization questions the console shows one org at a time - fleet patch posture, CVE blast-radius, per-client scorecards - and lets your AI agent run them from the terminal.

What does it cost?

Free. Apache-2.0 licensed. You pay only for whichever AI agent you use (Claude, ChatGPT, Codex, etc.), and that's billed by your AI provider, not by us.

Safety model

The strongest control is the scope you grant the Action1 credentials - the CLI can only do what the credentials are permitted to do. Full details, including how to lock it down, are in governance.md.

Status

Beta. Validated against the Action1 API surface and being validated with MSPs running it live against their own production tenant in our weekly Build Sessions. RSVP at compoundingteams.com/build-sessions.

Standards. Conforms to the open Agent Skills spec (Anthropic, Dec 2025; 40+ agents). MCP-compatible - works with any MCP-capable agent including Hermes. OpenClaw-ready (frontmatter pre-wired, awaiting OpenClaw launch).

Maintained by Servosity. Apache-2.0 licensed. Built with CLI Printing Press. Last updated: 2026-06-06.