Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
作者による説明(英語の原文)
Every Action1 endpoint, plus fleet-wide patch and vulnerability views across all your organizations.
この3つを1つのスコアにまとめることはしません。意見、測定、人気はそれぞれ別のものだからです。
このサーバーのやさしい解説はまだ書いていません。以下はレジストリから読み取った事実です。
使っているAIアプリを選んで、設定をコピーしてください。
ACTION1_BASE_URL, ACTION1_CLIENT_ID, ACTION1_CLIENT_SECRET, ACTION1_OAUTH2, ACTION1_ORG_ID, ACTION1_NO_CONFIG_WRITE, ACTION1_MCP_READ_ONLY, ACTION1_NO_LOCAL_DATA, ACTION1_USER_AGENT, ACTION1_MCP_HTTP_TOKEN, PRINTING_PRESS_CLIENT_PROFILE「秘密」と表示された値は、あなたのアカウントの鍵です。絶対に人に教えたり、チャットに貼り付けたりしないでください。
どのアプリを使っていますか?
上でアプリを選んでください。選んだアプリを覚えておくので、次からはボタンに「…にインストール」と表示されます。
リンク先は作者自身のファイルです。私たちが置いたり再パッケージしたりしたものではありません。ファイルを開くと、Claude Desktopがインストールします。
ターミナルでこれを実行します
動かす前に、空欄の値を入力してください。
ブラウザがアプリを開いてよいか確認し、そのあとアプリが設定を表示して確認を求めます。キーの値は空欄のままなので、自分で入力してください。
ブラウザがアプリを開いてよいか確認し、そのあとアプリが設定を表示して確認を求めます。キーの値は空欄のままなので、自分で入力してください。
これはパソコンで動くサーバーですが、ChatGPTがつなげるのはインターネット上のサーバーだけです。ほかのアプリを選んでください。
選んだアプリは、この端末のCookieに保存されます。アカウントは不要です。
ACTION1_BASE_URL envACTION1_ORG_ID envACTION1_NO_CONFIG_WRITE envACTION1_MCP_READ_ONLY envACTION1_NO_LOCAL_DATA envACTION1_USER_AGENT envPRINTING_PRESS_CLIENT_PROFILE envこの設定は、作者のレジストリ登録情報から作成しています。READMEと違う場合は、READMEに従ってください。
パソコンで動くサーバーです。インストールすると、ツール一覧がAIアプリに表示されます。
誰でも見られる情報をチェックしており、コードは読んでいません。当てはまらない項目は数に入れていません。 · 2026年11月6日にチェック
レジストリ名は、リポジトリを所有するGitHubアカウント servosity で確認済みです
このリポジトリはまだGitHubから読み取っていません
このリポジトリはまだGitHubから読み取っていません
これはパソコンで動くため、インターネット上のエンドポイントはありません
パソコンで動き、代わりにローカルの設定を使います
パソコンで動くサーバーです。ツール一覧を読み取れるのは、インターネット上のエンドポイントがある場合だけです
レジストリでこのカテゴリにある有効なすべてのサーバーと比較しています。スターは、公開者がリポジトリの所有者である場合だけ数えます。
当てはまる基本チェック1項目のうち1項目に合格しました。コードは読んでいません。キーやトークンを追加する前に、サーバーがどんなアクセスを求めているかを確認し、必要な権限だけを持つキーを使ってください。
入力が必要なもの:ACTION1_CLIENT_ID, ACTION1_CLIENT_SECRET, ACTION1_OAUTH2, ACTION1_MCP_HTTP_TOKEN
あなたのパソコンで動きます。必要なときにAIアプリが起動し、データは作者のサーバーを通りません(サーバー自体がオンラインサービスを呼び出す場合を除きます)。
GitHubリポジトリの最終更新は–、最新バージョン(0.1.11)がレジストリに届いたのは今日です。
Claude Desktop、Claude Code、Cursor、VS CodeなどのMCP対応アプリで使えます。パソコンにMCPBも必要です。
同じカテゴリには:Spec Driven Development, Remote Desktop Commander, zanadir
同じカテゴリで、ほかの作者が作ったサーバー。スターの多い順。
カードの見方:★ GitHubスターi3つの柱:レビュー · チェック · 利用状況i更新=最新バージョンをレジストリに公開した日i
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Find what a repository's CI is missing, and which security checks cannot fail the build.
作者のリポジトリから書かれたとおりにコピーしたものです。PopNx MCPは内容を確認・推奨していません。HTML、画像、スクリプトは取り除いています。リンクはこのサイトの外へ移動します。
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.
Security note (until this connector is reprinted). Do not run HTTP mode
(
--transport http), not even on localhost. This build has no password,
listens on every network interface, and predates the browser-rebinding guard,
so a web page you open can reach it. The MCP tools can also make changes with
your credentials. Use the default stdio transport. If you set up 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):
| Your AI agent | How to install the Action1 skill |
|---|---|
| Claude Desktop | Run installer, then Settings > Extensions to register action1-mcp (no JSON editing). |
| ChatGPT (desktop app) | Run installer, then add action1-mcp in Settings > MCP servers as a local (STDIO) server. ChatGPT on the web is not supported yet. |
| Codex CLI | Paste the install prompt below. |
| Claude Code | Paste the install prompt below. |
| Claude Cowork | Paste the install prompt below. |
| GitHub Copilot (VS Code) | Run installer, add action1-mcp to mcp.json under the servers key, then pick Agent mode. |
The ChatGPT desktop app runs action1-mcp locally and shares MCP configuration with Codex (OpenAI). ChatGPT on the web needs a remote (HTTP) server, and this connector's HTTP mode 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.
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.
| Agent | What it takes |
|---|---|
| Microsoft 365 Copilot / Copilot Studio | Not supported by msp-skills yet: it needs a remote server. A hosted gateway is the better pick; check that your AI app is on the gateway's setup list. |
| Google Gemini | Gemini CLI is local - same as Claude Code. See mcp-install.md. The Gemini app needs a remote server and is not supported by msp-skills yet. |
Skill-native agents (also covered): Hermes and OpenClaw read this skill's
SKILL.mddirectly *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.
.mcpbClaude Desktop bundle: the
.mcpblaunches on macOS (Intel and Apple Silicon), Windows x64 and Linux x64. Every tool shells out to the companionaction1-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 setACTION1_CLI_PATHto 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
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, runiwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/action1/install.ps1 | iex. Then authenticate per the README and runaction1-cli --helpto explore.
The same prompt works in any agent that can run shell.
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
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.
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.
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.
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 theopenclaw:frontmatter block.
OpenClaw isn't generally available yet; the frontmatter wiring is pre-shipped and will activate the moment OpenClaw launches.
Set the credentials the CLI needs (from your Action1 portal):
ACTION1_CLIENT_ID=<value> ACTION1_CLIENT_SECRET=<value> ACTION1_REGION=<value> action1-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.
| Question your MSP keeps asking | Command |
|---|---|
| Which endpoints across all clients are missing the most patches? | action1-cli fleet patch-posture |
| Which CVEs hit the most machines, severity- and KEV-weighted? | action1-cli fleet vuln-triage --kev-only |
| Which agents have stopped checking in across the fleet? | action1-cli fleet stale --days 14 |
| What is the patch-and-vulnerability posture per client organization? | action1-cli fleet org-scorecard |
| Which endpoints are waiting on a reboot to finish a patch cycle? | action1-cli fleet reboot-pending |
| Rank every endpoint by overall risk (updates, CVEs, reboot, staleness) | action1-cli fleet health-score |
| What software is installed across the whole fleet, deduped by version? | action1-cli fleet software-rollup |
| List the managed endpoints in one client organization | action1-cli endpoints managed |
Full command reference: guide.md. For the AI-agent operating contract (--agent, --dry-run, when to confirm before mutating), see AGENTS.md.
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.
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]
冒頭だけを表示しています。続きはリポジトリで読めます