Integrations

Connect apps

Desktop: Sidebar > Integrations (/dashboard/integrations), or Settings > Integrations.

Mobile: profile avatar (top-left) > Profile > Integrations (/m/profile/integrations).

Available connections include Google Calendar (auto-join upcoming meetings), Slack (send action items and summaries to channels or people, and ask Kojo questions from inside Slack), and Notion (Pro plan and above, lets Kojo search and read pages you share, read only).

MCP

The MCP tab sits directly below CRM in the desktop category list. It is available on Pro plans and above and opens the complete MCP Access screen, where you can copy the server URL, connect an OAuth aware client such as Claude, create or revoke a manual client token for Cursor or Warp, and review recent access activity. See MCP Access for the full connection guide.

Personal or shared with a workspace. Right after connecting any of the three, you're asked whether the connection is personal only or shared with a team workspace you own or admin, from the full list of workspaces you belong to (up to 5). You must answer or cancel, cancelling disconnects rather than leaving it in a half-configured state.

Slack

Connect from the Integrations page, then click Configure on the Slack card to pick which channels receive meeting content. Each channel can take summaries, decisions, and action items independently.

Which channels a meeting posts to. A finished meeting goes to the channels its recorder configured, plus any channel bound to the folder the meeting sits in. Your channel choices only ever apply to your own meetings, so connecting Slack never routes a colleague's meetings anywhere.

Restricted meetings are never auto posted. A meeting scoped to specific groups or to only you stays out of Slack entirely, because channel membership has nothing to do with the meeting's audience. You can still share one deliberately from the meeting page.

Direct messages. When a task is assigned to you, MemorDesk DMs you in Slack with buttons to mark it Done, In Progress, or Blocked, and reminds you the day before it is due. Turn this off under Settings > Notifications > Slack notifications, or from Slack with /memordesk dm off.

Slash commands. /memordesk tasks lists your open action items. /memordesk dm on and /memordesk dm off control the DMs above. /memordesk ask, /memordesk link, and /memordesk unlink are covered under Ask Kojo in Slack below, and /memordesk help lists everything.

Disconnecting revokes MemorDesk's access to the workspace, it does not merely forget the connection locally.

Ask Kojo in Slack

Once an owner or admin has connected Slack and shared the connection with the workspace, anyone in the workspace can ask Kojo questions without leaving Slack. Kojo answers from the same meetings, documents, and tasks the person can already see in MemorDesk. In a Slack workspace that was not shared with a workspace, Kojo answers from the asker's personal meetings and documents only, and only for the person who connected that Slack workspace.

Link your account (once per person). In Slack, type /memordesk link, or send the MemorDesk app any message, and it replies with a Link account button. The button opens MemorDesk, where you sign in (and enter your two factor code if you use one), check which Slack account is being linked, and confirm. Your Slack email must match your MemorDesk email. The link works once and expires after 10 minutes. Kojo does not answer anyone who has not linked.

Ways to ask.

• Message the MemorDesk app in Slack. Every message is a question.
• Mention it in a channel it has been added to: @MemorDesk followed by your question.
• Type /memordesk ask followed by your question, in any conversation. This is also the way to ask in a direct message between people, where the app cannot be mentioned because it is not a member of that conversation.

Who sees the answer. In a channel, and for /memordesk ask, only the person who asked. A Share in thread (or Share in channel) button posts it for everyone. It is offered only when the answer came from meetings and documents that everyone in the workspace can see, and never in a channel that includes people from outside your company. Answers from your personal space are never offered for sharing. Owners and admins can switch sharing off. Viewers can ask and read answers like a member, but are never offered the share button.

How a channel is checked before sharing. MemorDesk works out who can actually read the conversation, then checks that every one of them may open every meeting and document the answer came from. The button says how many people will see it, for example "Share in thread, 24 people can see it". Nothing is shared when:

• the channel includes people from outside your company (Slack Connect or a shared channel), or a guest
• someone in the channel cannot be matched to a MemorDesk account, or may not have access to all of the sources
• MemorDesk cannot check who is in the channel, or the channel is too large to check, in which case the answer stays private

A public channel can be read by everyone in your Slack workspace, so only what the whole MemorDesk workspace may read is shared there, and by default every full member of your Slack workspace must be accounted for first. Meetings marked sensitive are never shared. When a share is refused the message is plain and never says which source or which person was the reason.

The same check covers everything else MemorDesk posts to Slack. Automatic meeting recaps, a meeting you send from the meeting's share sheet, and action items you send to a channel or a teammate are all checked against who can read that conversation first. A recap of a group meeting can therefore go to a channel whose every reader is in that group, and is skipped everywhere else. A recap that could not be checked right now is retried automatically.

If a channel changes after you share. MemorDesk remembers what each shared answer was built from, never its text. If someone joins the channel who may not open all of it, the channel is made public, or a meeting or group changes so that someone in the channel can no longer open a source, the answer is removed and the person who shared it is told privately. This is checked when it happens and again daily.

Answers written for a whole channel (optional). An owner or admin can turn on Let people ask for an answer written for a whole channel. Then /memordesk channel <question>, or a mention that starts with "for this channel:", makes Kojo answer using only what everyone in the channel can open, and post it there. The channel just gets the answer. The person who asked gets a private note that they can ask privately for a fuller one. It is off by default, needs a full member role (viewers cannot post), and is never available in a direct message.

Who Kojo answers. Full members of the Slack workspace who have linked their account. Guest accounts (multi channel and single channel guests), deactivated accounts and bots are not answered. In a Slack workspace shared with a MemorDesk workspace, Kojo answers only people who are still members of it, so someone removed from the workspace stops being answered straight away, and a deactivated Slack account loses its link. If Slack cannot confirm an account at that moment, Kojo asks the person to try again rather than guessing.

Credits and limits. Each question costs the same credits as in MemorDesk and counts toward the same hourly limit.

What is kept. Slack conversations are not saved to your Kojo chat history. A short memory of recent turns is held for a few hours so follow up questions work, then discarded. It is also discarded straight away if your access changes in that time, for example if you are removed from a group or a meeting is made private, so a follow up can never reuse something you can no longer see. MemorDesk also keeps a short record of each question for 90 days: who asked, where, what was decided, and how many meetings and documents the answer used. It never contains the question, the answer or a meeting title.

Turning it off. Owners and admins can open the Slack card, click Configure, and use the switches under Ask Kojo in Slack for the whole workspace and for sharing. Under Channels and sharing they can turn the channel answer mode on, relax the public channel check, and count other apps in a channel as unknown readers, and a Recent shared answers list shows what was shared, by whom, to how many people, and whether it was removed because the channel changed. Each person can unlink with /memordesk unlink in Slack, or Unlink Slack account at the bottom of the Integrations page. A link is also removed automatically after a password reset, an admin two factor reset, a forced logout, or an email change, and you link again afterwards.

Checking where you stand. The Ask Kojo in Slack section at the bottom of the Integrations page shows both parts for each Slack workspace. Whose meetings Kojo answers from says whether that Slack workspace is shared with a team workspace, or whether Kojo answers from your personal meetings and documents only. Your Slack account says whether you have linked your account there. A connection set to personal only cannot be switched to shared afterwards. Disconnect Slack and connect it again to be asked.

Mobile: the same Integrations screen (profile avatar > Integrations) holds the Configure panel and the Ask Kojo in Slack section. The link page is a single full page that works the same on a phone.

Notion

Connect from the Integrations page, under the Knowledge category. Available on Pro plans and above. Notion's own setup screen lets you pick exactly which pages or databases to share, only those become visible to Kojo, never your whole workspace.

Once connected, ask Kojo about something and it can search your shared pages and read one when it's relevant, citing what it finds. Read only: Kojo can never edit, create, or delete anything in Notion, the connection itself is configured with read-only capabilities in Notion's own settings, not just by MemorDesk's own code choosing not to write.

Disconnecting only forgets the connection on MemorDesk's side. Notion has no API for a connected app to revoke its own access remotely, to fully remove it, go to Notion's own Settings & members > Connections and remove MemorDesk there too.

Calendar routing (team workspaces)

If you belong to one or more team workspaces, each connected calendar can route its meetings to your Personal Space or to any team workspace you own or admin, decided two ways:

• Per-connection default: click the routing icon on a connected calendar (Integrations page) to pick its default workspace from the full list you belong to.
• Attendee auto-detection: if a meeting invite includes attendees from your team workspace, that meeting is automatically routed to the team workspace even if the calendar's default is Personal.

When a meeting is auto-routed to the team workspace, you get an in-app notification explaining why, so it never looks like the meeting just disappeared from Personal.

Who can see a calendar's meetings

A calendar routed to the team workspace also carries an audience: Workspace default, Everyone, Specific groups, or Only me. Set it on the Integrations page, in the same dialog as routing.

• MemorDesk asks this as soon as a calendar connects. Until you answer, meetings from that calendar are visible only to you, nothing is shared with the workspace yet.
• Changing it later applies to meetings that calendar has already synced, not just future ones. Switching a calendar to Only me pulls its existing meetings back out of the team's view.
• A meeting whose audience you set by hand on the meeting page always wins, the calendar's setting never overwrites it.

How calendar sync stays in step

Your calendar is the source of truth for what is scheduled. MemorDesk keeps a copy of each upcoming meeting so the assistant can join on time without you having the app open, and reconciles that copy against your calendar continuously.

• Delete or cancel an event in Google and its upcoming meeting disappears from MemorDesk, so no assistant joins it. This happens on a schedule, not only when you open the app, so it clears whether or not you are using MemorDesk at the time.
• Remove the meeting link from an event and the same thing happens, there is no longer a call to join.
• Move an event and MemorDesk follows it, the assistant arrives at the new time.
• Right before the assistant is due to join, MemorDesk checks the event one last time, so an event cancelled at the last minute does not get an assistant.
• Meetings that already ran are never touched by this. Editing your calendar does not delete your history.
• Disconnecting and reconnecting the same Google account does not duplicate anything, meetings are matched on the account and event, not on the connection.

Disconnecting a calendar

Integrations > Google Calendar > Manage > Disconnect on the account you want removed. You can also disconnect from the Upcoming Meetings section on the dashboard, which is also where Add calendar connects another Google account.

• Syncing stops immediately for that account only, other connected calendars are unaffected.
• Upcoming meetings from it that have not started yet are removed, so no assistant joins them.
• Meetings that already ran are kept, with their recordings, transcripts, and action items.

Developer API

API keys and webhooks are not available yet. The Developer screen (Settings > Developer on desktop, Settings gear > Developer Settings on mobile) shows them marked Coming Soon.

There is no public REST API to send the note taker, read meetings, or subscribe to events today. Everything MemorDesk does is driven from the app and its integrations.