# How to connect DunSocial MCP to Copilot Studio and Microsoft Teams

> Add DunSocial as a Streamable MCP tool in Copilot Studio, test OAuth safely, then publish the agent for agency use in Microsoft Teams.

- Published: 2026-08-06
- Last updated: 2026-08-06
- Author: DunSocial
- Topics: mcp, how-to

---

If your agency already works in Microsoft 365, Copilot Studio can connect to an existing Streamable HTTP MCP server and make its tools available to an agent. That agent can then be published to Microsoft Teams and Microsoft 365 Copilot.

This is an administrator-led integration, not the same two-click flow as adding Claude or ChatGPT. Power Platform data policies, OAuth configuration and Teams distribution rules still apply.

Search phrases: DunSocial MCP Copilot Studio, social media agent Microsoft Teams, connect MCP server to Copilot, agency Teams social media agent, Copilot Studio MCP OAuth.

## What you will do

- Add the DunSocial server through Copilot Studio’s MCP onboarding wizard.
- Test the connection against a non-production client workspace.
- Publish the agent to yourself in Teams before broader agency distribution.

## Before you start

- An active DunSocial workspace with the intended social accounts already connected.
- An MCP client that supports Streamable HTTP and OAuth, such as Claude, ChatGPT, Cursor or Copilot Studio.
- A person who can review the final account, copy and time before publishing.
- Copilot Studio access, generative orchestration enabled, and permission to create connectors under your Power Platform data policies.

## Step by step

### 1. Create or open the agency agent

In Copilot Studio, open the agent’s Tools page, choose Add a tool → New tool → Model Context Protocol. Microsoft currently recommends its MCP onboarding wizard for existing servers.

### 2. Add the DunSocial server

Enter a clear name, description and `https://api.dunsocial.com/api/mcp`. Choose Streamable transport. Configure OAuth following the wizard and your tenant’s connector policy.

### 3. Test with read-only requests

Use a test workspace first. Confirm workspace identity, accounts and queue before testing draft creation. Copilot Studio dynamically discovers the tools exposed by the server.

### 4. Publish carefully to Teams

Publish the agent, add the Microsoft 365 and Teams channel, then install it only for yourself. Microsoft recommends personal testing before sharing the installation link or requesting organization-wide availability.

## Check before you finish

- The assistant names the correct DunSocial workspace and destination accounts.
- Every factual claim comes from the source material or saved workspace memory.
- The final action, timezone and returned post or draft IDs are visible.
- The agency documents which Teams users can access the agent and which DunSocial workspace its OAuth connection can change.
- A tenant administrator reviews Power Platform connector and data policies.

## Where to go next

Microsoft’s official setup references are learn.microsoft.com/microsoft-copilot-studio/mcp-add-existing-server-to-agent and publication-add-bot-to-microsoft-teams.

---

## About this document

This is the Markdown representation of https://www.dunsocial.com/blog/connect-dunsocial-mcp-to-copilot-studio-and-microsoft-teams. The HTML version of the same page is at the same URL. You can also request Markdown from any page by sending `Accept: text/markdown`.

Machine-readable summary of the whole site: https://www.dunsocial.com/llms.txt

## Company

- Product: DunSocial, https://www.dunsocial.com
- Legal entity: THISUX PRIVATE LIMITED, Chennai, Tamil Nadu, India
- Support: support@dunsocial.com
- Open the app: https://app.dunsocial.com/login