Atera MCP

io.github.ServosityPublished by GitHub account Servosityv0.1.8Updated Oct 24, 2026

Every Atera RMM + PSA endpoint, plus a local SQLite mirror that answers fleet-health, SLA, and

Overview

AI-generated overview

Unofficial local MCP server and CLI that lets an assistant query Atera RMM/PSA data, including a local SQLite mirror for fleet-health, SLA and contract rollups.

What you can do
  • Query Atera RMM and PSA records through the full API surface, plus a local SQLite mirror with full-text search
  • Check fleet health: stale agents, noisy machines, patch status, end-of-life inventory
  • Review service desk load: open tickets ranked by time to SLA breach, technician workload
  • Analyze the book of business: customers with agents but no active contract, expiring contracts, coverage by customer
  • Summarize what changed across agents, tickets and alerts over a period
  • Create and update tickets, contacts, customers, contracts, alerts and devices, and delete records
When to use it
Useful for MSP owners and service desk leads who want an AI assistant to answer cross-client questions Atera's portal and reporting do not show in one view, such as which machines went dark, which tickets breach SLA next, or which customers are under-contracted.
Requirements
Runs as a local process (stdio) on the user's machine; desktop agents only, not web clients. Needs an Atera account and an API key created under Admin, supplied as ATERA_API_KEY, plus ATERA_ACCOUNT_API. ATERA_BASE_URL has a prefilled default for regional or self-hosted hosts. Some tools call a companion CLI binary.
Before you install
The README warns that HTTP mode is unsafe in this build: no password, listens on all interfaces, and a web page could reach it, so use stdio only and shut down any tunnel. Tools can make changes with your credentials, including deletes and credential changes; preview writes with dry-run and keep destructive actions human-reviewed. Credentials are read from the environment or agent config. Beta software, unofficial and not affiliated with Atera.

Installation

In SourceWeft

  1. Open Atera MCP in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

Atera + 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 Atera API. Not affiliated with, endorsed by, or sponsored by Atera Networks Ltd.

[Atera demo - animated preview]

▶ Watch the 30-second demo - demo data is simulated; every command shown exists in the real CLI.

Every Atera RMM + PSA endpoint, plus a local SQLite mirror that answers fleet-health, SLA, and book-of-business questions no single API call can. 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

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 agentHow to install the Atera skill
Claude DesktopRun installer, then Settings > Extensions to register atera-mcp (no JSON editing).
ChatGPT (desktop app)Run installer, then add atera-mcp in Settings > MCP servers as a local (STDIO) server. ChatGPT on the web is not supported yet.
Codex CLIPaste the install prompt below.
Claude CodePaste the install prompt below.
Claude CoworkPaste the install prompt below.
GitHub Copilot (VS Code)Run installer, add atera-mcp to mcp.json under the servers key, then pick Agent mode.

The ChatGPT desktop app runs atera-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.

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.

AgentWhat it takes
Microsoft 365 Copilot / Copilot StudioNot 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 GeminiGemini 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.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 atera-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 ATERA_CLI_PATH to an existing binary). Details: #331.

Download Atera MCP (.mcpb) - then open Claude Desktop > Settings > Extensions and select the file. One click, no JSON, no shell. (Browse every Atera 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 atera@msp-skills

Path A - paste one prompt into your AI agent (recommended)

Copy this into Claude Code, Codex CLI, or Claude Cowork:

Install the Atera 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/atera/install.sh). If it uses Windows PowerShell, run iwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/atera/install.ps1 | iex. Then authenticate per the README and run atera-cli --help to explore.

The same prompt works in any agent that can run shell.

Path B - run the installer yourself

Windows (PowerShell):

powershell
iwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/atera/install.ps1 | iex

macOS / Linux:

bash
bash <(curl -fsSL https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/atera/install.sh)

The installer drops both atera-cli (the CLI) and atera-mcp (the MCP server) into your user bin path. Claude Code, Codex, and Cowork discover the Skill via SKILL.md in this directory.

Verify:

bash
atera-cli --version

Upgrade to the latest version

The installer always fetches the current release - re-run it to upgrade:

macOS / Linux:

bash
bash <(curl -fsSL https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/atera/install.sh)

Windows (PowerShell):

powershell
iwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/atera/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 atera@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:

bash
hermes skills install servosity/msp-skills/skills/atera --force

Inside a Hermes chat session:

/skills install servosity/msp-skills/skills/atera --force

Hermes speaks MCP natively, so it can also use the atera-mcp server directly - same install path, same env vars.

Install for OpenClaw

Tell your OpenClaw agent (copy this):

Install the atera skill from https://github.com/servosity/msp-skills/tree/main/skills/atera. The skill defines how its required CLI (atera-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

Create an API key in your Atera portal under Admin → API, then set it and confirm it works:

bash
ATERA_API_KEY=<your-key> atera-cli doctor

doctor confirms the credential works and the API is reachable before you run anything that touches data. It exits 0 even when the credential is rejected, so scripts should add --fail-on error. You can also persist it with atera-cli auth set-token.

What this skill does

Question your MSP keeps askingCommand
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
Where are the chronic machines generating the most alerts?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 since yesterday?atera-cli since 24h

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 Atera integrations and MCP servers proxy each question into a live API call. That's fine for one record. It dies at scale, when you're asking "which customers across all 40 clients have managed agents but no active contract" or "what's about to breach SLA right now."

This skill syncs Atera into a local SQLite mirror with full-text search. Aggregate questions become one local SQL join: instant, offline, and the AI sees the answer, not the raw data. Compound commands like customers coverage, customers book, and agents noisy join across customers, contracts, agents, and alerts - work a stateless API wrapper can't do.

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.

This skill closes that gap with cross-client rollups that run offline against the local mirror:

  • atera-cli agents stale --days 30 - the machines that quietly stopped reporting, before the client calls.
  • atera-cli tickets sla - open tickets ranked by minutes-to-breach, soonest first.
  • atera-cli customers coverage - accounts you manage but don't bill: managed agents, no active contract.
  • atera-cli contracts expiring --days 60 - the renewal calendar Atera never shows as one view.
  • atera-cli agents patch-status - fleet-wide missing-patch rollup the API has no single endpoint for.

See pain-point.md for the longer narrative.

Frequently asked questions

Does this work with ChatGPT?

Yes, in the ChatGPT desktop app. It runs MCP servers locally (STDIO), the way atera-mcp runs, and shares MCP configuration with Codex (OpenAI): add atera-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 (HTTP) server, and this connector's HTTP mode is paused until it is reprinted; the security note in mcp-install.md explains why. 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 Atera credentials once.

Is my Atera 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.

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.

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

TierExamplesRecommended agent policy
Readagents stale, tickets sla, customers coverage, contracts expiring, since, search, sync, every get-/rollup commandAllow
Write (routine)tickets post/put, contacts post/put, customers post/put, contracts post/update, alerts post/resolve, devices create-*, customvalues set-*, importPreview with --dry-run, then a reviewed write
Destructive / configagents delete, tickets delete, customers delete, devices delete-*, and credential changes (auth set-token, auth setup, auth logout)Human-in-the-loop only

The strongest control is the scope you grant the Atera 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 Atera 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.

Source: skills/atera/README.md at commit 061ec05

Tools

0
SourceWeft started this package once in an isolated sandbox, without credentials, to list its tools. That failed: the package type cannot run in the sandbox.

Version history

5
  1. v0.1.8LatestOct 23, 2026
  2. v0.1.7Oct 23, 2026
  3. v0.1.6Oct 22, 2026
  4. v0.1.5Oct 16, 2026
  5. v0.1.4Sep 16, 2026

Score

40% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.