Atera MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ATERA_API_KEY | No | Legacy API key for Atera (X-API-KEY). Required if ATERA_API_TOKEN is not provided. | |
| ATERA_BASE_URL | No | Base URL of the Atera API. Default: https://api.atera.com/api/v3 | |
| ATERA_API_TOKEN | No | API token for Atera (Bearer JWT). Required if ATERA_API_KEY is not provided. | |
| ATERA_AUTH_MODE | No | Authentication mode override: 'bearer' or 'legacy'. Defaults to auto-detection. | |
| ATERA_OPENAPI_PATH | No | Path to a local OpenAPI file to expose additional Atera operations as MCP tools. | |
| ATERA_WRITE_ENABLED | No | Whether write operations (POST/PUT) are enabled. Default: true. | |
| ATERA_ENABLE_DESTRUCTIVE_OPERATIONS | No | Whether destructive operations (DELETE) are enabled. Default: true. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| atera_health_checkA | Check Atera API connectivity and authentication without exposing the token. |
| atera_account_getA | Get the authenticated Atera account context without exposing the API token. |
| atera_capabilitiesA | Show connector policy and the Atera domains covered by the endpoint catalog. |
| atera_customers_listB | List customer records with Atera pagination. |
| atera_customers_getA | Get one customer by numeric Atera customer ID. |
| atera_agents_listA | List installed Atera agents, optionally filtered by customer. |
| atera_agents_getA | Get one Atera agent by numeric agent ID. |
| atera_tickets_listA | List Atera tickets with pagination and optional status filter. |
| atera_tickets_getA | Get one ticket by numeric ticket ID, including fields returned by Atera. |
| atera_alerts_listB | List Atera alerts with pagination. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.