How Do I Connect WorkStory MCP to Microsoft Copilot?

Choose the Copilot setup that matches your workspace

Microsoft 365 Copilot and GitHub Copilot connect to WorkStory differently. Both use the same WorkStory MCP endpoint: https://app.workstory.team/mcp.

Microsoft 365 Copilot

This is a Copilot Studio maker or admin setup.

1. In Copilot Studio, create or open an agent—for example, “WorkStory.”
2. Go to Tools → Add a tool → Model Context Protocol. Add https://app.workstory.team/mcp and select OAuth sign-in so each person connects with their own WorkStory account.
3. Under Channels, enable Microsoft 365 Copilot and publish the agent. Your tenant may require admin approval.
4. Open the WorkStory agent in Copilot. The first time, sign in to WorkStory and approve access.

GitHub Copilot in VS Code

1. Open the Command Palette and run MCP: Add Server. Choose HTTP and enter the endpoint—or edit .vscode/mcp.json.

{
 "servers": {
   "workstory": {
     "type": "http",
     "url": "https://app.workstory.team/mcp"
   }
 }
}

2. Start the server, sign in to WorkStory, and approve access.
3. Switch Copilot Chat to Agent mode. Then ask normally, mentioning WorkStory, a person, team, or review cycle when helpful.

Permissions and control

WorkStory respects your existing access rules. Everyday questions are read-only, and feedback requests require approval before they are sent.

See Claude, ChatGPT and Codex, Gemini, or the MCP overview.

‍