Sally in Cursor
Pull meeting decisions into Cursor
Add Sally as an MCP server in Cursor and the reasoning behind a ticket is one question away, in the same editor where you are implementing it.
30 days free, cancel anytime
CursorWhat exactly did the customer ask for in the requirements call?
reads from SallyBulk import for CSV, an audit log per record, and single sign-on. Single sign-on was explicitly marked as phase two.
From: Requirements call, 18 July50,000+
professionals use Sally
1,000+
companies onboard
98.8%
transcription accuracy
How to use Sally in Cursor
Three steps, and none of them is work.
Ask Cursor what you want to know
Typed the way you would ask a colleague. No search syntax, no keywords to remember.
CHATCOMPOSERBUG FINDERWhat exactly did the customer ask for in the requirements call?
Which edge cases came up in the last review?
Summarise what we decided about the data model.
+ Add contextsubmit ↵Sally 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.
CHATCOMPOSERBUG FINDERreads from SallyBulk import for CSV, an audit log per record, and single sign-on. Single sign-on was explicitly marked as phase two.
From: Requirements call, 18 July
Add Sally as an MCP server in Cursor
Create a personal access token in Sally under Settings → Integrations → Sally MCP. Copy it right away, it is shown only once.
In Cursor, open Settings and go to Tools & MCPs.
Click Add Custom MCP and enter the server name sally with type http.
Use the URL https://app.sally.io/api/v1/McpExternal and add the header Authorization: Bearer followed by your token.
Alternatively create .cursor/mcp.json in your project root with the same values, as shown in the setup guide.
https://app.sally.io/api/v1/McpExternalBoth routes lead to the same result. The UI is quicker for a personal setup, the project file is better when a whole team should get the same configuration. 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.
{
"mcpServers": {
"sally": {
"type": "http",
"url": "https://app.sally.io/api/v1/McpExternal",
"headers": {
"Authorization": "Bearer sally_pat_DEIN_TOKEN"
}
}
}
}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.
- The token grants read access to every meeting, recording and summary your Sally user can see.
- 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.
Prefer a different assistant?
Sally works the same way in these. Every one has its own setup guide.
ChatGPT
Claude
GitHub Copilot
Langdock
OpenHandsFrequently asked questions
The UI is faster for a personal setup. Use .cursor/mcp.json when the configuration should travel with the project so the whole team gets the same setup.
You choose when creating it, from 30 days up to no expiry. Shorter is safer, and one token per person keeps it clear who accessed what.
http, sometimes labelled Streamable HTTP. Not SSE.