Saelyx now talks to Claude

Saelyx listens to your meetings, writes the minutes, remembers what matters to you and keeps your documents and notes. Since 10 October 2026 it is also a Claude connector: on the web, on the desktop and in Claude Code, Claude can read as much of that as you authorise. Under the hood it is a remote MCP server, at https://mcp.saelyx.ai/mcp.

It's read-only: Claude looks things up and quotes them, and you set the limits, permission by permission.

01What you can ask

You ask Claude in your own words. Three examples:

• “What was left pending in the meeting with the design team?” Claude finds the minutes and tells you the decisions, the tasks and the open questions.
• “Get me ready for tomorrow's meeting using my agenda and the previous minutes.” It lines up your agenda, from the calendar you've connected to Saelyx, with what was said in earlier meetings.
• “Search my notes for what I wrote down about the budget.” It can also read your notes and the documents you keep in Saelyx.

Claude decides what to read depending on what you ask, and you can always ask it what it read. It can also put a question to Saelyx, which answers from your memory, your documents and your chat history.

02Permission by permission

When you connect, Saelyx shows you its own consent screen, with eight checkboxes: your account, your meetings and minutes, your agenda, what Saelyx remembers about you, your documents, your notes, your chat history and asking Saelyx. You tick what you want to share. The two most personal ones, chat history and asking Saelyx, come unticked.

• From a meeting, Claude reads the minutes, never the raw transcript.
• Asking Saelyx uses one of your daily chat messages for each question.
• To take access away, go to saelyx.ai/conectar/conectores/ (the screen is in Spanish). You see which application has access, with which permissions, since when and how many calls it has made today, and you remove it with “Quitar acceso”.
• Saelyx keeps a log of every access, without its content, for 90 days at most.

Revoking doesn't delete what Claude has already read: that lives in your Claude account. The details are in section 13 of the privacy policy.

03How to connect it today

Saelyx doesn't appear in Claude's connector directory yet, so today you add it as a custom connector:

1. In Claude, open Settings → Connectors → Add custom connector.
2. As the server address, enter https://mcp.saelyx.ai/mcp.
3. Claude takes you to saelyx.ai/conectar/. Sign in with your Saelyx session, tick the permissions you want to grant and press Permitir (Allow). That screen is in Spanish.

In Claude Code it's one line:

claude mcp add --transport http saelyx https://mcp.saelyx.ai/mcp

Then type /mcp and choose Authenticate; from there it's the same as above. Nothing connects until you approve it. The full documentation, with all 15 tools and the most common errors, is at saelyx.ai/en/connect/claude/.

04Odoo and Jira, as a separate connector

If you've connected Odoo or Jira to Saelyx (I cover that integration in Odoo and Jira by voice), a second connector lets Claude read those too, also read-only. You add it as a custom connector, at this address: https://mcp.saelyx.ai/integrations/mcp. It has its own permissions and its own consent screen, and your Odoo and Jira keys stay in Saelyx.

05What's next

The request to list Saelyx in Claude's connector directory is under way. I don't have a date and I'd rather not make one up. Until then, the custom connector above is the way in.

06You need an invitation

Saelyx is still invite-only, and the connector doesn't create accounts: only accounts with access can connect. If you don't have access yet, request an invitation. If you try without it, the connection stops at Saelyx's sign-in with a notice. And 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.