Integrations
The Argus Archive MCP server gives Microsoft 365 Copilot, Copilot Studio agents and your own AI agents read-only access to archived conversations, transcripts and alerts, with Argus Archive permissions applied to every request.
Model Context Protocol (MCP) is the open standard AI assistants use to call tools. Argus Archive answers each call the same way it would answer the person or app behind it.
People sign in with their Microsoft work account. Each request acts as that person, and their Argus Archive role and data scope decide what comes back.
Background services and agents can connect through an Argus Archive app registration instead, with the app's own permissions.
Permissions are checked again on every request, so a role change applies from the next question. Transcripts and alerts need their own permissions, as they do in Argus Archive.
Every tool only reads. Nothing in the archive can be changed or deleted through MCP.
Results link back to the conversation or alert in Argus Archive, so people can check the original themselves.
Each completed tool call is recorded in the audit log, with the person or app that made it and what it asked for.
Agents pick the tool that fits the question, and Argus Archive returns only what the caller is allowed to see.
Lets an agent answer "my alerts" or "my conversations" without asking who you are.
Looks up people by name, to filter conversations and alerts by them.
Looks up groups by name, such as a desk or a team.
Finds the conversations most relevant to a question, with their transcripts.
Lists recent conversations, newest first, by date, people, groups, platform or keyword.
Fetches conversations by ID, such as the ones behind a set of alerts, with transcripts when allowed.
Lists alerts by status, severity, assignee, the person concerned, conversation, case or date.
Fetches alerts by ID, with the policy, the reason and the AI's findings.
A standard MCP server, so any client that speaks the protocol and signs in with Microsoft Entra ID can use it.
| Area | Details |
|---|---|
| Clients | Microsoft 365 Copilot, Copilot Studio agents, and other MCP clients that support Streamable HTTP and Microsoft Entra ID sign-in |
| Transport | MCP over Streamable HTTP |
| Sign-in for people | Microsoft Entra ID, found through OAuth protected resource metadata (RFC 9728); an Entra admin consents once |
| Sign-in for services | OAuth 2.0 client credentials, through an Argus Archive app registration |
| Results | Up to 20 per search or list; the last 90 days unless you ask for more, up to two years |
| Access | Read only |
| Audit | Every completed tool call, with the person or app that made it |
| Plans | Professional and Enterprise; each person who uses it needs a Professional or Reviewer named user license |
Microsoft 365 Copilot and Copilot Studio agents, and other MCP clients that support Streamable HTTP and Microsoft Entra ID sign-in.
People whose Argus Archive role includes the MCP permission. The Administrator and Supervisor roles have it by default, and an administrator can add it to other roles.
The same conversations, transcripts and alerts they can see in Argus Archive. Someone without the transcript permission gets no transcripts, and someone without the alerts permission gets no alerts.
Communications stay in Argus Archive. Each tool call returns only what was asked for, to someone allowed to see it. What an AI client does with an answer follows that client's own data policies.
No. Every tool only reads.
Yes. Searching by meaning uses your organization's AI credits, the same as searching in Argus Archive.
MCP gives AI agents a small set of read-only tools made for answering questions. The API gives your own applications the full range, including changes such as closing alerts or managing cases.
How governed communications fit into Microsoft 365 Copilot and your own agents.
Built by the people who created market-leading compliance recording and archiving products. Talk to us to see the MCP server with Microsoft 365 Copilot or your own agents, or to ask about a trial.
