Agenten stärken
Installation vom Herausgeber. Kein PlugMCP-Endpunkt.
Host a copy with our keys and logs.
Noch kein paketiertes Release in der Registry. Folgen Sie der README des Repositorys.
Remote-URL oder ein Befehl auf Ihrem Rechner? Worin sich die beiden Installationen unterscheiden
Auf PlugMCP ausführen
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
StartenVom Herausgeber
CLI for the Action1 API — manage your endpoints, automations, patches, and more from the terminal.
CLI for the Action1 API — manage endpoints, automations, patches, vulnerabilities, software deployment & RBAC from the terminal. Includes MCP server (50 tools) for Claude Code / AI assistants.
--allGo to the Releases page and download the archive for your platform.
Or with a single command:
macOS (Apple Silicon — M1/M2/M3/M4):
curl -sL https://github.com/dimer47/action1-cli/releases/latest/download/action1-cli_darwin_arm64.tar.gz | tar xz
sudo mv action1 /usr/local/bin/
macOS (Intel):
curl -sL https://github.com/dimer47/action1-cli/releases/latest/download/action1-cli_darwin_amd64.tar.gz | tar xz
sudo mv action1 /usr/local/bin/
Linux (amd64):
curl -sL https://github.com/dimer47/action1-cli/releases/latest/download/action1-cli_linux_amd64.tar.gz | tar xz
sudo mv action1 /usr/local/bin/
Linux (arm64 — Raspberry Pi, etc.):
curl -sL https://github.com/dimer47/action1-cli/releases/latest/download/action1-cli_linux_arm64.tar.gz | tar xz
sudo mv action1 /usr/local/bin/
Windows:
Download action1-cli_windows_amd64.zip from the Releases page, extract and add the folder to your PATH.
go install github.com/dimer47/action1-cli@latest
The binary will be installed in $GOPATH/bin/ (usually ~/go/bin/). Make sure this directory is in your PATH.
git clone https://github.com/dimer47/action1-cli.git
cd action1-cli
go build -o action1 .
./action1 version
action1 version
# action1 version 0.1.0
The CLI automatically checks for new versions at startup and notifies you when an update is available.
# Update to the latest version
action1 self-update
# Check for updates without installing
action1 self-update --check
The update is downloaded from GitHub Releases and replaces the current binary in place. If the binary is in a protected directory (e.g. /usr/local/bin/), sudo will be requested automatically.
action1 auth login --region eu
Answer the prompts:
Region: eu (https://app.eu.action1.com/api/3.0)
Client ID: [email protected] # Paste your Client ID
Client Secret: # Paste your secret (hidden)
Successfully authenticated.
Token expires in 3600 seconds.
The client credentials are stored in the OS keychain (encrypted). Tokens are stored locally with restricted permissions (0600).
# List organizations to find your org ID
action1 org list
# Set the default
action1 config set org <orgId>
# List your endpoints
action1 endpoint list
# Check endpoint status
action1 endpoint status
# List vulnerabilities
action1 vulnerability list
# Run a report
action1 report data <reportId>
Located at:
~/Library/Application Support/action1/config.yaml~/.config/action1/config.yaml%APPDATA%\action1\config.yaml# Create a "production" profile
action1 config use-profile production
action1 auth login --region eu
# Create a "staging" profile
action1 config use-profile staging
action1 auth login --region na
# List profiles (* = active)
action1 config list-profiles
# default
# * production
# staging
# Switch profile
action1 config use-profile production
# Use a profile for a single command
action1 endpoint list --profile staging
Tokens (access + refresh) are always stored in the config file with restricted permissions, as they are too large for some keychain implementations.
Use --no-keychain to force file-based storage for everything.
action1 endpoint list # List all endpoints
action1 endpoint list --all # Fetch all (auto-paginate)
action1 endpoint list --filter "name eq 'SRV01'" # OData filter
action1 endpoint get <id> # Endpoint details
action1 endpoint status # Online/offline counts
action1 endpoint update <id> --name "new-name" # Rename
action1 endpoint delete <id> # Delete (asks confirmation)
action1 endpoint move <id> --to-org <orgId> # Move to another org
action1 endpoint missing-updates <id> # Missing patches
action1 endpoint install-url windowsEXE # Agent install URL
action1 endpoint-group list # List groups
action1 endpoint-group create --name "Servers" # Create
action1 endpoint-group members <id> # List members
action1 endpoint-group add <id> --endpoints a,b,c # Add endpoints
action1 endpoint-group remove <id> --endpoints a,b # Remove endpoints
# Schedules
action1 automation schedule list
action1 automation schedule create --data @schedule.json
action1 automation schedule get <id>
action1 automation schedule delete <id>
# Run immediately
action1 automation instance run --data @automation.json
action1 automation instance results <instanceId>
action1 automation instance stop <instanceId>
# Action templates
action1 automation template list
action1 automation template get <templateId>
action1 report list # List reports
action1 report data <reportId> # Get report rows
action1 report data <reportId> --all # All rows
action1 report export <reportId> --output-file r.csv
action1 report requery <reportId> # Re-run
action1 report drilldown <reportId> <rowId> # Row details
action1 software list # List packages
action1 software get <id> # Package details
action1 software clone <id> # Clone a package
action1 software version create <pkgId> --data @v.json
action1 software upload <pkgId> <verId> ./installer.exe
action1 update list # All missing updates
action1 update get <packageId> # Updates for a package
action1 update endpoints <pkgId> <verId> # Endpoints missing update
action1 installed-software list # All installed apps
action1 installed-software get <endpointId> # Apps on one endpoint
action1 installed-software requery # Refresh data
action1 vulnerability list # Vulnerable software
action1 vulnerability get <cveId> # CVE details (org)
action1 vulnerability cve <cveId> # CVE details (global)
action1 vulnerability endpoints <cveId> # Affected endpoints
action1 vulnerability remediation list <cveId> # Past remediations
action1 vulnerability remediation create <cveId> --data @control.json
action1 script list # List scripts
action1 script create --name "Cleanup" --type powershell --file cleanup.ps1
action1 script get <id>
action1 script update <id> --file cleanup_v2.ps1
action1 script delete <id>
action1 user me # Current user
action1 user list # All users
action1 user create --email [email protected] --name "Admin"
action1 role list # All roles
action1 role assign <roleId> <userId> # Assign user to role
action1 role permissions # Permission templates
action1 org list # List orgs
action1 org create --name "Production" # Create
action1 org update <id> --data '{"name":"Prod"}' # Update
action1 org delete <id> # Delete
action1 audit list # Audit events
action1 audit list --from 2026-01-01 --to 2026-01-31
action1 audit get <id> # Event details
action1 audit export --output-file audit.json # Export
action1 search "query" # Quick search
action1 log get # Diagnostic logs
action1 enterprise get # Enterprise settings
action1 subscription info # License info
action1 subscription usage # Usage stats
# Bash
action1 completion bash > /etc/bash_completion.d/action1
# Zsh (add to your .zshrc)
action1 completion zsh > "${fpath[1]}/_action1"
# Fish
action1 completion fish > ~/.config/fish/completions/action1.fish
# PowerShell
action1 completion powershell > action1.ps1
For faster typing:
The CLI includes a built-in MCP (Model Context Protocol) server exposing 50 tools for AI assistants.
Add to your Claude Code settings (or VS Code / JetBrains with the Claude extension):
{
"mcpServers": {
"action1": {
"command": "action1",
"args": ["mcp-serve"]
}
}
}
The MCP server automatically uses your credentials from
action1 auth login. No extra configuration needed.
Once configured, you can simply say:
Claude will automatically call the right MCP tools.
When the Action1 API rejects a request, the CLI appends a short explanation to the raw error when it recognises the case — so you don't have to rediscover the API's expectations by trial and error.
Error: API error 400: Invalid schedule settings
Format attendu pour settings :
ENABLED|DISABLED <fréquence> AT:hh-mm-ss [DATE:AAAA-MM-JJ]
...
Covered cases: settings schedule syntax, mandatory fields when creating a
script (platform, language, status, script_text), read-only fields
(randomize_start, success_codes), and retry_minutes on an
already-executed automation.
A hint prefixed with [observé] rests on an empirical finding the API docs do
not confirm — treat it as a lead, not a rule. Unprefixed hints were verified
directly.
The original API message is always preserved; hints never block a call, so a
change on Action1's side cannot make the CLI reject a valid value.
Hints live in internal/apierr/hints.go and are shared by the CLI and the MCP
server.
# Clone
git clone https://github.com/dimer47/action1-cli.git
cd action1-cli
# Build
go build -o action1 .
# Run tests
go test ./...
# Lint
go vet ./...
git tag v0.1.0
git push origin v0.1.0
# GitHub Actions builds and publishes automatically
MIT
CLI for the Action1 API — manage endpoints, automations, patches, vulnerabilities, software deployment & RBAC from the terminal. Includes MCP server (50 tools) for Claude Code / AI assistants.
Tools
Noch keine Tool-Liste. Remote-Server erhalten eine nach dem ersten Health-Check.
FAQ
Kopieren Sie auf dieser Seite die stdio-Konfiguration für Cursor, Claude Desktop, Claude Code oder VS Code. Sie nutzt die Installation des Herausgebers, keinen PlugMCP-Proxy.
In diesem Eintrag ist keine erforderliche Umgebungsvariable aufgeführt.
Action1 Cli läuft lokal über stdio.
Zuletzt geprüft: 2026-10-28. CLI for the Action1 API — manage endpoints, automations, patches, vulnerabilities, software deployment & RBAC from the terminal. Includes MCP server (50 tools) for Claude Code / AI assistants.