> You are reading the Docusign Developer Documentation. For clean Markdown of any page, append .md to the page URL.
>
> Documentation indexes by section:
> - APIs and SDKs: https://docusign.docs.buildwithfern.com/docs/llms.txt
> - Platform 101: https://docusign.docs.buildwithfern.com/platform/llms.txt
> - Extension Apps: https://docusign.docs.buildwithfern.com/extension-apps/llms.txt
> - Docusign CLI: https://docusign.docs.buildwithfern.com/docusign-cli/llms.txt
>
> Authentication (OAuth, JWT Grant, M2M): https://docusign.docs.buildwithfern.com/platform/auth
> Webhooks and Connect: https://docusign.docs.buildwithfern.com/platform/webhooks
>
> OpenAPI specifications: https://docusign.docs.buildwithfern.com/openapi.json
> MCP server: https://docusign.docs.buildwithfern.com/_mcp/server

# Microsoft (Copilot Studio)

> Discover how to use the Docusign MCP Server to access APIs, trigger workflows using Microsoft (Copilot Studio)

Follow the steps below to configure your Docusign MCP server, starting with the required prerequisites and credentials.

## Prerequisites

Before connecting to the Docusign MCP server, you will need:

* A Docusign developer account. You can [create one](https://www.docusign.com/developers/sandbox) for free at the [Developer Center](/).
* Copilot Studio account – A Microsoft Copilot Studio plan.

## Connecting a Docusign Demo Account to Microsoft Copilot Studio

1. Open [Microsoft Copilot Studio](https://www.microsoft.com/en-us/microsoft-365-copilot/microsoft-copilot-studio)  .
2. Select **Sign in to Copilot Studio**.
3. Enter your corporate email address and login Microsoft Copilot Studio.
4. On the left navigation pane of the home page, select **Agents** and select **New agent**.
5. Enter a name for your agent. Ex.Docusign_MCP_Demo.
6. Select the three dots menu, and select **Settings**.
7. Under **AI  & behaviour > Orchestration** section, ensure **Allow other agents to connect** setting is enabled.

   ![Copilot-orchestration](/_fern-files/_img/b73478b904302ebef7cd612b1350405fe7b51486617b8d5b6da9d83d65bd88f6.webp)
8. Select **Done**.
9. On your agent’s home page, navigate to **Tools** and select **+** (Add a tool).
10. Select the **Model Context Protocol (MCP)** filter, and search for **Docusign MCP Demo.**
11. Select the Docusign connector named **Docusign MCP Server** under Docusign MCP Demo to add it to your agent.

    ![add-tool-copilot](/_fern-files/_img/6fb2fae8bbcdbdd5f26ede37a4d2d167435ce36a70148d2bc001cbb766965784.webp)
12. Select **Not Connected** > **Create new connection**.
13. (Optional) Enter a connection name.
14. Select **Create**.
15. Sign in to your Docusign Developer’s account (Docusign Demo account).
16. Select **Allow Access**.
17. Select **Add** to confirm the connection.
18. Select **Save**.
19. Select **Publish**.

The agent with MCP server connection is added at the end of this step.

## Run a test prompt

1. Select **Preview** tab on the agent's page.
2. Verify the MCP connection by entering a prompt such as: “Can you list the Docusign tools available to me?”

   **Note**: The wording of AI responses may differ between AI platforms, but the data and results should be the same.

![copilot-tools](/_fern-files/_img/bb53c3e936528183b131c0016f8b71e5dd65d2bd45e7a361d1a4581411224470.webp)

Your Copilot Studio agent is now configured to orchestrate Docusign agreement workflows using natural language.

## Remove MCP Configuration

1. In your agent homepage, navigate to **Agents**.
2. Select three dots under Docusign MCP Server tool.

   ![remove-copilot-config](/_fern-files/_img/a6e4ab26db1f9b6f7f9358c0e69f2cf9f1c52cf802bc7bde20aa05a95654021f.webp)
3. Select **Delete**.
4. Select **Delete** to confirm.

Your Docusign MCP server is now deleted in your agent.

## Next steps

* Try the Docusign MCP server with [GitHub (Copilot)](/platform/mcp-server/github-copilot) to explore its capabilities in Microsoft Visual Studio Code.
* Try the Docusign MCP server with [Anthropic (Claude)](/platform/mcp-server/anthropic-claude) to explore its capabilities.