You are in Claude, working on something, and you need what was decided in Tuesday's meeting. Until now that meant opening Saelyx, finding the minutes, copying a paragraph and going back. Since 3 November, Saelyx is in Claude's connector directory: you connect it, ask Claude, and Claude reads it for you.
It shows up as Saelyx, with the “Community” label. It works in Claude on the web, on the desktop and on mobile, and in Claude's command-line tool. It only reads, and you set the limits.
01What you can ask
You ask Claude in your own words. Three examples:
- “What was left open in the meeting with the design team?” Claude finds the minutes and tells you the decisions, the tasks and the open questions.
- “Prepare tomorrow's meeting.” It checks your next event in the agenda and sets it against earlier minutes, your notes and what Saelyx remembers.
- “What does Saelyx know about the new project?” It searches what Saelyx remembers about you, your minutes, your documents and your notes, and cites where each thing comes from.
Claude decides what to read from what you ask, and you can ask it what it read. The connector also ships five starter prompts, such as “Weekly digest” or “Prepare the next meeting”.
02How it connects
You need a Saelyx account. Saelyx is still invitation-only and the connector doesn't create accounts: without access, the connection stops at Saelyx's sign-in with a notice.
- In Claude, open the connector directory, find Saelyx and connect it. It also has a public listing.
- Claude takes you to saelyx.ai/conectar/. If you aren't signed in, sign in the usual way: the connector has no password of its own.
- Tick what Claude may read and select Allow. You go back to Claude with the connector on.
The permissions screen is in Spanish for now. The table below lists the checkboxes in the order they appear, in English.
Under the hood it is a remote MCP server using OAuth 2.1 with PKCE, at
mcp.saelyx.ai. In Claude's command-line tool you add it with one line:
claude mcp add --transport http saelyx https://mcp.saelyx.ai/mcp
Then, inside Claude, type /mcp, choose saelyx and
Authenticate. Your browser opens with the same permissions screen. Saelyx's
plugin for that command-line tool is on its way into the directory; until it's there, the
line above is the way in.
03Checkbox by checkbox
The permissions screen belongs to Saelyx, not to Claude. Each checkbox is one permission, and what you don't tick, Claude doesn't get. Six come ticked. The two most personal ones, chat history and Ask Saelyx, come unticked. With none ticked, the screen won't let you continue.
| Checkbox | What Claude can read | Tools |
|---|---|---|
| See which Saelyx account is connected (ticked) | Which account you're connected with, your plan and this month's usage | saelyx_whoami, saelyx_get_account_status |
| Read your meetings and minutes (ticked) | The title, date and minutes of each meeting; never the transcript | saelyx_list_meetings, saelyx_search_meetings, saelyx_get_meeting |
| Read your agenda (ticked) | The events in your Outlook (Microsoft 365) calendar | saelyx_get_agenda |
| Read what Saelyx remembers about you (ticked) | The facts it has learned about you; never photos, faces or voice | saelyx_list_memories, saelyx_search_memories |
| Read your knowledge bases (ticked) | The documents you uploaded and the passages that match a search | saelyx_list_knowledge_bases, saelyx_search_knowledge |
| Read your notes (ticked) | Your notes, synced between your devices | saelyx_list_notes, saelyx_get_note |
| Read your chat history with Saelyx (unticked) | Your conversation with Saelyx: the latest turns or a search by text or date | saelyx_search_conversation |
| Ask Saelyx (unticked) | A question that Saelyx answers from your memory, your documents and your chat | saelyx_ask |
That leaves saelyx_ping, which needs no permission and only checks that the
connector responds. If Claude needs a permission you didn't tick, the tool tells it that
it's missing: connect again and tick it.
04It only reads
All fifteen tools are read-only. None of them creates, changes or deletes anything in
Saelyx: no notes, no memory, no documents, no meetings. Only one has a cost:
saelyx_ask uses one of your daily chat messages.
And some data stays put however much you tick: the raw transcript of a meeting (you read the minutes), photos, faces and voice, what your camera or screen sees, your security settings, your billing and your credentials.
Claude reads what you grant and nothing else.
05How to remove it
In your Saelyx account, open Conectores (saelyx.ai/conectar/conectores/; the screen is in Spanish). You see each connection with its application, its permissions, since when it exists, 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). If you have several, Quitar todas (remove all) cuts them at once. Saelyx stops serving that connection in under a minute.
- Disconnecting Saelyx only from Claude removes Claude's access, but it doesn't cancel the permissions in Saelyx. Remove them here too.
- Removing access doesn't delete what Claude already read: that lives in your Claude account. The details are in section 13 of the privacy policy.
- Saelyx keeps a log of each connector access, without its content, for 90 days at most.
06What “Community” means
In the directory, Saelyx carries the “Community” label. It means the connector wasn't
made by the Claude team but by a third party. That third party is me: I built it and I
run it at mcp.saelyx.ai. What Claude reads from Saelyx comes out of that
server and into your conversation with Claude. That's why you decide the permissions on
a Saelyx screen, and why you remove them in Saelyx.
07What it doesn't do
- It doesn't read your email. The connector has no email tool.
- The agenda is Outlook's. Google's doesn't go through the connector.
- It's for Claude. Other MCP clients don't work for now.
-
Odoo and Jira are separate. If you've connected them to Saelyx, a
second connector lets Claude read them too, also read-only and with its own permissions
screen. It isn't in the directory: you add it as a custom connector, with the address
https://mcp.saelyx.ai/integrations/mcp.
The tool-by-tool detail is at saelyx.ai/en/connect/claude/ and in the connectors documentation. If something doesn't work, write to me at info@saelyx.ai.
— Adianny
Senior DevOps engineer. I've spent about four years working with machine learning and MLOps, now as a tech lead; Saelyx is my side project.