Atera + AI in 60 seconds
Unofficial. Community-built Claude Code Skill and MCP server for the Atera API. Not affiliated with, endorsed by, or sponsored by Atera Networks Ltd.
Awaiting live verification - passes every mechanical gate (build, command-surface, claims, install). Be the first to confirm it against your tenant: report it works.
Ask plain-English questions about your whole Atera estate and get answers the portal can’t assemble in one view: which agents went dark, which tickets are about to breach SLA, which customers are under-contracted, and what contracts expire next quarter. atera-cli syncs Atera into a local SQLite mirror, then answers cross-client rollups instantly and offline - from the terminal or any AI agent.
New to the term? An MCP server is the same thing ChatGPT calls an app or connector, Claude on the web calls a connector, and Claude Code calls a Skill. One thing, many names →
Install in 60s → View on GitHub →
Instead of clicking through Atera, just ask
Instead of Exporting the agents list and filtering by last-seen date to find the machines that quietly stopped reporting
just ask: “Which Atera agents have gone dark in the last 30 days?”
Your agent runs: atera-cli agents stale --days 30 --agent
Instead of Opening every open ticket to eyeball which ones are closest to breaching first-response or resolution SLA
just ask: “Which open Atera tickets are about to breach SLA?”
Your agent runs: atera-cli tickets sla --agent
Instead of Cross-referencing the customer list against contracts by hand to spot accounts you manage but don’t bill
just ask: “Which customers have managed agents but no active contract?”
Your agent runs: atera-cli customers coverage --agent
See it in 30 seconds
Demo data is simulated. Every command shown exists in the real CLI.
What it does
| Question your MSP keeps asking | Command your agent runs |
|---|---|
| Which agents have gone offline or stopped checking in? | atera-cli agents stale --days 30 |
| Which open tickets are closest to breaching SLA? | atera-cli tickets sla |
| Who is overloaded on the service desk right now? | atera-cli tickets workload |
| Which customers have managed agents but no active contract? | atera-cli customers coverage |
| What contracts expire in the next 60 days? | atera-cli contracts expiring --days 60 |
| What’s my full book of business by customer and contract mix? | atera-cli customers book |
| Which machines generate the most alerts over a week? | atera-cli agents noisy --days 7 |
| What’s the patch-compliance picture across the fleet? | atera-cli agents patch-status |
| Which machines are running an end-of-life OS? | atera-cli agents inventory --eol |
| What changed across agents, tickets, and alerts in the last 24 hours? | atera-cli since 24h |
Full command reference at github.com/servosity/msp-skills/blob/main/skills/atera/guide.md.
What makes this one different
Most Atera integrations proxy each question into a live API call - fine for one record, useless for a fleet-wide rollup that would page through thousands of objects against the rate limit. This skill syncs Atera into a local SQLite mirror, so cross-entity questions become one offline join: instant, rate-limit-friendly, and the AI sees the answer, not the raw dump.
Atera’s portal and its add-on AI surface single records and canned reports; this skill answers the cross-client, time-windowed questions the portal leaves you to assemble by hand - dark-agent sweeps, SLA-breach queues, under-contracted accounts, and renewal calendars - from one local mirror you can read every line of.
The pain this closes
- Atera’s reporting is the consistent gripe in G2 and Capterra reviews: custom reports need workarounds, filtering is rigid, exports are clunky, and the deeper cross-client analytics sit behind higher-tier plans.
- There’s no single screen that answers ‘which machines went dark,’ ‘which tickets breach SLA next,’ or ‘which customers are under-contracted’ across every client at once - you assemble it by hand, portal tab by portal tab.
- Pulling fleet-wide numbers through the live API means paging thousands of objects against a rate limit, so the questions that matter at a QBR are the ones nobody has time to answer.
Install
Works in any of these agents - pick yours:
| Agent | Quick install |
|---|---|
| Claude Desktop | Step-by-step → |
| ChatGPT (Plus/Pro+) | Step-by-step → |
| Claude Code | Step-by-step → |
| Codex CLI | Step-by-step → |
| Cursor, Windsurf, Cline, Continue, Zed, Copilot, Gemini, Hermes, OpenClaw | Which agent? → |
Quickest path for everyone else (terminal):
macOS / Linux:
bash <(curl -fsSL https://raw.githubusercontent.com/servosity/msp-skills/main/skills/atera/install.sh)
Windows (PowerShell):
iwr -useb https://raw.githubusercontent.com/servosity/msp-skills/main/skills/atera/install.ps1 | iex
After install, authenticate once with your Atera credentials, then verify with atera-cli --version.
Safety model
| Tier | Examples | Recommended agent policy |
|---|---|---|
| Read | agents stale, tickets sla, customers coverage, contracts expiring, since, search, sync, and every get-/rollup command | Allow |
| Write (routine) | tickets post/put, contacts post/put, customers post/put, contracts post/update, alerts post/resolve, devices create-, customvalues set-, import | Preview with –dry-run, then a reviewed write |
| Destructive / config | agents delete, tickets delete, customers delete, devices delete-*, and credential changes (auth set-token, auth setup, auth logout) | Human-in-the-loop only |
The skill reads everything - agents, tickets, customers, contracts, alerts, devices, rates, and custom fields - and can also create, update, and delete those records through the Atera API. Reads, including every cross-client rollup, are always safe to run; routine writes should be previewed with --dry-run and approved before they fire; deletes and credential changes are human-in-the-loop only. The CLI can only do what your Atera API key is permitted to do, so scope the key to the workflow. Full details in governance.md.
Frequently asked questions
Does this work with ChatGPT?
Yes, on paid ChatGPT plans. ChatGPT connects to remote MCP servers over HTTPS, so you expose the local Atera MCP server via a secure bridge. Step-by-step in the install guide.
Do I need to know how to code?
No. Paste one sentence into Claude Code or Codex and your agent does the install, or run a one-line installer. You enter your credentials once.
Is my Atera data safe?
Your data stays on your machine. The CLI, MCP server, and the local mirror are all local. The AI sees query results, not raw bulk data, and credentials are never bundled or transmitted by MSP Skills.
What does it cost?
Free. Apache-2.0 licensed. You pay only for whichever AI agent you already use.
Will this hit my Atera API rate limits?
Rarely. Most questions run against the local SQLite mirror after a one-time sync, so they make zero API calls. The few commands that fetch live (like agents patch-status) are paced under Atera’s 700-requests-per-minute limit.
Do I need to be an Atera partner?
No. You need an Atera account and an API key created under Admin → API. Any plan that exposes the API works; nothing here requires a special partner tier.
Will this replace my Atera portal?
No - it complements it. The portal stays your system of record and remote-access console; this skill adds the cross-client, terminal-and-AI query layer the portal doesn’t offer.
Status
Beta. Validated against the Atera API surface and being validated with MSPs running it live against their own production tenants in our weekly 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 for the MSP community. Apache-2.0 licensed. Built with CLI Printing Press.