WorkStory MCP · Microsoft Copilot

Connect WorkStory to Microsoft Copilot.

Bring WorkStory feedback, reviews, and review cycles into Microsoft 365 Copilot or GitHub Copilot, and ask about them in plain language.

✓ Your company only✓ Your permissions only✓ Feedback requests need approval
WorkStory
+
Microsoft CopilotMicrosoft Copilot
Microsoft Copilot● WorkStory connected
Which managers on my team have recurring negative feedback signals this quarter, and what are the themes?
Two managers show a repeated pattern in the WorkStory feedback you can access:
Delegation
16
Meeting follow-through
13
Clarity of priorities
9
Connect it

Pick the Copilot you use.

"Copilot" covers two different products, and each connects to WorkStory a different way. Find yours below, then follow that card.

Microsoft 365 Copilot

For: teams using Copilot inside Microsoft 365. WorkStory is added once in Copilot Studio and shared as an agent — this is a maker or admin step.

1
Open Copilot Studio and create or open an agent.

Give it a clear name like WorkStory so people can find it in Copilot.

2
Add WorkStory as a tool.

Go to Tools → Add a tool → Model Context Protocol, paste the server URL below, and choose the sign-in (OAuth) authentication option so each person connects with their own WorkStory account.

https://app.workstory.team/mcp
3
Publish the agent to Microsoft 365 Copilot.

Under Channels, enable Microsoft 365 Copilot and publish. Depending on your tenant settings, an admin may need to approve it before it appears for everyone.

4
Open the agent and ask.

In Copilot, choose the WorkStory agent and ask normally. The first time, you'll be sent to WorkStory to log in and approve access.

GitHub Copilot in VS Code

For: anyone using Copilot Chat in VS Code. You connect it yourself — no admin needed.

1
Add an MCP server.

Open the Command Palette and run MCP: Add Server, choose HTTP, and enter the URL below. Or edit .vscode/mcp.json directly.

{ "servers": { "workstory": { "type": "http", "url": "https://app.workstory.team/mcp" } } }
2
Start the server and sign in.

Click Start above the server entry (or run MCP: List Servers). VS Code opens WorkStory so you can log in and approve access.

3
Use Agent mode in Copilot Chat.

Switch Copilot Chat to Agent mode. WorkStory's tools appear in the tools list and Copilot can call them as it answers.

4
Ask a question normally.

Mention WorkStory, a person, team, or review cycle when you want an answer grounded in your data.

Not sure which Copilot you have?

If Copilot lives in Teams, Outlook, Word, or a browser tab with your work account, it's Microsoft 365 Copilot — use the left card and loop in whoever manages Copilot Studio. If Copilot is a chat panel inside VS Code, it's GitHub Copilot — use the right card. Either way the MCP server address is the same: https://app.workstory.team/mcp.

Related use cases

Explore what else you can ask WorkStory.

Browse practical examples for HR, managers, and employees—each built around a focused question and a useful next step.

Data access

It only sees what you can see.

Connecting WorkStory does not expand anyone's access.

Your company only

Every request is limited to the company connected to the signed-in WorkStory account.

Your permissions only

Copilot follows the same access rules as the WorkStory web app.

Answers do not change data

Looking up information is read-only. If you ask to send a feedback request, you must approve it first.

Control

You stay in charge.

01

Everyday questions are read-only. Copilot can retrieve authorized WorkStory information without changing it.

02

Feedback requests need approval. Before a request is sent, you see what will happen and confirm it.

03

Disconnect whenever you want. Remove the workstory entry from mcp.json, or ask your Copilot Studio maker to remove the tool or unpublish the agent.

Troubleshooting

Quick fixes.

WorkStory is not appearing.

Microsoft 365 Copilot: confirm the agent is published to the Microsoft 365 Copilot channel and approved for your tenant. VS Code: check mcp.json is valid JSON and the server shows as running.

It answers without WorkStory.

Start a new conversation, confirm the connector is enabled, and name WorkStory or a specific person, team, or review cycle.

Copilot cannot reach the server.

Check the server URL is exactly https://app.workstory.team/mcp, sign in again, then restart the MCP server in VS Code or republish the agent in Copilot Studio.

It cannot find a person or review.

Check that the item is visible to your account in the WorkStory web app. The connector cannot widen access.

Support

Need a hand?

Email us for help connecting WorkStory, checking access, or troubleshooting an unexpected answer.

WorkStory + Microsoft Copilot

Ask better questions with real performance context.

Connect WorkStory, name the person, team, or review cycle you care about, and get an answer grounded in the data you are allowed to access.

Connect WorkStory ↑