# io.github.WYRE-AI/atera-mcp MCP server for Atera RMM — customers, tickets, and more. - **Type:** MCP server - **Trust:** 60/100 (B), scored on the content rubric - **Verification:** community-indexed — nobody has claimed this listing - **Version:** 1.5.10 - **Author:** io.github.WYRE-AI - **License:** Unknown - **Source:** https://github.com/WYRE-AI/atera-mcp ## Trust 60/100 (B), scored on the content rubric - Publisher verified: no - Install scripts: nothing suspicious found - Prompt-injection scan: clean - Obfuscation scan: clean - Evidence age: 1 day ## Security scan - **Status:** clean - **Scanned:** 2026-09-24T22:21:14.522Z - **Version scanned:** HEAD - **CVEs:** no coverage — this entry has no package coordinates to query OSV against, so "no known CVEs" is NOT asserted for it. ## Tools 20 declared. Statically extracted from the shipped source — a floor on the surface, not a census. - `atera_navigate` — Navigate to a specific domain in Atera. Call this first to select which area you want to work with. After navigation, domain-specific tools will be available. - `atera_back` — Return to domain selection. Use this to switch to a different area of Atera. - `atera_agents_list` — List agents (managed devices/endpoints) in Atera. Agents include servers, workstations, and Macs with the Atera agent installed. Returns device info including O - `atera_agents_get` — Get detailed information about a specific agent (device) by its ID. Returns full device profile including OS, hardware specs, and current status. - `atera_agents_get_by_machine` — Get agent information by machine name. Useful when you know the computer name but not the agent ID. - `atera_alerts_list` — List alerts from monitored devices in Atera. Alerts indicate issues detected by monitoring thresholds on agents and devices. - `atera_alerts_get` — Get detailed information about a specific alert by its ID. Returns full alert details including source, severity, and related device/agent info. - `atera_alerts_by_agent` — List alerts for a specific agent (device). Useful for troubleshooting issues on a particular machine. - `atera_alerts_by_device` — List alerts for a specific device (SNMP, HTTP, or TCP monitor). Useful for checking network device health. - `atera_contacts_list` — List contacts across all customers in Atera. Contacts are people associated with customer companies who may submit tickets or receive communications. - `atera_contacts_get` — Get detailed information about a specific contact by their ID. Returns full contact profile including customer association and contact details. - `atera_contacts_by_customer` — List contacts for a specific customer. Useful for finding who to contact at a particular company. - `atera_customers_list` — List customers (companies) in Atera with pagination. Returns customer details including name, address, contact info, and primary contact. - `atera_customers_get` — Get detailed information about a specific customer by their ID. Returns full customer profile including primary contact. - `atera_customers_create` — Create a new customer (company) in Atera. Only CustomerName is required, all other fields are optional. - `atera_tickets_list` — List tickets in Atera with optional filters. Returns ticket details including status, priority, customer, technician assignment, and SLA information. - `atera_tickets_get` — Get detailed information about a specific ticket by its ID. Returns full ticket details including comments, work hours, and billing info. - `atera_tickets_create` — Create a new ticket in Atera. TicketTitle is required, can optionally set priority, status, type, and assignment. - `atera_tickets_update` — Update an existing ticket in Atera. Only specify the fields you want to change. - `atera_tickets_add_comment` — Add a comment to a ticket. Comments are internal (hidden from the end user) by default; set isInternal to false only when the comment should be visible to the e ## Install This entry has no npm package and no hosted endpoint, so there is nothing for an MCP client to launch or connect to. It is indexed as source only. ## Blast radius Contained to moderate — no package coordinates and no declared endpoint — Forge cannot tell where this would run or whose authority it would borrow. Known so far: holds an api key; read-only tool surface. - Floor 13, ceiling 25 (tier: unknown) - `unknown` means the floor and ceiling land in different bands — not measured enough to name one. It does not mean low. - This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score. ## Machine-readable views of this entry - Signed JSON: https://forgeregistry.com/api/v1/packages/io.github.WYRE-AI%2Fatera-mcp - Install plan: https://forgeregistry.com/api/v1/packages/io.github.WYRE-AI%2Fatera-mcp/install-plan - Alternatives: https://forgeregistry.com/api/v1/alternatives/io.github.WYRE-AI%2Fatera-mcp - HTML page: https://forgeregistry.com/registry/io.github.WYRE-AI%2Fatera-mcp - MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan` ## About this document Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.