Atera MCP server

What the model can do

Atera RMM and helpdesk: tickets with status, priority, customer, end user, technician and SLA dates, a ticket's comments, customers, contacts, managed devices (agents) with online state and OS, and monitoring alerts. Can add an internal note or a public reply to a ticket, open, update or delete a ticket, resolve an alert, create and update customers and contacts, and remove an agent, when asked.

Reads

• atera_ticketsAtera helpdesk tickets, newest first: number, title, status, priority, impact, type, customer, end user, technician…
• atera_ticketOne Atera ticket with its first description and its most recent comments (who, when, internal or not), each cut short.
• atera_customersAtera customers (the organisations an MSP supports): name, domain, city, country, created and last modified.
• atera_contactsAtera contacts (end users at customers): name, email, job title, customer, and whether they are the customer's main contact.
• atera_agentsDevices managed by Atera agents: agent and machine name, customer, folder, online or offline, last seen, OS and version, device type, last reboot.
• atera_alertsAtera monitoring alerts: title, severity, category, device, customer, when raised, archived or not, and the ticket it became if any.

Acts, when you ask

These change something in Atera. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.

• atera_add_internal_noteAdd an internal technician note to an Atera ticket.
• atera_create_ticketOpen a new ticket in Atera for an existing contact (find the contact id with atera_contacts).
• atera_update_ticketChange one Atera ticket's title, status (Open, Pending, Resolved, Closed), type, priority, impact or assigned technician.
• atera_reply_to_ticketPost a public technician reply on an Atera ticket.
• atera_resolve_alertResolve one Atera monitoring alert (find it with atera_alerts).
• atera_create_customerCreate a customer (an organisation the MSP supports) in Atera.
• atera_update_customerUpdate one Atera customer's name, domain, business number, address, phone or notes.
• atera_create_contactCreate a contact (an end user) for an existing Atera customer (find the customer id with atera_customers).
• atera_update_contactUpdate one Atera contact's name, job title, phone numbers, whether they are the customer's main contact, or ignore mode…
• atera_delete_ticketPermanently delete one Atera ticket with its comments and history, for everyone.
• atera_delete_agentPermanently remove one agent (a managed device) from Atera: monitoring, alerts and remote access for that device stop…

Connect it

First connect Atera on Dashboard → Connections, then add Memtro to your client once. The Atera tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Atera connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

• › What's open for Acme in Atera?
• › Which of Northwind's devices are offline?
• › Are there any open critical alerts for BigCo?
• › Add an internal note to the BigCo printer ticket saying the replacement drum is on order.
• › Reply to the Northwind VPN ticket that the fix is live and set it to Resolved.

Questions

Is this an official Atera MCP server?

No. It is Memtro's MCP server with Memtro's Atera connector behind it: the connector reads Atera through its API with the credentials you connect on Dashboard → Connections, and Atera publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.

What does it cost?

Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.

Can it change anything in Atera?

Only when you ask, and only what it has been granted: add an internal technician note to an Atera ticket (never shown to the end user); open a new Atera ticket for an existing contact; change an Atera ticket's title, status, type, priority, impact or technician; reply to an Atera ticket as a technician (visible to the end user); resolve an Atera alert; create an Atera customer; update an Atera customer's details; create an Atera contact for a customer; update an Atera contact; delete an Atera ticket; delete an Atera agent (remove a managed device). Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.

Which clients work?

Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

Other MCP servers · Support

• Help Scout MCP server
• Zendesk MCP server
• Intercom MCP server
• Freshdesk MCP server
• Front MCP server
• Zoho Desk MCP server