Copilot Studio e-signature MCP guide

Add e-signatures to a Microsoft Copilot Studio agent

Connect your Copilot Studio agent to the eSign 360 MCP server so it can prepare documents, send them for signature after confirmation, and chase unsigned documents.

Start free ›

In short

  • What it is: a remote MCP server for legal e-signatures, built into eSign 360 by 360 SaaS Pty Ltd, an Australian company.
  • Server address: https://admin.esign360.ai/mcp
  • Works with: Microsoft Copilot Studio agents. Copilot Studio supports remote MCP servers over the streamable HTTP transport, with OAuth 2.0 including dynamic discovery.
  • Price: AI assistant access is A$10 a month plus GST on the API plan, charged only while it is on. eSign 360 is free for Portal 360 customers, and the free tier is 5 documents a month.
  • Control: Copilot Studio asks before it sends, and every action is in your audit log.

How to connect eSign 360 to Microsoft Copilot Studio

Before you start:

  1. On the eSign 360 API plan, an administrator switches on AI assistant access in Settings. It is A$10 a month plus GST, charged only while it is on.
  2. You sign in with your own eSign 360 account, so the assistant acts as you and your permissions apply.

Then:

  1. Open your agent in Copilot Studio and go to its Tools page.
  2. Select Add a tool, then New tool, then Model Context Protocol.
  3. Enter a server name such as eSign 360, and a clear description such as “Prepare, send, track and remind documents for legal e-signature.” The description helps the agent decide when to use it.
  4. Enter the server URL https://admin.esign360.ai/mcp.
  5. Choose OAuth 2.0 and then Dynamic discovery. Select Create.
  6. Create a connection, sign in to eSign 360, press Allow, then select Add to agent.

Add an instruction to your agent such as “Always show me the signers and ask before sending a document for signature.” eSign 360 already separates preparing from sending, so the agent cannot send until you confirm.

What you can ask Microsoft Copilot Studio to do

AskWhat happens
“Send the attached NDA to sam@acme.com.”It prepares the document and shows you the signers. Nothing is emailed until you say yes.
“Which documents are still waiting?”It lists your documents and their status.
“Remind everyone who has not signed.”It sends reminders to the outstanding signers.
“Cancel the lease renewal.”It voids the document.
“Get me the signed copy.”It returns a link to the signed PDF or audit certificate that expires in 10 minutes.

The full list of tools is on the MCP server page. Signatures are legally recognised in Australia, and every signed document carries a tamper-evident certificate of completion. See are electronic signatures legal in Australia.

Questions about Microsoft Copilot Studio and eSign 360

Does Copilot Studio work with the eSign 360 MCP server?

Yes. Copilot Studio can add any remote MCP server that uses streamable HTTP and OAuth 2.0, which the eSign 360 server does.

Which authentication option should I choose?

Choose OAuth 2.0 with dynamic discovery. The eSign 360 server publishes its OAuth details and supports dynamic client registration, so there is nothing to copy by hand.

Can several people in my organisation use the same agent?

Yes. Each person creates their own connection and signs in to eSign 360 as themselves, so roles and audit logs stay per person.

Connect other assistants

Source for the Microsoft Copilot Studio steps: Microsoft Learn: connect an agent to an MCP server. Menus and labels can change, so check the vendor’s documentation if a step looks different.