Skip to content

SSO

Microsoft 365 MCP connector

The Microsoft 365 connector brings your Teams, channels, chats, chat messages and user directory into Claude, ChatGPT, Cursor and the Elaichi Agent, so each person can search and act on them inside their own Microsoft 365 access.

  • How it connects. Connects over OAuth. The credential goes into a vault nobody reads back.

  • One address. https://api.elaichi.ai/mcp, the same for every user.

  • Their own access. An agent never gets more than the person it acts for.

How to connect

How to connect Microsoft 365 to Claude, ChatGPT or Cursor

Two steps, about a minute.

1

In Elaichi

Connect Microsoft 365 once

  1. Open Connections, choose Add connection, and pick Microsoft 365.

  2. Optionally set Share with to give a team access, then press Connect.

  3. Approve it in Microsoft 365. Microsoft 365's own window opens. Whoever approves it decides what this connection can reach.

The credential is vaulted. Nobody reads it back, not even the AI.

Add connection

Choose a connector.

microsoft 365
Microsoft 365
Auth0
Google
Google Workspace
JumpCloud
Okta
2

In your AI client

Point it at one endpoint

Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.

Microsoft 365 MCP connector for Claude

  1. 1

    Open Customize, then Connectors.

  2. 2

    Press Add.

  3. 3

    Name it, paste the MCP server URL, then Continue.

    https://api.elaichi.ai/mcp
  4. 4

    Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

Microsoft 365 MCP connector for ChatGPT

  1. 1

    Open Plugins, then press the + button.

  2. 2

    Name it and paste the endpoint into Server URL.

    https://api.elaichi.ai/mcp
  3. 3

    Leave Authentication on OAuth, then tick the risk acknowledgement.

  4. 4

    Press Create, then sign in and approve.

Works on the web today. The plugin directory lives at chatgpt.com/plugins.

Microsoft 365 MCP connector for Cursor

  1. 1

    Open ~/.cursor/mcp.json.

  2. 2

    Add the endpoint under mcpServers.

    https://api.elaichi.ai/mcp
  3. 3

    Reload Cursor, then sign in and approve.

~/.cursor/mcp.json

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

Set up per machine, so repeat it on each computer you work from.

Connect Microsoft 365 to any MCP client

  1. 1

    Add the endpoint as a remote MCP server.

    https://api.elaichi.ai/mcp
  2. 2

    Sign in and approve.

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

The Elaichi Agent already has these tools, with nothing to set up.

Use cases

What teams do with Microsoft 365 through Elaichi

Every one of these runs inside the access the person already has, and lands in the same audit log.

  • Sales

    Post the call recap to the deal channel

    After a customer call, have the agent write a short recap and post it to the account's Teams channel so the rest of the deal team sees the next steps without being asked.

  • Support

    Find the chat where the fix was agreed

    Search across chats and channels for the thread about a customer's issue, pull out what was decided, and reply in the same chat with the answer.

  • Operations

    Set up channels for a new project

    Create the project channels, name them to match your convention, and start the kickoff chat with the right people, all in one request.

  • HR

    Check who is still in which team

    List the members of a team, compare them with who should be there, and remove anyone who has moved on.

  • IT

    Keep the user directory tidy

    Look up a person by name, confirm their account details, and remove accounts that should no longer exist in Microsoft 365.

  • Leadership

    Catch up on a week of chats

    Ask what changed across the channels and chats you care about and get a summary with the open questions, instead of scrolling through Teams on Monday morning.

Try asking

  • “Post a recap of today's customer call to the Northwind channel”
  • “Who is in the Support Escalations team right now?”
  • “Find the chat where we discussed the Q3 pricing change”

See all 86 Microsoft 365 tools below

Compare

Elaichi vs Zapier MCP vs Composio for Microsoft 365

All three can connect Microsoft 365 to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.

Elaichi compared with Zapier MCP and Composio for Microsoft 365, by what to check
What to check Elaichi Zapier MCP Composio
Where the AI connects One address for the whole organization. https://api.elaichi.ai/mcp A server per member, created at sign-in. An MCP endpoint per team, or an SDK.
Control over Microsoft 365 tools Allow or restrict single Microsoft 365 tools, per role or user. App and action restrictions on the account. Role permissions, down to the action.
Record of calls One audit entry per Microsoft 365 call. A History tab of tool calls. A log of every tool call.
Single sign-on SAML or OIDC, plus SCIM, on Gold. SAML on Enterprise. SAML and OIDC on Enterprise.
Price $15 per user per month. 2 tasks per successful call. Billed per tool call.

Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.

Longer take: Zapier MCP alternative and when you don't need an MCP gateway.

AI tools

Microsoft 365 tools for your AI agents

86 tools are ready to call through Elaichi's MCP endpoint the moment you connect Microsoft 365, governed by the same roles, restrictions, and audit log as everything else in Elaichi.

See it in Elaichi

What connecting Microsoft 365 gets you

6 screens from the product, each doing one job for your Microsoft 365 account.

The agent

Ask about Teams chats in plain words.

Starter prompts pull live channels, chats and members from Microsoft 365 and answer directly.

  • teams
  • channels
  • chats
  • messages

Ask Elaichi to work across your apps.

Post a recap of today's customer call to the Northwind channel

Who is in the Support Escalations team right now?

Find the chat where we discussed the Q3 pricing change

Also runs in Claude, ChatGPT or Cursor

MCP clients

Microsoft 365 in Claude, ChatGPT and Cursor.

One governed endpoint over OAuth, no SDK, no shared API key, every client connected once.

ElaichiMCP clients
Claude ChatGPT Cursor

Copy the endpoint

https://api.elaichi.ai/mcp
Client Connected by Status Last used
Claude
E

Emily Carter

• Connected 4 minutes ago
Cursor
M

Megan Brooks

• Connected 2 hours ago
ChatGPT
R

Ryan Hayes

• Connected Yesterday

Tool catalog

86 Microsoft 365 tools, no code to write.

Teams, channels, chats, messages and users, listed with resources and methods, ready to use.

  • List all Microsoft 365 teams
  • Get single Microsoft 365 team by ID
  • List all Microsoft 365 team members
  • Get single Microsoft 365 team member by ID
ElaichiTools
Tool Action Description
List all Microsoft 365 teams List List Microsoft teams in the organization, with optional OData ordering, property selection, and entity expansion. Returns each team object including its id, displayName, description, memberSettings, and createdDateTime. Results are paginated.
Get single Microsoft 365 team by ID Get Get the properties and relationships of a specific Microsoft team by id. Returns the team object, identified by its id. Required: id.
List all Microsoft 365 team members List List members of a Microsoft team. Returns each conversation member's id plus its subtype-specific fields (attributes); membership ids are opaque strings and members may span tenants. Required: team_id.
Get single Microsoft 365 team member by ID Get Get a single conversation member of a Microsoft team by id. Returns: id, displayName, roles, visibleHistoryStartDateTime, attributes, token_type, expires_in, ext_expires_in, access_token. Required: team_id and id.
Delete a Microsoft 365 team member by ID Delete Remove a conversation member from a Microsoft team by id. Returns an empty 204 response on success. Required: team_id and id.

Toolboxes

Every team gets its own Microsoft 365 toolbox.

Scope a toolbox to Sales, Support or IT and each team sees only its own.

  • Sales
  • Support
  • IT
  • HR
ElaichiToolboxes
Name Source template Tools Created

Sales toolbox

Microsoft 365 · deal channels and customer chats

Microsoft 365 starter 18 Mar 4, 2026

Support toolbox

Microsoft 365 · escalation chats and channels

— 9 Mar 2, 2026

IT toolbox

Microsoft 365 · users and team membership

— 24 Feb 27, 2026

HR toolbox

Microsoft 365 · onboarding teams and members

Microsoft 365 starter 6 Feb 19, 2026

Operations toolbox

Microsoft 365 · project channels and chats

— 31 Jan 30, 2026

Leadership toolbox

Microsoft 365 · team digests and chat summaries

— 12 Jan 22, 2026

Shared connections

Teammates work through a connection, never a credential.

The connections table shows who connected each Microsoft 365 account and who it is shared with.

  • Sales EMEA
  • Support
  • IT Helpdesk
  • People Ops
ElaichiConnections
Connection Scope Status Access
MI

Microsoft 365 (Sales EMEA)

Connected by Emily Carter

Personal • Active 1 team · 6 members
MI

Microsoft 365 (Support)

Connected by Jake Morgan

Organization • Active 3 teams · 24 members
MI

Microsoft 365 (IT Helpdesk)

Connected by Megan Brooks

Organization • Active 2 teams · 11 members
MI

Microsoft 365 (People Ops)

Connected by Tyler Reed

Personal • Needs re-auth 1 team · 3 members
MI

Microsoft 365 (Project Office)

Connected by Ryan Hayes

Personal • Active Not shared
MI

Microsoft 365 (Executive)

Connected by Ashley Parker

Personal • Active 2 teams · 9 members

Audit log

Every Microsoft 365 call lands in the log.

When, who, what happened, type and resource, so you can answer who posted that message.

  • When
  • Who
  • What happened
  • Type
ElaichiAudit log
When Who What happened Type

2 minutes ago

Mar 6, 2026, 3:10 PM

E

Emily Carter

[email protected]

Restriction Created Access

8 minutes ago

Mar 6, 2026, 3:04 PM

J

Jake Morgan

[email protected]

Restriction Updated Access

14 minutes ago

Mar 6, 2026, 2:58 PM

M

Megan Brooks

[email protected]

Role Assigned Access

20 minutes ago

Mar 6, 2026, 2:52 PM

T

Tyler Reed

[email protected]

Microsoft 365 Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

R

Ryan Hayes

[email protected]

Microsoft 365 Teams Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

A

Ashley Parker

[email protected]

Microsoft 365 Teams List Toolbox

Launching soon

From answering questions to doing the work

A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.

Automations

A schedule starts the work, a person approves.

New chat messages are fetched, grouped, drafted into a digest, approved, then posted to the channel.

Microsoft 365 digest

Run 418 · started 2 minutes ago · on behalf of Emily Carter

  1. ✓

    Schedule

    Every weekday at 8:00 AM

    0.2s
  2. ✓

    Fetch teams

    Microsoft 365

    1.4s
  3. ✓

    Group by owner

    Transform

    0.1s
  4. ✓

    Draft the digest

    Agent step

    Ran with 4 tools, returned a structured summary

    6.2s
  5. Approve the digest

    Needs approval

    Assigned to Michael Brennan

    Approve
  6. Post the digest

    Microsoft 365

    Queued

Collections and dashboards

Microsoft 365 health numbers, nobody has to ask.

Four metrics, a 14 day chart of messages created and a team breakdown, no model involved.

Microsoft 365 health

Refreshed 4 minutes ago · every 15 minutes · from the teams collection

Live

Teams

1,284 ↓ 12%

Channels

96 ↓ 8%

Needs attention

3 ↑ 2

Updated this week

412 ↑ 9%

Teams created

Last 14 days

By team

Share of activity

Sales EMEA 34%

Support 27%

IT Helpdesk 21%

People Ops 18%

FAQ

Frequently asked questions

How do I connect Microsoft 365 to Claude?

First, connect Microsoft 365 in Elaichi: a Microsoft sign-in window opens, you sign in with your work account and approve, and there is no OAuth application to register and no client ID or secret to generate. Then open Claude, go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp as the endpoint. Claude asks you to sign in to Elaichi, and from then on it can work with your Microsoft 365 teams, channels and chats as you.

Does Microsoft 365 work with ChatGPT and Cursor as well as Claude?

Yes. Once Microsoft 365 is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any MCP client and the Elaichi Agent. You connect Microsoft 365 once and every client you use picks it up.

What can an AI agent actually do with my Microsoft 365 data?

With Microsoft 365 connected, an agent can list your teams and their members, browse channels, read and search chats and chat messages, send a message into a chat, create or rename a channel, and look people up in the user directory. In practice that means asking for a recap of a channel, finding the chat where something was decided, or posting a note to the right team. Short, concrete asks work better than long sentences.

Does connecting Microsoft 365 give the AI access to everything in my tenant?

No. Access follows the person who signed in, so an agent working through Microsoft 365 sees only the teams, channels and chats that person can already see, and a private channel they are not in stays hidden. Elaichi can narrow that access further with restrictions, and it never widens it beyond what Microsoft 365 already allows that person.

Can my team share one Microsoft 365 connection?

Yes. One person connects Microsoft 365 in Elaichi and shares the connection with a team, and nobody else ever sees or handles a credential. Each teammate still signs in to Elaichi as themselves, so every action in Microsoft 365 is logged under the name of the person who asked for it.

Can I stop an agent from deleting or changing things in Microsoft 365?

Yes. Restrictions in Elaichi work per action, so you can block deleting users, removing team members, deleting channels or chats, or editing messages while still allowing reading and searching. A restricted action is left out of the tool list the AI client receives for Microsoft 365, so it cannot be called no matter how the prompt is worded.

What happens to a Microsoft 365 connection when someone leaves?

Offboarding a person in Elaichi ends their access to Microsoft 365 through every client at once. A shared Microsoft 365 connection keeps working for everyone else on the team. If you want to remove Microsoft 365 entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client.

Does the Microsoft 365 MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. Microsoft 365 is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

Is Elaichi an alternative to Zapier MCP for Microsoft 365?

Yes. Both let Claude, ChatGPT or Cursor use Microsoft 365. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Microsoft 365 call.

How is Elaichi different from Composio for Microsoft 365?

Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Microsoft 365: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

Put Microsoft 365 in front of your team

14 days on Gold, no credit card. Connect it once and pick what each team can call.

Works with
Claude ChatGPT Cursor and any other MCP client, or the Elaichi Agent.
When the trial ends
Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.