Sally in GitHub Copilot
Meeting context inside Copilot Chat
Connect Sally to GitHub Copilot in Visual Studio Code and ask about the call that produced the ticket, without switching windows or digging through notes.
30 days free, cancel anytime
Which API changes did we agree on in the architecture review?
Versioning moves to the header, the old query parameter stays valid until the end of the quarter. The breaking change lands with v3.
From: Architecture review, 22 July50,000+
professionals use Sally
1,000+
companies onboard
98.8%
transcription accuracy



How to use Sally in GitHub Copilot
Three steps, and none of them is work.
Ask GitHub Copilot what you want to know
Typed the way you would ask a colleague. No search syntax, no keywords to remember.
GITHUB COPILOTWhich API changes did we agree on in the architecture review?
What did the customer say about the migration deadline?
Summarise the decisions from this sprint's planning meetings.
Ask about your meetingsSally searches every meeting, transcript and recording
Across all your meetings at once, and only in what you are allowed to see.
MeetingsTranscriptsRecordingsYou get your answer
With the meeting it came from, so you can check it instead of trusting it.
GITHUB COPILOTreads from Sally
Versioning moves to the header, the old query parameter stays valid until the end of the quarter. The breaking change lands with v3.
From: Architecture review, 22 July
Connect Sally to GitHub Copilot
Create a personal access token in Sally under Settings → Integrations → Sally MCP. Copy it right away, it is shown only once.
Install the Microsoft 365 Agents Toolkit extension in Visual Studio Code.
Create a new Declarative Agent, add an action and choose Start with MCP server (Remote).
Enter the endpoint https://app.sally.io/api/v1/McpExternal.
Replace .vscode/mcp.json with the configuration from the setup guide.
Click Start, paste your token when prompted, then enable the Sally tools in Copilot Chat agent mode.
https://app.sally.io/api/v1/McpExternalVisual Studio Code is the only supported surface right now. That is a limitation of Microsoft's Agents Toolkit, which ships as a VS Code extension only, not of Sally. One requirement on the Sally side: your Sally admin has MCP enabled for the company account.
The configuration
Copy it as it is and replace the token with your own. Treat the token like a password.
{
"servers": {
"appsallyio": {
"command": "npx",
"args": [
"-y", "mcp-remote",
"https://app.sally.io/api/v1/McpExternal",
"--header", "Authorization: Bearer ${input:sally_pat}"
]
}
},
"inputs": [
{
"type": "promptString",
"id": "sally_pat",
"description": "Sally Personal Access Token",
"password": true
}
]
}Customer voice
The work starts before the call ends

Jörg-Uwe LiebischCEO, Dispomed GmbH
Customer voice“Sally closes the gap between our meetings and our tools. What we decide is instantly where the work actually happens.”
Try it with your own meetings
Record a meeting with Sally, connect your assistant, and ask it what was decided.
- Visual Studio Code only. The Microsoft 365 Agents Toolkit is not available for other IDEs yet.
- Only your own meetings, plus recordings that were explicitly shared with you through recording folders.
- Delegation rights do not extend to MCP. Meetings you stand in for in Sally stay out of reach here.
- Access is read-only: the assistant reads meetings, it never changes or deletes anything.
Frequently asked questions
Not yet. The connection runs through Microsoft's 365 Agents Toolkit, which currently ships as a Visual Studio Code extension only. As soon as Microsoft supports more surfaces, the same token works there.
Into .vscode/mcp.json, referenced as a prompted input so it is not written into the file itself. Treat it like a password and use one token per person.
No. The connection is read-only. Copilot can search and read meetings, it cannot change or delete anything.