Atera MCP by usefulapi

Reviewed 1h ago.

• tools: 20 tools scanned
• metadata: scanned

No findings.

Tools (20)

• atera_get_account

  Fetch the Atera account this key belongs to — company name, plan, country and timezone. A cheap way to confirm the key works. Atera: GET /api/v3/account.

• atera_list_customers

  List the customers (client companies) managed in Atera, paginated. Atera: GET /api/v3/customers.

• atera_get_customer

  Fetch a single customer by id — address, domain, phone, notes. Atera: GET /api/v3/customers/{customerId}.

• atera_list_agents

  List Atera agents — the managed machines — with online status, last seen, OS, hardware and logged-in user. Pass customer_id to list only one customer's devices. Atera: GET /api/v3/agents or GET /api/v3/agents/customer/{customerId}.

• atera_get_agent

  Fetch a single agent by its AgentID — full device inventory, online status, IPs, OS build and last reboot. Atera: GET /api/v3/agents/{agentId}.

• atera_find_agents_by_machine

  Find the agent(s) installed on a machine by its machine name, e.g. DESKTOP-4F2K9. Atera: GET /api/v3/agents/machine/{machineName}.

• atera_get_agent_patches

  List the Windows/OS patches on one device — either those still AVAILABLE (missing) or those already INSTALLED. Takes the device's DeviceGuid (from atera_list_agents / atera_get_agent), not the AgentID. Atera: GET /api/v3/agents/{deviceGuid}/available-patches or /installed-patches.

• atera_list_alerts

  List monitoring alerts (disk, CPU, availability, hardware...) with severity, device, customer and linked ticket. Filter by status. Atera: GET /api/v3/alerts.

• atera_list_tickets

  List helpdesk tickets with priority, status, type, end user, technician, SLA durations and last comments. Filter by customer and/or status. Atera: GET /api/v3/tickets.

• atera_get_ticket

  Fetch a single ticket by its TicketID. Atera: GET /api/v3/tickets/{ticketId}.

• atera_list_ticket_comments

  List the comment thread on one ticket — end-user and technician replies, with internal notes flagged. Atera: GET /api/v3/tickets/{ticketId}/comments.

• atera_list_ticket_work_hours

  List the time entries logged on one ticket — technician, start/end, billable, on-site, rate. Atera: GET /api/v3/tickets/{ticketId}/workhoursrecords.

• atera_list_contacts

  List end-user contacts, optionally searching by whole or partial email or phone number. Atera: GET /api/v3/contacts.

• atera_list_contracts

  List service contracts (retainer, block hours, hourly, remote monitoring...) with their rates and billing periods. Pass customer_id for one customer's contracts. Atera: GET /api/v3/contracts or GET /api/v3/contracts/customer/{customerId}.

• atera_list_kb_articles

  List knowledge-base articles with their product, keywords, section, category and ratings. Atera: GET /api/v3/knowledgebases.

• atera_create_ticket

  Open a new helpdesk ticket. Give either end_user_id (an existing contact's EndUserID) or all of end_user_first_name, end_user_last_name and end_user_email to create a new contact with it. Atera: POST /api/v3/tickets.

• atera_update_ticket

  Change a ticket's title, status, type, priority, impact or assigned technician. Only the fields you pass are sent. Atera: PUT /api/v3/tickets/{ticketId}.

• atera_add_ticket_comment

  Add a comment to a ticket, either as a technician (technician_id, with is_internal=true for a private note or false for a reply the end user sees) or on behalf of an end user (enduser_id). Atera: POST /api/v3/tickets/{ticketId}/comments.

• atera_create_contact

  Create a new end-user contact under an existing customer (give customer_id or customer_name). Atera: POST /api/v3/contacts.

• atera_resolve_alert

  Mark one monitoring alert as resolved. If the underlying condition persists, Atera raises it again on the next check. Atera: PUT /api/v3/alerts/{alertId}.