Connect Atera to Microsoft Copilot via MCP

💡 No install? Use cloud.anythingmcp.com directly. Sign in, click Connectors → Atera, paste your credentials, mint an MCP API key and you're done. No Docker, no git clone, no local server.

Atera + Microsoft Copilot

Atera RMM and help desk: customers, contacts, monitored agents with hardware and patches, agentless devices, alerts, tickets with comments and work hours, contracts and knowledge base. Atera REST API v3 with an API token.

Prerequisites

See the full setup instructions baked into the connector (visible in the in-app store when you select the connector). The required environment variables for this connector are:

ATERA_API_KEY

Step 1 — Get credentials

1. In Atera open Admin → Data management → API. Only Atera admins see this page.
2. Click New token and choose an expiration date (at most one year), the IP addresses allowed to use the token (keep Allow all, or add the outbound address of your AnythingMCP server) and the permissions: Full access, or Custom access with Read on the domains the AI should see, plus Write on Tickets and Alerts if you want the write tools.
3. Copy the token into ATERA_API_KEY right away: Atera shows it only once. The connector sends it as a Bearer token.
4. Install the connector and run atera_list_customers. It lists your client companies with the CustomerID most other tools need.

Use a token, not a legacy key: older accounts may still hold a static API key (a short key that does not start with eyJ). Atera is replacing those with tokens and this connector only sends the Bearer form, so create a new token.

Token expiry: a token lasts at most one year. Atera notifies admins 7 days and 1 day before it expires; then create a new token and paste it into ATERA_API_KEY.

Who sees what: with Full access the token has the rights of the whole Atera account, so anyone using this connector can read every customer, device and ticket. Custom access limits the AI to the domains you grant.

What it reads: customers and their contacts, monitored agents with their full hardware inventory and installed or missing patches, agentless devices (ping, SNMP, HTTP, TCP), alerts, tickets with comments, work hours and billable time, contracts and the knowledge base. Good starting points are atera_list_tickets, atera_list_customer_agents and atera_list_alerts with the status Open.

Confirm first: the AI can create and update tickets (atera_create_ticket, atera_update_ticket), add comments (atera_add_technician_comment, atera_add_enduser_comment) and resolve alerts (atera_resolve_alert). A technician comment that is not internal is emailed to the end user, so the AI shows you the text before it posts. Ticket status names are free text in Atera, so it reads them from existing tickets.

Limits: Atera allows about 700 requests per minute per account. Lists come in pages of at most 50 items, so on large accounts the AI filters by customer or status and uses atera_list_modified_tickets for recent changes instead of paging through every ticket.

Deleting customers, contacts, agents or tickets is not offered, and patches are only listed, not installed.

Step 2 — Install the adapter

curl -fsSL https://raw.githubusercontent.com/HelpCode-ai/anythingmcp/main/docker-compose.quickstart.yml -o docker-compose.yml
printf 'JWT_SECRET=%s\nENCRYPTION_KEY=%s\n' "$(openssl rand -hex 32)" "$(openssl rand -hex 32)" > .env
docker compose up -d

Step 3 — Add the connector in Microsoft Copilot

Your server URL: in AnythingMCP, open MCP Servers → the server this connector is on, and copy its URL (https://cloud.anythingmcp.com/mcp/…). Use it wherever this guide shows YOUR_SERVER_ID.

Microsoft Copilot uses MCP servers through agents built in Copilot Studio: you add AnythingMCP to an agent as a tool, then publish the agent to Microsoft 365 Copilot and Teams. Copilot Studio connects from Microsoft's cloud over Streamable HTTP, which AnythingMCP supports.

1. In Copilot Studio, open your agent (or create one), go to Tools and choose Add a tool → New tool → Model Context Protocol.
2. Enter a Server name (for example AnythingMCP), a Server description that says what the connector does, and the Server URL https://cloud.anythingmcp.com/mcp/YOUR_SERVER_ID. Copilot Studio uses the description to decide when to call the server.
3. Under authentication, choose API key, set Type to Header and the header name to X-API-Key, then select Create.
4. In Add tool, choose Create a new connection, paste an MCP API key from AnythingMCP (MCP Servers → your server → API keys) and select Add to agent.
5. Try it in the agent's Test pane: ask for something that needs the Atera tools.
6. Select Publish, then Channels → Microsoft 365 and Microsoft Teams, keep Make agent available in Microsoft Copilot selected and choose Add channel. See agent in Teams installs it for you; in Microsoft 365 Copilot, type @ and pick the agent.

Prefer per-user sign-in? Choose OAuth 2.0 → Dynamic discovery instead of an API key: each user then signs in to AnythingMCP the first time the agent calls it.

Self-hosting? Use your instance's public HTTPS address instead of https://cloud.anythingmcp.com. Copilot Studio connects from Microsoft's cloud, so localhost does not work.

Available tools

Example prompts

• "Which critical alerts are still open right now, and on which customers' machines?"
• "Show me the open tickets of the customer Northwind with their technician and SLA due date."
• "How many billable hours did we log on tickets closed last month, per customer?"
• "Draft a reply to the end user on ticket 1234 and show it to me before you post it."

FAQ

Which Copilot is this for? Microsoft 365 Copilot at work, through agents built in Copilot Studio. The Microsoft Copilot app for personal accounts has no option to add your own MCP server.

What do I need? A work account with access to Copilot Studio (a license or a trial) to build the agent. People who use it in Microsoft 365 Copilot or Teams need access to the agent: share it with them, or ask an admin to publish it to the organization. If your organization applies data policies to Power Platform connectors, they cover MCP servers too.

The agent doesn't call the tools. Check that the header name is exactly X-API-Key and that the key belongs to the same MCP server as the URL, and make the server description specific: Copilot Studio uses it to decide when to call the server. Publish the agent again after each change; in an open chat, type "start over" to get the new version.

Next steps

• Connector landing page
• Connect to Claude
• Connect to ChatGPT
• Connect to Cursor
• Connect to Gemini
• Connect to Meta Muse