Sally - AI Meeting Assistant
LangdockSally

Sally in Langdock

Meetings inside your company AI platform

Langdock supports MCP servers as integrations. Connect Sally once and everyone who works in Langdock can ask about the meetings they are allowed to see.

Start for freeRead the setup guide

30 days free, cancel anytime

LangdockLangdock

Which decisions from the management meetings are still open?

Langdock
Sallyreads from Sally

Three: the hiring budget for Q4, the vendor for the CRM migration, and whether the second location goes ahead.

From: 5 meetings, June and July
Ask about your meetings

50,000+

professionals use Sally

1,000+

companies onboard

98.8%

transcription accuracy

Made in GermanyISO certifiedGDPR compliant

How to use Sally in Langdock

Three steps, and none of them is work.

  1. 1

    Ask Langdock what you want to know

    Typed the way you would ask a colleague. No search syntax, no keywords to remember.

    LangdockLangdock

    What did we agree with this customer over the past quarter?

    Which decisions from the management meetings are still open?

    Summarise all customer feedback about onboarding.

    Ask about your meetings
  2. 2

    Sally searches every meeting, transcript and recording

    Across all your meetings at once, and only in what you are allowed to see.

  3. 3

    You get your answer

    With the meeting it came from, so you can check it instead of trusting it.

    LangdockLangdock
    Langdock
    Sallyreads from Sally

    Three: the hiring budget for Q4, the vendor for the CRM migration, and whether the second location goes ahead.

    From: 5 meetings, June and July

Connect Sally to Langdock

  1. 1

    Create a personal access token in Sally under Settings → Integrations → Sally MCP. Copy it right away, it is shown only once.

  2. 2

    In Langdock, open Integrations and choose Add integration, then Create new.

  3. 3

    Pick the type Connect MCP server.

  4. 4

    Enter the server URL https://app.sally.io/api/v1/McpExternal and select API Key as the authentication method.

  5. 5

    Give the connection a name and paste your token including the sally_pat_ prefix.

  6. 6

    Run Test connection, then enable the Sally tools you want and save.

MCP endpointhttps://app.sally.io/api/v1/McpExternal

Use one token per user rather than a shared one. Access follows the token's Sally user, so a shared token would make every request look like it came from the same person. One requirement on the Sally side: your Sally admin has MCP enabled for the company account.

Read the setup guide

Customer voice

The work starts before the call ends

Jörg-Uwe Liebisch, CEO, Dispomed GmbH - Sally AI customer

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.”
What it cannot do

Try it with your own meetings

Record a meeting with Sally, connect your assistant, and ask it what was decided.

  • Each user's reach follows their own Sally permissions, so a token per person keeps attribution clean.
  • 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.
Start for freeBook a demo
See all AI assistants

Prefer a different assistant?

Sally works the same way in these. Every one has its own setup guide.

Frequently asked questions

An enterprise AI platform that supports MCP servers as integrations. It is where some companies centralise AI access instead of letting everyone use their own assistant.

Better not. Access always follows the Sally user behind the token, so a shared token would show every request as the same person and would hand everyone that person's reach.

Yes. MCP has to be enabled for the company account in Sally, otherwise no connection is established.