Connecting Microsoft Copilot

Add Clment to a Microsoft Copilot agent as an MCP server via Copilot Studio.

Updated 11 Aug 2026

Microsoft connects MCP (Model Context Protocol) servers through Copilot Studio — the agent builder — rather than directly in the Microsoft 365 Copilot chat. So this is a maker / admin path: someone with Copilot Studio access adds Clment to an agent, publishes it, and your team then uses it inside Microsoft 365 Copilot.

Before you start

You’ll need:

  • Copilot Studio access — a Microsoft 365 Copilot / Power Platform environment where you can build or edit agents.
  • A Clment account with at least one organization to authorize against.

Clment’s MCP server speaks the Streamable HTTP transport that Copilot Studio requires, so once it’s connected, Copilot Studio discovers all of Clment’s tools automatically.

1. Add the MCP server to an agent

In Copilot Studio:

  1. Open or create an agent.
  2. Go to Tools (called Actions in some tenants) → Add a tool → Model Context Protocol.
  3. In the MCP wizard, enter:
    • Server name — e.g. Clment.
    • Description — what it does, e.g. “Search, review, and redline contracts in Clment”.
    • Server URL — Clment’s MCP endpoint for your org’s data region: https://api-<your-region>.clment.com/v1/mcp (e.g. https://api-uk.clment.com/v1/mcp) (the exact URL is under Settings → Connect AI Agent in the Clment web app).

2. Authenticate

Copilot Studio connects to the MCP server with a bearer token, so the simplest, most portable path is:

  1. In the Clment web app, open Settings → Connect AI Agent and generate an MCP token (read-only or read + write).
  2. In the Copilot Studio MCP wizard, choose API key / bearer authentication and paste that token as the bearer.

If your tenant’s Copilot Studio supports OAuth for MCP servers, you can use that instead — Clment self-registers via Dynamic Client Registration — but the token approach works everywhere. Either way the connection is scoped to one org and attributed to you; revoke it any time from Settings → Connect AI Agent.

3. Publish

Publish the agent. It’s then available to your users wherever the agent is surfaced — including Microsoft 365 Copilot.

What your team can ask

Once published, users drive Clment from Microsoft 365 Copilot with plain requests, e.g.:

  • “List our contracts expiring in the next 90 days.”
  • “Summarise the limitation of liability in CLM-42 and how it compares to our standard.”
  • “For REV-12, accept the AI’s recommendations and generate the redline.”

If you issued a read + write token, the agent can also correct the details Clment extracted — the parties, the key dates and duration, or the financial terms:

  • “On CLM-42, change Pavel Kopytin’s role to Landlord and add PropNex Realty as a counterparty.”
  • “Set CLM-42’s effective date to 13 Oct 2018, expiry to 12 Oct 2020, and the duration to 2 years.”
  • “Update CLM-42’s financials to SGD 2,400 per month, payable monthly in advance.”

With a bearer token, every action — read or write — is attributed in Clment’s audit log to whoever generated the token, not to the individual Copilot user. The MCP skills catalog lists every read and write tool.

Notes

  • This is the maker path: end users don’t add Clment in the Copilot chat themselves; an admin/maker wires it into an agent once.
  • For an individual who just wants to drive Clment from an AI Agent, Claude Desktop or ChatGPT are the quicker, self-serve options.
  • Uploads run through the agent server-side, so the simplest route is to have it fetch a file link (Google Drive, SharePoint, or any HTTPS URL Clment can reach), or drag the file into the Clment web app. See Uploading contracts.

Troubleshooting

Switching to a different Clment account, org, or region, or the tool starts returning 401 / 403 — the fix depends on how you authenticated the MCP tool:

  • Bearer token (the default above) — there’s no stored sign-in to disconnect; the tool just holds a token. In the Clment web app open Settings → Connect AI Agent, generate a new token for the org and region you want, then in Copilot Studio edit the Clment tool’s authentication and paste the new token. Revoke the old token in Clment so it can’t be reused.
  • OAuth (only if your tenant uses it instead of a token) — if the consent screen says “Unknown or revoked client”, Copilot Studio is presenting a client identity registered against a different Clment environment or region. Remove the Clment MCP tool from the agent, then add it again so it re-registers against the right environment, and re-authorize. Editing the URL in place keeps the stale registration.

See also

Still have questions?

Instant article search