Atera MCP
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Atera MCP show me open high-priority tickets"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Atera MCP for Codex
A standalone MCP server for the official Atera REST API.
The current vertical slice already includes:
MCP
stdiotransport with legacy/modern protocol negotiation;atera_health_checkandatera_capabilities;reading Customers, Agents, Tickets, and Alerts;
auto-selection of legacy
X-API-KEYor Bearer JWT, with a manual override;timeout, cancellation, rate limiting,
Retry-After, and retry of safe GETs;normalized errors and a managed mutation policy (writes and deletions are enabled by default).
The full catalog of all Atera endpoints is added after importing the current OpenAPI. Instructions: docs/OPENAPI_IMPORT.md. Reference baseline by domain: REFERENCE_COVERAGE.md.
The local tenant export has already been verified: OpenAPI 3.0.4, 81 paths, and 136 operations (69 GET, 35 POST, 19 PUT, 13 DELETE). The file is located in openapi-private/ and is intentionally excluded from git; on startup, the server publishes these operations as additional MCP tools.
Running
npm install
npm run typecheck
npm test
npm run build
npm run openapi:validate -- openapi-private/atera-openapi.jsonThe last command checks the imported tenant schema before restarting Codex. If the file does not exist yet, it exits with a clear diagnostic.
Variables are set through the environment; the template is in .env.example. At minimum, ATERA_API_TOKEN or legacy ATERA_API_KEY is required.
ATERA_API_TOKEN='…' npm startDo not add the secret to git or pass it in MCP tool arguments.
Related MCP server: Atera MCP Server
Connecting to Codex
In the Codex configuration, add the local server. On macOS/Linux, check the Node.js path with which node; on Windows, use where node:
[mcp_servers.atera]
command = "/opt/homebrew/bin/node"
args = ["/Users/vardahei/Documents/atera-mcp/dist/src/index.js"]
startup_timeout_sec = 30
[mcp_servers.atera.env]
ATERA_API_TOKEN = "<Atera token>"
ATERA_BASE_URL = "https://api.atera.com/api/v3"
ATERA_AUTH_MODE = "bearer"
ATERA_OPENAPI_PATH = "/Users/vardahei/Documents/atera-mcp/openapi-private/atera-openapi.json"
ATERA_WRITE_ENABLED = "true"
ATERA_ENABLE_DESTRUCTIVE_OPERATIONS = "true"Writes and deletions are enabled by default. You can disable them locally by setting the corresponding value to false. Capabilities are still limited by the Atera token's permissions.
Employee Installation from GitHub
An employee can give Codex the following task on any supported OS:
Установи Atera MCP из https://github.com/Oleksandr-Kliuiev/atera-mcp.
Определи мою ОС. На macOS/Linux выполни scripts/install-codex.sh, на Windows — scripts/install-codex.ps1.
Не запрашивай и не выводи мой Atera token в чат. После установки объясни, как добавить мой token локально в окружение MCP-сервера atera.For macOS/Linux, you can run locally:
git clone https://github.com/Oleksandr-Kliuiev/atera-mcp.git ~/.local/share/codex/atera-mcp
~/.local/share/codex/atera-mcp/scripts/install-codex.shFor Windows PowerShell:
$dir = Join-Path $HOME ".local\share\codex\atera-mcp"
git clone https://github.com/Oleksandr-Kliuiev/atera-mcp.git $dir
& "$dir\scripts\install-codex.ps1"Requirements for all OSes: Git, Node.js 20+, and an installed Codex CLI. On Windows, the script runs from PowerShell; if the execution policy prevents local scripts, use powershell -ExecutionPolicy Bypass -File .\scripts\install-codex.ps1.
The installer installs dependencies, builds the server, and registers stdio MCP in Codex. Each employee adds only their own ATERA_API_TOKEN; there is no shared token in the repository. By default, writes and deletions are enabled; if necessary, they can be disabled via ATERA_WRITE_ENABLED=false and ATERA_ENABLE_DESTRUCTIVE_OPERATIONS=false.
Available Tools
10 toolsatera_account_getGet Atera accountARead-onlyIdempotent
Get the authenticated Atera account context without exposing the API token.
Inputs: no named parameters.
atera_agents_getGet Atera agentARead-onlyIdempotent
Get one Atera agent by numeric agent ID.
Inputs: agentId (required).
atera_agents_listList Atera agentsARead-onlyIdempotent
List installed Atera agents, optionally filtered by customer.
Inputs: page, customerId, itemsInPage.
atera_alerts_listList Atera alertsBRead-onlyIdempotent
List Atera alerts with pagination.
Inputs: page, itemsInPage.
atera_capabilitiesAtera capabilitiesARead-onlyIdempotent
Show connector policy and the Atera domains covered by the endpoint catalog.
Inputs: no named parameters.
atera_customers_getGet Atera customerARead-onlyIdempotent
Get one customer by numeric Atera customer ID.
Inputs: customerId (required).
atera_customers_listList Atera customersBRead-onlyIdempotent
List customer records with Atera pagination.
Inputs: page, itemsInPage.
atera_health_checkAtera health checkARead-onlyIdempotent
Check Atera API connectivity and authentication without exposing the token.
Inputs: no named parameters.
atera_tickets_getGet Atera ticketARead-onlyIdempotent
Get one ticket by numeric ticket ID, including fields returned by Atera.
Inputs: ticketId (required).
atera_tickets_listList Atera ticketsARead-onlyIdempotent
List Atera tickets with pagination and optional status filter.
Inputs: page, itemsInPage, ticketStatus.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 10 tools
Each tool targets a distinct Atera resource or meta-information task. The health check, account context, and capabilities tools are descriptive enough that an agent can reliably distinguish them from the operational list/get tools.
Tool names consistently use the atera_ prefix and mostly follow an atera_<resource>_<action> pattern with list/get pairs. atera_health_check and atera_capabilities are minor exceptions because they do not follow the same resource/action structure.
Ten tools is well-scoped for an Atera connector: three meta/info tools plus list/get operations for customers, agents, and tickets, plus alerts listing. Each tool serves a clear purpose without unnecessary bloat.
The read-side surface covers the core Atera entities (customers, agents, tickets, alerts) with list and detail access for most resources. It lacks write/update/delete operations and an alerts-get detail tool, but this appears to be a deliberate read-only connector rather than a severe gap.
Maintenance
Related MCP Connectors
Accelo MCP server for ChatGPT, Claude and any AI agent: list tickets, reply to ticket, update ticket, log time, create task and create quote in your own Accelo account. Cotlet works in the account through your Cloud Browser, a real Chrome where you sign in to Accelo yourself; Cotlet does not store your password and you need no Accelo API key. About the official Accelo API: Accelo has a full REST API and a hosted MCP server, but the MCP server is built for questions about your data (checked 17 Oct 2026). The API covers companies, contacts, tickets, projects, tasks, activities, quotes and invoices, and you register an OAuth application under Configuration > API to use it. Setup and FAQ: https://cotlet.dev/integrations/accelo-api-mcp-server
Autotask MCP server for ChatGPT, Claude and any AI agent: search tickets, create ticket, update ticket, add ticket note, log time entry and find company in your own Autotask account. Cotlet works in the account through your Cloud Browser, a real Chrome where you sign in to Autotask yourself; Cotlet does not store your password and you need no Autotask API key. About the official Autotask API: Autotask has a full REST API, and Kaseya publishes an official Autotask MCP server that is still in alpha (checked 6 Nov 2026). Both run as an API-only user with an integration code, set up by an admin, and the MCP server supports Claude only. Setup and FAQ: https://cotlet.dev/integrations/autotask-api-mcp-server
AroFlo MCP server for ChatGPT, Claude and any AI agent: list tasks, create task, schedule technician, create final invoice, approve invoice and email invoice in your own AroFlo account. Cotlet works in the account through your Cloud Browser, a real Chrome where you sign in to AroFlo yourself; Cotlet does not store your password and you need no AroFlo API key. About the official AroFlo API: Yes, AroFlo has a REST API (checked 23 Oct 2026), but it is off by default and an account asks AroFlo support to enable it. Each request carries an HMAC-SHA512 signature, replies are XML unless you ask for JSON, and the API is capped at 2,000 calls a day. Setup and FAQ: https://cotlet.dev/integrations/aroflo-api-mcp-server
ConnectWise MCP server for ChatGPT, Claude and any AI agent: list tickets, read ticket notes, update ticket, add ticket note, log time entry and create ticket in your own ConnectWise account. Cotlet works in the account through your Cloud Browser, a real Chrome where you sign in to ConnectWise yourself; Cotlet does not store your password and you need no ConnectWise API key. About the official ConnectWise API: ConnectWise PSA, formerly ConnectWise Manage, has a REST API, but no documented ConnectWise-hosted MCP server (checked 5 Nov 2026). To use the API you register on the ConnectWise Developer Network, get a ClientId and create an API member with a public and a private key. Setup and FAQ: https://cotlet.dev/integrations/connectwise-api-mcp-server
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceEnables Codex to safely interact with Bitwarden vault status, metadata, generated logins, folders, and approved automation profiles while preventing direct secret access.MIT
- AlicenseNot gradedqualityBmaintenanceLets an AI agent read an MSP's customers, monitored agents, alerts, tickets and contacts through the Atera RMM/PSA v3 API, and, on explicit request, create customers and tickets, update ticket fields and add ticket comments. It runs statelessly over MCP Streamable HTTP with a per-request API key and exposes all 20 list, get and write tools from the first tools/list call.Apache 2.0
- AlicenseCqualityBmaintenanceEnables interaction with the Atera RMM/PSA API v3 for managing tickets, customers, contacts, agents, alerts, contracts, knowledge base, billing, custom fields, network devices, departments, and rates. It exposes 47 tools with read-only defaults and optional write or delete access.3237 npmMIT
- AlicenseAqualityBmaintenanceEnables AI assistants to triage an Atera help desk by ranking open tickets with plain reasons, summarizing site health and alerts, and producing a one-call morning brief. It redacts personal data, fences user-written text as untrusted, and stays read-only unless writes are explicitly enabled.6MIT