# Kiteworks MCP in Copilot Studio — Setup Guide

> Connect the Kiteworks MCP Server to Microsoft Copilot Studio as a Model Context Protocol tool. Deploy the Remote HTTPS server, register the callback URL, and authenticate an agent with OAuth 2.0 dynamic discovery.

Kiteworks MCP

# Kiteworks MCP in Microsoft Copilot Studio

Connect the Kiteworks MCP Server to Microsoft Copilot Studio as a Model Context Protocol tool, so an agent can work with Kiteworks data. Copilot Studio connects to the Kiteworks **Remote HTTPS** server over OAuth 2.0.

> The flow uses OAuth 2.0 with **dynamic discovery**, so you do not enter a client ID or secret by hand. You will need privileges to create tools and agents in Copilot Studio, plus Kiteworks Admin Portal access. Microsoft's reference: [Setup and connect to MCP Server ↗](https://learn.microsoft.com/en-us/power-pages/configure/mcp-connect-clients).

## Prepare the Kiteworks MCP Server

Before you open Copilot Studio, deploy the Kiteworks Remote HTTPS server and register its OAuth callback URL. All three steps are detailed in the [Installation & Setup guide](mcp-installation-setup.html).

1. **Configure MCP in the Kiteworks Admin Portal.** Enable Kiteworks MCP in the Admin Portal console. See [Configure MCP in Admin Portal](mcp-installation-setup.html#pdn-plugin).
2. **Deploy the Remote HTTPS server.** Stand up the centralized Remote HTTPS MCP Server that Copilot Studio will connect to. See [Remote HTTPS Server](mcp-installation-setup.html#remote-https).
3. **Add the callback URL to the MCP configuration.** Register the callback (redirect) URL of your MCP deployment in the Admin Portal so the OAuth flow can complete for remote clients. Note your server's base URL — you register it in Copilot Studio with `/mcp` appended.

## Create the MCP Tool in Copilot Studio

Register the Kiteworks MCP Server as a reusable Model Context Protocol tool. You create the tool once, then add it to any agent that should work with Kiteworks.

1. **Sign in to Copilot Studio.** Go to [copilotstudio.microsoft.com ↗](https://copilotstudio.microsoft.com/) and sign in with an account that has privileges to create tools and agents.
2. **Open Tools and start a new tool.** In the left navigation, select **Tools**, then select **New tool**.
3. **Choose Model Context Protocol.** Select **Model Context Protocol** as the tool type.
4. **Name the tool.** Enter **Kiteworks MCP** as the server name.
5. **Enter the server URL.** For **Server URL**, enter the URL of your Remote HTTPS server ending in `/mcp` (for example `https://your.mcp.domain/mcp`).
6. **Choose OAuth 2.0.** Under **Authentication**, select **OAuth 2.0**.
7. **Keep dynamic discovery enabled.** Leave the **Dynamic discovery** option enabled. Copilot Studio then discovers the Kiteworks authorization and token endpoints automatically — there is no need to enter a client ID or secret manually.
8. **Create the tool.** Select **Create**. The Kiteworks MCP tool is now available to add to agents.

> The Kiteworks MCP tool is registered. Next, add it to an agent and authenticate the connection.

## Add the Tool to an Agent

Create an agent and attach the Kiteworks MCP tool. The connection you create determines which Kiteworks account the agent acts as — every operation the agent performs runs with that account's permissions.

1. **Create an agent.** In the left navigation, select **Agents**, then **Create agent**, and complete the agent details.
2. **Add the Kiteworks MCP tool.** Open the agent's **Tools**, select **Add a tool**, and choose **Kiteworks MCP**.
3. **Create a new connection and authenticate.** Select **Create new connection**, then sign in with the Kiteworks account you want the agent to interact from. Copilot Studio uses the dynamic-discovery OAuth flow to complete authentication.
4. **Choose whose credentials the agent uses.** In the tool's authentication settings, set **Credentials to use**. > **Recommended: End user credentials.** Each person authenticates with their own Kiteworks account, so the MCP Server enforces that user's own permissions for least privilege. The alternative, **Maker-provided credentials**, runs the agent as the one account that created the connection for everyone.

> Your Copilot Studio agent is now connected to Kiteworks. It can use the Kiteworks MCP tools to search, read, and manage data on behalf of the connected account. Publish and share the agent from Copilot Studio when you are ready to roll it out to users.

## Next Steps

With the Kiteworks MCP tool connected to your agent, explore what you can do with it:

- [Usage Examples ↗](https://github.com/kiteworks/mcp/blob/main/docs/USAGE_EXAMPLES.md) — Detailed examples including Compliance Review with Forms, Sensitive Data Audit, and Project Handover workflows
- [Available MCP Tools ↗](https://github.com/kiteworks/mcp/blob/main/docs/AVAILABLE_TOOLS.md) — Full list of tools exposed by the MCP Server