Connect Copilot Studio

Microsoft Copilot Studio adds MCP servers as tools on an agent. It connects to them from Microsoft’s cloud over the Streamable HTTP transport, which is what the Scrive MCP uses, so no bridge or self-hosting is needed.

Surface	Connection	Status
Copilot Studio agent	MCP tool, OAuth 2.0	Supported, see below

You need OAuth client credentials from Scrive

Copilot Studio’s automatic OAuth options (Dynamic discovery and Dynamic) need dynamic client registration, which Scrive’s authorization server does not offer. Use the Manual option instead, with a client ID and client secret that Scrive issues for your organisation. Request the client before you start; once the wizard shows its callback URL, send that to Scrive so it can be registered on the client. See When you need a client ID and secret.

What you need

Requirement	Why
Permission to add tools to an agent and create Power Platform connections	The MCP wizard creates a custom connector in your environment. Data policies on Power Platform connectors apply to it too
An OAuth client ID and secret issued by Scrive	Copilot Studio authenticates users through Scrive’s authorization server with these
Each user’s own Scrive account	Connections use user authentication, so every user signs in to Scrive themselves and the agent acts as them

Add the tool

1. Open your agent and go to the Tools page. Select Add a tool → New tool → Model Context Protocol.

2. Fill in Server name (Scrive), Server description (for example “Find, prepare, send and follow up on Scrive documents”) and Server URL (https://mcp.scrive.com/mcp). The orchestrator uses the description to decide when to call the server.

3. Under authentication choose OAuth 2.0, set Type to Manual and fill in:

   Field	Value
   Client ID, Client secret	Issued by Scrive
   Authorization URL	https://oauth2.scrive.com/oauth2/auth
   Token URL template	https://oauth2.scrive.com/oauth2/token
   Refresh URL	https://oauth2.scrive.com/oauth2/token
   Scopes	full

   Select Create.

4. The wizard now shows a callback URL. Copy it and make sure it is registered on the Scrive OAuth client, then select Next.

5. In the Add tool dialog choose Create a new connection, sign in to Scrive when the browser window opens, then select Add to agent.

6. Test in the agent’s chat:

   List the Scrive documents that are still pending signature.

   The Scrive tools appear under the new MCP tool. Keep the agent’s confirmation on for start_signing, remind_document, cancel_document, start_flow and delete_flow_draft.

Agents in the new experience

Agents built in Copilot Studio’s new experience (the GitHub Copilot harness, in preview) add MCP servers from the Build tab instead. Open Tools, select Add next to the search bar, then Model Context Protocol (MCP). Enter the same name, description and server URL, choose OAuth 2.0 with the values above, select Add, review the Scrive tools and select Save. Test from the Preview tab.

File uploads

create_document, set_file and add_document_to_draft open a file picker panel on clients that support MCP Apps. Copilot Studio agents do not render such panels, so uploads from the chat are not available there. Documents can still be created from templates with create_from_template, and everything else works.

Remove

Delete the tool from the agent’s Tools page and delete the connection and custom connector in Power Apps. See Revoke access.

---

Related reading

• Microsoft’s documentation: Connect your agent to an existing MCP server, Add an MCP server in the new experience
• Any MCP client
• Access & permissions