Microsoft 365 access for AI agents
The Rubi 365 MCP lets Claude work with Outlook Mail, Calendar, and Microsoft To Do. You review and send messages and invitations yourself.
The Model Context Protocol (MCP) server limits which actions the agent can take. The Rubi Odoo MCP docs explain the shared access pattern.
What the 365 MCP can do.
Search, draft, file, and flag mail, manage events, check availability, or turn an email into a task. Reusable prompts include summarize_inbox, prepare_week, and email_to_task.
Mail tools are drafts-only. New events go on your own calendar without attendee invitations. The server asks for confirmation before deleting an event or task and returns Outlook web links for review.
Identity and permissions
Each person signs in through Microsoft Entra ID. Requests use short-lived, delegated tokens limited to that person's permissions. Calls go through Microsoft Graph. The server keeps its own secrets in Azure Key Vault, outside the AI client.
The agent prepares the work. You stay in control of what actually goes out.
Extending Microsoft 365 access
Microsoft Graph lets us scope extensions for OneDrive and SharePoint and Teams. The same identity and approval model can cover workflows such as reading a document, preparing a draft, and updating a task.
Related MCP connectors
The 365 MCP shares its access model with the Rubi Odoo MCP and the Rubi Loom MCP. We apply it to other systems with APIs.
Frequently asked questions.
The server leaves mail in Drafts and does not send invitations. Send or invite after reviewing the details in Outlook.
The connector stores no long-lived Microsoft 365 user credentials or API keys. Each request uses a short-lived delegated token.
Yes. We scope OneDrive, SharePoint, or Teams access to the needs of each engagement.