MCP server for Action1 — endpoint inventory, patch visibility, and policy automation. Read-only v1.
- ✓Open-source license (Apache-2.0)
- ✓Actively maintained (<30d)
- ✓Clear description
- ✓Documented (README)
claude mcp add action1-mcp -- npx -y github{
"mcpServers": {
"action1-mcp": {
"command": "npx",
"args": ["-y", "github"],
"env": {
"ACTION1_API_KEY": "<action1_api_key>",
"ACTION1_SECRET": "<action1_secret>"
}
}
}
}ACTION1_API_KEYACTION1_SECRETMCP Servers overview
# Action1 MCP Server [](https://modelcontextprotocol.io) [](LICENSE) MCP server for [Action1](https://www.action1.com/) — endpoint inventory, patch visibility, and policy automation via the [Model Context Protocol](https://modelcontextprotocol.io). Read-only in v1. Deploy / automation surface is intentionally separated to a later release for blast-radius reasons (a bad policy push can brick endpoint fleets). ## Tools | Tool | Description | |---|---| | `action1_navigate` | Discover available tools by domain (organizations / endpoints / policies / updates) | | `action1_list_organizations` | List Action1 tenants accessible to the configured credentials | | `action1_list_endpoints` | List managed devices in an organization | | `action1_get_endpoint` | Get a single endpoint by id | | `action1_list_missing_updates` | List missing OS/application patches across endpoints — Action1's headline value-prop | | `action1_list_policies` | List automation / policy / remediation rules | API surface maps to [PSAction1](https://github.com/Action1Corp/PSAction1) (Action1's MIT-licensed PowerShell module). When the v1 surface earns its keep, write tools (deploy, requery, package upload) come in v2 behind separate review. ### Interactive Device Card (MCP Apps) `action1_get_endpoint` renders as an interactive device-summary card in MCP Apps hosts (Claude Desktop/web) — status, OS, user, IP, agent version, reboot-required, and missing-update counts at a glance; plain-JSON behavior is unchanged in other hosts. The card is read-only (matching the v1 tool surface), neutral by default, and brandable via `window.__BRAND__` injection or `MCP_BRAND_*` env vars (`MCP_BRAND_NAME`, `MCP_BRAND_LOGO_URL`, `MCP_BRAND_PRIMARY_COLOR`, `MCP_BRAND_ACCENT_COLOR`, `MCP_BRAND_BG`, `MCP_BRAND_TEXT`) — no rebuild needed. ## Usage ### Claude Desktop (MCPB) Install via the MCPB bundle from the [latest release](https://github.com/wyre-technology/action1-mcp/releases). Required credentials (created in Action1 → Settings → API Credentials, **non-recoverable on creation — copy immediately**): - API Key (Client ID) - Secret - Region (`NorthAmerica` default; also `Europe`, `AsiaPacific`, `Australia`) - Optional default organization id (for single-tenant use) ### Stdio (direct) ```bash ACTION1_API_KEY=... \ ACTION1_SECRET=... \ ACTION1_REGION=NorthAmerica \ ACTION1_DEFAULT_ORG_ID=org-... \ npx -y github:wyre-technology/action1-mcp ``` ### HTTP (gateway mode) ```bash MCP_TRANSPORT=http PORT=8080 AUTH_MODE=gateway \ docker run -p 8080:8080 ghcr.io/wyre-technology/action1-mcp:latest ``` Per-request credentials via headers: - `X-Action1-API-Key` - `X-Action1-Secret` - `X-Action1-Region` - `X-Action1-Default-Org-Id` ## Architecture ``` src/ ├── index.ts # stdio + HTTP transports, tool dispatch ├── card.builder.ts # MCP Apps device-card normalization + brand injection ├── resources.ts # resources/list + resources/read (ui:// device card) ├── generated/ │ └── device-card-html.ts # committed vite single-file bundle (npm run build:ui) ├── sdk/ │ └── action1-client.ts # embedded REST + OAuth client (factor-out candidate │ # if surface crosses ~20 tools / 2+ domains) ├── utils/ │ ├── client.ts # credential resolution (env vs gateway headers) │ └── types.ts # DomainHandler interface ├── domains/ # one file per resource type │ ├── organizations.ts │ ├── endpoints.ts │ ├── policies.ts │ └── updates.ts └── __tests__/ # domain tests + MCP Apps contract tests ui/ # device-card source (index.html + device-card.ts) ``` Per-request credential isolation via `AsyncLocalStorage` — concurrent requests in HTTP mode never share credentials through `process.env`. ## Development ```bash npm install npm run build npm test npm run dev # tsc --watch npm run lint # eslint npm run typecheck ``` ## License Apache-2.0. See [LICENSE](LICENSE).
What people ask about action1-mcp
What is wyre-technology/action1-mcp?
+
wyre-technology/action1-mcp is mcp servers for the Claude AI ecosystem. MCP server for Action1 — endpoint inventory, patch visibility, and policy automation. Read-only v1. It has 2 GitHub stars and its last recorded update is dated 2026-08-20.
How do I install action1-mcp?
+
You can install action1-mcp by cloning the repository (https://github.com/wyre-technology/action1-mcp) or following the README instructions on GitHub. ClaudeWave also provides quick install blocks on this page.
Is wyre-technology/action1-mcp safe to use?
+
Our security agent has analyzed wyre-technology/action1-mcp and assigned a Trust Score of 87/100 (tier: Trusted). See the full breakdown of passed checks and flags on this page.
Who maintains wyre-technology/action1-mcp?
+
wyre-technology/action1-mcp is maintained by wyre-technology. The last recorded GitHub activity is dated 2026-08-20, with 2 open issues.
Are there alternatives to action1-mcp?
+
Yes. On ClaudeWave you can browse similar mcp servers at /categories/mcp, sorted by popularity or recent activity.
Deploy action1-mcp to your cloud
Ship this repo to production in minutes. Each platform spins up its own environment with editable env vars.
Maintain this repo? Add a badge to your README
Drop the badge into your GitHub README to show it's tracked on ClaudeWave. Each badge links back to this page and reflects the live Trust Score.
[](https://claudewave.com/repo/wyre-technology-action1-mcp)<a href="https://claudewave.com/repo/wyre-technology-action1-mcp"><img src="https://claudewave.com/api/badge/wyre-technology-action1-mcp" alt="Featured on ClaudeWave: wyre-technology/action1-mcp" width="320" height="64" /></a>More MCP Servers
Fair-code workflow automation platform with native AI capabilities. Combine visual building with custom code, self-host or cloud, 400+ integrations.
User-friendly AI Interface (Supports Ollama, OpenAI API, ...)
An open-source AI agent that brings the power of Gemini directly into your terminal.
Real-time global intelligence dashboard. AI-powered news aggregation, geopolitical monitoring, and infrastructure tracking in a unified situational awareness interface
The fastest path to AI-powered full stack observability, even for lean teams.
🕷️ An adaptive Web Scraping framework that handles everything from a single request to a full-scale crawl!