Use Reynforce in Copilot Studio

Last updated 21 October 2026

Add your workspace's address to a Copilot Studio agent as a Model Context Protocol tool. Give the agent its own key, or have each person sign in with their work account; neither needs a Microsoft listing.

Not tried end to end yet. Neither way has been run in Copilot Studio. The sign-in way also waits on the fix for the problem Claude met on 20 October 2026. This page will say so when each has worked once.

Which way to choose

	An agent key	Each person signs in
Who it acts as	the agent, which is what the record names	the person who signed in
What it can do	search the register, and check an action against the mandate	the same, plus propose, accept, own, confirm and contest lines
What you need	a key issued on your workspace's keys screen	each person a member of your workspace
Works today	should; untested	waits on our sign-in fix

An agent key never shows the writing tools. Accepting a line, owning one, confirming one and contesting one are a person's acts, so a key cannot do them whatever it is plugged into.

What you need first

A Reynforce workspace. Its MCP address is on your workspace's Settings page and looks like https://app.reynforce.com/t/<your workspace>/mcp.
A Copilot Studio agent you can edit.
For the key way: an owner issues a key for this agent on your workspace's keys screen. It is shown once. Give each Copilot Studio agent its own key, so the record says which one acted.

Add it

Open your agent in Copilot Studio and go to its Tools page.
Select Add a tool, then New tool, then Model Context Protocol.
Fill in Server name (Reynforce), Server description and Server URL (your workspace's MCP address). The agent reads the description to decide when to call us, so say what it is for, for example: "Search what our company stands behind before answering a buyer, and check a discount, date or term against our agent mandate before offering it."
Choose the authentication type, below.
In Add tool, select Create a new connection, then Add to agent.

With an agent key

Choose API key.
Set Type to Header, and the header name to Authorization.
Select Create.
When the connection asks for the key, enter Bearer followed by the key, with one space between them.

Why Bearer : our door reads the key from a standard Authorization: Bearer <key> header. Microsoft's page does not say whether Copilot Studio adds the word itself. If the connection is refused with the word, try it once without, and tell us which worked.

Choose OAuth 2.0, and Type Dynamic discovery.
Select Create, then Next.
Each person who uses the agent signs in with their work account, the one your workspace knows.

If it does not work

What you see	What it means	What to do
The connection is refused with a `401`	the key did not arrive in the form we read	check the `Bearer` prefix, above. Then check the key was not revoked
Still a `401`, or no Reynforce tools, with the prefix right	the key belongs to a different workspace from the address	the workspace in the address and the workspace that issued the key must be the same
Only two tools appear	you connected with an agent key	expected. The other five are a person's
The sign-in page refuses you	the account you signed in with is not a member of this workspace	ask whoever runs your workspace to add you
A tool answers that a line is unusable	the line is overdue, has no owner, or is contested	not an error. Tell the buyer you are checking, and ask the owner

Anything else: Get help.

What Copilot Studio sends us

Only what each tool needs: the search words, the action described, and the line acted on. Not the conversation. What we hold has the full account. If your organisation has a data policy for Power Platform connectors, Microsoft's page says it covers this tool as well.

Copilot Studio's steps and labels are from Microsoft's page Connect your agent to an existing Model Context Protocol (MCP) server, read on 21 October 2026. If a label has changed, that page is the one to trust.