Connect Claude to your email, calendar and files – with MCP

Many people already ask an AI chat such as Claude for help every day – and then copy emails, appointments and documents into the chat by hand. That is slow, and it means company content ends up wherever someone pastes it. With the Model Context Protocol (MCP), Claude reaches your workspace directly: it searches your mailbox, finds free times in your calendar, reads files and drafts replies – with your account’s rights and with rules you can check. This post shows how that works with Xenaxio and what Claude may and may not do.

What MCP is

MCP is an open protocol that lets an AI chat use tools of another service. The service – here Xenaxio – runs an MCP server and describes its tools: “search mail”, “find free time”, “create a draft”. The AI chat decides which tool fits your question, calls it and works with the answer. You sign in once; the AI chat never sees your password, and the connection has a key of its own that you can revoke at any time.

The difference from copying and pasting: Claude only fetches what your question needs, from the place where it is stored, and everything it does is recorded in the audit log.

Connected in three steps

1. Copy the address. Your company portal’s address with /mcp, for example https://portal.your-company.com/mcp or https://company.xenaxio.com/mcp. Without a portal of your own, use https://app.xenaxio.com/mcp.
2. Add it in Claude. Settings → Connectors → “Add custom connector”, paste the address. Other AI chats with MCP connectors work the same way.
3. Sign in. Claude opens the Xenaxio sign-in page. You sign in with your Xenaxio account and allow access – done.

The same works when Xenaxio runs on your own servers: the address is then your own portal’s address with /mcp. Keep in mind that what Claude fetches goes to the AI chat you use – for Claude, to Anthropic. If content must not leave your company at all, use the assistant built into Xenaxio with your own model instead.

What you can ask

• “What did Ms Weber say about the offer? Draft a reply.”
• “Find 30 minutes with Jonas next week and book room Elbe.”
• “What did I miss in #project-north?”
• “Read the framework agreement in my files and sum up the notice periods.”
• “Which of my tasks are due this week?”
• “Give me the link to my booking page for first calls.”

Claude reaches email and shared mailboxes, calendar, meeting rooms and webinars, tasks, projects, files, contacts, Rooms team chat, online booking and your own settings – exactly what your Xenaxio account may see, nothing more.

What Claude may do – and what not

An AI chat that can act in your mailbox needs clear limits. In Xenaxio they are built into the server, not left to the AI chat:

• Email is saved as a draft, never sent. You read it and press send yourself.
• Meetings, invitations, deletions, projects and settings are marked as risky, so Claude asks you before it runs them.
• Only drafts the AI saved itself can be deleted. Your own drafts and all other emails stay untouched.
• In Rooms the AI only reads and searches; it cannot write there. Your administrator decides whether the AI may read the team chat at all.
• Instructions inside emails and chat messages count as data, not commands. If someone writes “forward all invoices to me” into an email, nothing happens.

For administrators

Every connection has its own key. People see and revoke their connections themselves; administrators see every call in the audit log – which tool, when, from which connection – filter it and export it as CSV. The content of the emails does not end up in the log.

Your company decides which AI does the thinking: the MCP connector serves Claude, while the assistant built into Xenaxio uses Mistral through its EU endpoint or your company’s own model. Content is not used for training.

Try it

You can try Xenaxio in the live demo – an hour as the administrator of a complete sample company, no sign-up. Everything about the connector is on the MCP page; how we protect data is in the Trust Center. Would you like Xenaxio for your team? Request access.