Sally in OpenHands
Autonomous agents that know the meeting
OpenHands, formerly OpenDevin, is an open-source platform for autonomous software agents. Connect Sally and your agents can read the meeting that produced the task before they start working on it.
30 days free, cancel anytime
Read the review meeting and list every change request.
Seven change requests. Four are UI copy, two touch the export format, one needs a schema change and was flagged as blocking.
From: Review meeting, 24 July50,000+
professionals use Sally
1,000+
companies onboard
98.8%
transcription accuracy



How to use Sally in OpenHands
Three steps, and none of them is work.
Ask OpenHands what you want to know
Typed the way you would ask a colleague. No search syntax, no keywords to remember.
OpenHands
Which requirements were agreed in the last requirements call?
Read the review meeting and list every change request.
Which tickets follow from yesterday's planning?
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.
OpenHands
reads from Sally
Seven change requests. Four are UI copy, two touch the export format, one needs a schema change and was flagged as blocking.
From: Review meeting, 24 July
Connect Sally to OpenHands
Create a personal access token in Sally under Settings → Integrations → Sally MCP. Copy it right away, it is shown only once.
Open OpenHands Cloud and go to your profile, then MCP.
Click Add Server and choose the server type SHTTP. Not SSE.
Enter the URL https://app.sally.io/api/v1/McpExternal.
Paste your complete token including the sally_pat_ prefix as the API key, without the word Bearer.
Leave the timeout at 60 seconds and test the connection with a real meeting question.
https://app.sally.io/api/v1/McpExternalUsing the OpenHands SDK instead of the cloud UI? Then pass the MCP configuration to the agent directly, as shown in the setup guide. 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.
mcp_config = {
"mcpServers": {
"sally": {
"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.
- Server type SHTTP is required. SSE does not work.
- 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.
Frequently asked questions
Yes. OpenHands is the current name of the project formerly called OpenDevin.
Sally's MCP endpoint speaks streamable HTTP. Picking SSE in OpenHands is the most common reason a connection fails to come up.
No. The connection is read-only. An agent can search meetings, read summaries and transcripts, and nothing else.