Skip to content
Saelyx
ES Request access
Connect

Saelyx in Claude.

Let Claude read your meeting minutes, agenda, memory, documents and notes from Saelyx. Read-only, permission by permission, and only for as long as you want.

Updated · 10 October 2026

01 What this connector is

Saelyx is a meeting assistant: it listens to your meetings, writes the minutes, remembers what matters to you and keeps the documents and notes you give it. This connector lets Claude (on the web, in the desktop and mobile apps, and in Claude Code) read that data from your Saelyx account when you ask it to.

It is read-only. Claude can look things up and quote them; it cannot create, change or delete anything in Saelyx. The server is run by Saelyx at mcp.saelyx.ai and talks only to Saelyx’s own API.

02 What you need

A Saelyx account. Saelyx is currently available by invitation only. If you don’t have an account yet, request an invitation and wait for our email; the connector cannot create accounts.

Without an invitation the connection stops at Saelyx’s sign-in with this message: “Saelyx is available by invitation only, and this account doesn't have access yet. Request an invitation at saelyx.ai, then come back to Claude and select Connect again.”

Claude on the web, in the desktop or mobile apps, or Claude Code in the terminal. Connectors are managed from Claude’s own settings.

03 How to connect

  • From the directory. In Claude’s connector settings, find Saelyx and select Connect.
  • As a custom connector. If Saelyx doesn’t show up in your directory yet, use this link, which opens Claude with the server address already filled in (https://mcp.saelyx.ai/mcp): Add Saelyx to Claude.
  • In Claude Code. Run claude mcp add --transport http saelyx https://mcp.saelyx.ai/mcp, then type /mcp and choose Authenticate.

Claude then sends you to saelyx.ai. Sign in with your usual Saelyx session (a code we email you; there is no separate password for the connector) and Saelyx shows its own consent screen: which application is asking, with the host of its client identifier next to the name so you can tell who it is, which permissions it will get and where it returns to. Tick what you want to share and select Allow. You are then sent back to Claude.

The consent screen is currently in Spanish; section 5 lists each checkbox in English. Nothing is connected until you approve it.

04 What Claude can read

Fifteen read-only tools; all but saelyx_ping are tied to a permission. Claude calls them when your request needs them; you can always ask it what it read.

  • Meetings and minutes. saelyx_list_meetings (title, date, duration, status), saelyx_search_meetings (search by topic, person or decision) and saelyx_get_meeting (the minutes: summary, topics, decisions, action items, open questions, highlights). The raw transcript is never available.
  • Agenda. saelyx_get_agenda: the events of the calendar you connected to Saelyx (Google Calendar or Microsoft 365) for today, tomorrow, this week or next week.
  • Memory. saelyx_list_memories and saelyx_search_memories: the facts Saelyx has learned about you (preferences, people, decisions). Never photos, faces or voice data.
  • Knowledge bases. saelyx_list_knowledge_bases and saelyx_search_knowledge: the documents you uploaded to Saelyx and the passages that match a search.
  • Notes. saelyx_list_notes and saelyx_get_note: your notes, synced between your devices.
  • Chat history. saelyx_search_conversation: your conversation with Saelyx, the most recent turns or a search by text or date.
  • Ask Saelyx. saelyx_ask: a question answered by Saelyx from your own memory, documents and chat history. Each call uses one of your daily Saelyx chat messages.
  • Account. saelyx_ping (is the connector reachable), saelyx_whoami (which account is connected) and saelyx_get_account_status (plan, this month’s usage and whether Odoo and Jira are connected).

The connector also offers five starter prompts: Follow up on a meeting, Weekly digest, Prepare the next meeting, What do you know about a topic and Open work items.

05 Permissions and revocation

Each checkbox on the consent screen is one permission. The most personal ones are off by default, so granting them is a decision and not an oversight:

  • See which Saelyx account is connected (on by default): your email, id and name, your plan and usage.
  • Read your meetings and minutes (on): the minutes, never the transcript.
  • Read your agenda (on): the events of your connected calendar.
  • Read what Saelyx remembers about you (on): the facts, never photos, faces or voice.
  • Read your knowledge bases (on): your uploaded documents.
  • Read your notes (on).
  • Read your chat history with Saelyx (off by default).
  • Ask Saelyx (off by default): it uses one of your daily chat messages per question.

A connection sees only the data of the account that authorised it, and only within the permissions it was granted. If Claude needs a permission you didn’t tick, the tool answers that the permission is missing: connect again and tick it.

To revoke: under Connectors in your Saelyx account (the screen is in Spanish) you see every connection: the application, which Saelyx connector it belongs to, its permissions, when it was made, when it expires and how many calls it has made today. Select Quitar acceso (remove access) and confirm with ¿Seguro? Quitar (are you sure? remove); Saelyx stops serving it within a minute. Disconnecting Saelyx from Claude’s side removes Claude’s access but does not cancel the permissions in Saelyx, so revoke there too. Revoking does not delete what Claude already received: that lives in your Claude account.

06 What never leaves Saelyx

  • The raw transcript of a meeting. Only the minutes are available.
  • Photos, faces, voice or any other biometric data, and what your camera or screen sees.
  • Your security settings and billing.
  • Your credentials: the calendar you connected to Saelyx, and your Odoo and Jira keys, stay encrypted in Saelyx. The token Claude presents to the connector is never forwarded anywhere.
  • Nothing is written. The connector creates, edits and deletes nothing: no notes, no memory, no documents, no meetings.

07 How your data is handled

Everything the connector returns is Saelyx’s own data about the signed-in user: your meeting minutes, memory, documents, notes, chat history and agenda, plus the answers Saelyx itself gives to a question. The server at mcp.saelyx.ai calls only Saelyx’s own API. The one exception is the agenda tool, which returns your upcoming events: Saelyx reads them on your behalf from the calendar you connected to it (Google Calendar or Microsoft 365) with Saelyx’s own OAuth apps. Those calendar credentials are stored by Saelyx; the token Claude sends is never passed on.

Every tool is read-only, returns only the signed-in user’s data and stays within the permissions you approved. Saelyx keeps a history of each connector access (which connection, which tool, which permission, when, how long it took and how big the answer was) for up to 90 days, without the content. Saelyx does not store or log the content of your Claude conversations beyond the arguments each tool call needs in order to run. The connector carries no advertising or sponsored content and is not designed to process health data.

The full detail, including what Saelyx receives from Claude, is in section 13 of the privacy policy.

08 Odoo and Jira: a separate connector

If you have connected Odoo or Jira to Saelyx (from the Saelyx app), a second connector lets Claude read them too: your Odoo inbox, searches and records, and your Jira inbox, searches and issues. Read-only, as always. It is not part of the Saelyx connector in the directory: you add it yourself as a custom connector, it asks for its own permissions (account, Odoo and Jira, with Odoo and Jira off by default) and it has its own consent screen.

Server address: https://mcp.saelyx.ai/integrations/mcp. In Claude Code: claude mcp add --transport http saelyx-integrations https://mcp.saelyx.ai/integrations/mcp.

Add Saelyx integrations to Claude

Its tools: saelyx_odoo_inbox, saelyx_odoo_search, saelyx_odoo_get_record, saelyx_odoo_get_message, saelyx_jira_inbox, saelyx_jira_search and saelyx_jira_get_issue, plus saelyx_ping, saelyx_whoami and saelyx_get_account_status. Your Odoo and Jira credentials stay in Saelyx and are never given to Claude; what Claude reads from them contains other people’s data (customers, colleagues), and you are the one who decides to send it.

09 Common errors

  • “Saelyx is available by invitation only…” Your account has no access yet. Request an invitation, wait for our email, then select Connect again.
  • “This request has expired.” The consent link lives for ten minutes. Go back to Claude and select Connect again.
  • “This connection was not started in this browser.” Finish the connection in the same browser where you selected Connect. If you didn’t start it, close the window.
  • Claude asks you to authenticate again. The connection was revoked under Connectors or it expired. Connect again.
  • A tool says a permission is missing. You didn’t tick it on the consent screen. Connect again and tick it.
  • “Ask Saelyx” says the daily limit is reached. Each question uses one of your plan’s daily chat messages. It resets the next day.

10 Support, privacy and security

Questions or problems: info@saelyx.ai, or the support page. We reply on working days, by hand.

Privacy policy (section 13 covers the connector) · Terms.

Security issues: write to the same address. The disclosure policy is published at /.well-known/security.txt, following RFC 9116.