AI integrations · Microsoft Copilot
Microsoft Copilot

Run Manifestly from Microsoft 365 Copilot.

Manifestly's MCP server plugs into Copilot Studio as a tool. Build an agent once, publish it to Microsoft 365 Copilot and Teams, and your team can start runs, complete steps, reassign work, and author new SOPs — from the Microsoft 365 apps they already live in.

How to connect Have Copilot walk you through it
Endpoint
mcp.manifest.ly
Protocol
MCP · Streamable HTTP
Auth
OAuth 2.0 · dynamic registration
Setup
Copilot Studio · ~ 15 min
Why Copilot + Manifestly

Workflows where your team already works.

If your company runs on Microsoft 365, Copilot is already in Teams, Outlook, and Word. Add Manifestly as an MCP tool in Copilot Studio and Copilot becomes a workflow surface, not just a chat box: it can do the work, not just talk about it.

Build the agent once. Publish it to Teams and Microsoft 365 Copilot. Each user signs in with their own Manifestly account, so permissions, audit, and SSO behavior carry over cleanly. Already using our Teams app? This sits right alongside it.

  • Works with Copilot Studio agents and Microsoft 365 Copilot declarative agents
  • Native MCP tool — standard Streamable HTTP
  • OAuth 2.0 with dynamic client registration, scoped per user
  • Full read, write, and author surface
  • Every action attributed in the audit log

Have Copilot set itself up. Seriously.

Copy the prompt below, paste it into Microsoft 365 Copilot, and Copilot will read these pages, figure out your setup, and walk your maker or admin through the right path in Copilot Studio.

Copy & paste into Copilot
I want to connect Manifestly to Microsoft 365 Copilot using the Model Context Protocol so my team can run workflows by chatting with you.

Please:

1. Read https://www.manifest.ly/integrations/mcp-server and https://www.manifest.ly/ai-integrations/copilot so you understand exactly what Manifestly's MCP server does and how to add an MCP server as a tool in Copilot Studio.
2. Ask me whether I'm building the agent in Copilot Studio or with the Microsoft 365 Agents Toolkit in VS Code — the steps differ.
3. Walk me (or my admin) through adding Manifestly as a Model Context Protocol tool with server URL https://mcp.manifest.ly, using OAuth 2.0 with dynamic discovery, then publishing the agent to the Teams and Microsoft 365 Copilot channel.
4. Once I confirm we're connected, suggest three useful first prompts the team can try (e.g. "what's overdue across operations this week?", "start the new client onboarding workflow for Acme", "draft me a SOC2 evidence collection workflow and import it").
5. Remind me that every action you take via Manifestly is attributed to the human user in the audit log, scoped to that user's existing Manifestly permissions.

If your Copilot tenant doesn't have web content enabled, follow the manual setup steps below instead.

What you can ask

Three patterns that turn Copilot into a workflow surface.

Copilot's strength is sitting inside Teams, Outlook, and the rest of Microsoft 365. These three patterns are where most teams get the most value.

01 / Before the Teams meeting

Ask before your morning meeting.

Open Copilot in Teams. Ask what's overdue and who's stuck before you join the call. Pulls live data, scoped to your permissions.

For: managers · ops leads · team leads
Microsoft 365 Copilot · Manifestly connected
You
Ops sync starts in 10 min. What's overdue on the ops team this week?
Copilot
Pulling overdue assignments for the ops team.
→ list_my_assignments(team=ops, status=overdue)
5 overdue assignments across 4 runs:
• Sam — Q2 SOC2 evidence · "Collect access reviews" · 5d late
• Sam — Q2 SOC2 evidence · "Sign vendor questionnaire" · 3d late
• Priya — Acme onboarding · "Provision SSO" · 2d late
• Jordan — Acme onboarding · "Send welcome packet" · 1d late
• Priya — Northwind kickoff · "Schedule kickoff call" · 1d late
You
Reassign Sam's two to me and add a comment that I'm covering this week.
Copilot
Done. Both steps reassigned to you with the explanatory comment.
02 / In the flow

Run the workflow without leaving Outlook or Teams.

Start runs, complete steps, set due dates, capture data fields, leave comments — right from Copilot, while you're already on the email or thread that prompted the action.

For: anyone executing real work
Microsoft 365 Copilot · Manifestly connected
You
Start the client onboarding workflow for Northwind, mark step 1 complete, and assign the contract review to Priya.
Copilot
Starting the run, completing step 1, and assigning the contract review.
→ start_run_by_workflow_name("Client onboarding")
→ complete_run_step(run=14228, step=1)
→ assign_run_step_by_name(run=14228, step="Contract review", user="Priya")
✓ Run #14228 — "Northwind onboarding" started
✓ Step 1 "Create CRM record" — completed
✓ Step 4 "Contract review" — assigned to Priya Mehta, due Fri
You
Add a comment on step 7: "Northwind needs SOC2 type 2 — see RFP, page 14."
Copilot
Comment added on step 7. Anything else?
03 / The wow

Build Copilot Studio agents that run workflows.

In Copilot Studio, build a department-specific agent that talks to Manifestly directly — e.g. an "onboarding concierge" that starts the right run, assigns the right people, and posts to the right Teams channel automatically when a new client closes.

For: makers and ops architects building durable internal agents
Copilot Studio · Manifestly + Teams connected
You
Build an onboarding-concierge agent: when I say a client closed, start onboarding for them, assign the AE as run owner, and post a kickoff message in the CS channel.
Copilot
Drafting the agent. It will use the Manifestly tool to start runs and the Teams connector to post the kickoff message.
→ get_workflow_schema()
→ list_workflows(name~="onboarding")
→ publish_agent("Onboarding concierge")
✓ Agent published: "Onboarding concierge"
   Trigger: chat command "client closed: <name>"
   Actions: start "Client onboarding" run · assign AE · post Teams message
   Permissions: scoped to caller's Manifestly account
You
Client closed: Northwind. AE is Priya.
Manual setup

Two ways in. No code required for the first.

Copilot Studio adds MCP servers as tools with a wizard, and publishes the agent to Teams and Microsoft 365 Copilot. Developers can also wire Manifestly into a declarative agent with the Microsoft 365 Agents Toolkit. Both paths use the same endpoint.

Copilot Studio

Add Manifestly as a tool

  1. Open your agent in Copilot Studio and go to Tools.
  2. Select Add a tool → New tool → Model Context Protocol.
  3. Name it Manifestly, add a one-line description, and paste the server URL below.
  4. For authentication choose OAuth 2.0 → Dynamic discovery. No client ID or secret to paste.
  5. Select Create, create a new connection by signing in with your Manifestly account, then Add to agent.
  6. Publish the agent. Under Channels, open Teams and Microsoft 365 Copilot and make it available. Your admin may need to approve it for the tenant.
https://mcp.manifest.ly
Microsoft 365 Agents Toolkit

Declarative agent, for developers

  1. In VS Code with the Microsoft 365 Agents Toolkit, select Create a New Agent/App → Declarative Agent.
  2. Select Add an Action → Start with an MCP Server and enter the server URL below.
  3. Choose OAuth (with dynamic registration). The toolkit reads Manifestly's tools automatically.
  4. Sign in to Microsoft 365, then Provision to sideload it for testing.
  5. For rollout, an IT admin deploys the agent to users from the Microsoft 365 admin center.
https://mcp.manifest.ly
Good to know. Copilot Studio only supports Streamable HTTP for MCP, which is what Manifestly uses. Power Platform data policies that govern connectors also govern MCP tools. End users need a Microsoft 365 Copilot license to use the agent inside Copilot.

Need IAM details? The MCP server reference documents the OAuth flow, the available tools, and how permissions map from Manifestly to the connected agent.

Built right

Copilot can only do what the user can do.

Enterprise AI integrations have to be auditable. We built this to enterprise standards from day one.

— Auth
OAuth 2.0, no API keys to share.

Users sign in with their Manifestly account on first use. Microsoft never sees a long-lived secret, and admins never paste one.

— Permissions
Scoped per user.

Even when an agent is shared tenant-wide, each user only sees what their Manifestly account permits. Roles, departments, and assignments carry over.

— Audit trail
Every action attributed.

When Copilot completes a step, the audit log records the human user who asked — not a generic service account.

— Admin control
Revoke at the source.

Admins can block the agent or the connection tenant-wide from the Microsoft 365 admin center or Power Platform admin center. Users can revoke individually from their connected apps page.

Related

Not using Copilot? We have you covered.

Claude

Claude

Connect Manifestly to Claude.ai, Claude Desktop, and Claude Code. Learn how »
ChatGPT

ChatGPT

Connect Manifestly to ChatGPT Pro, Business, or Enterprise. Learn how »
Gemini

Gemini

Connect Manifestly to Gemini Enterprise and Agent Designer. Learn how »

Bring Manifestly to Microsoft 365 Copilot. Start free, or talk to us about your AI strategy.

With Manifestly, your team will Never Miss a Thing.

Start your free 14-day trial Schedule a demo »