Microsoft 365 MCP server
Give AI assistants live Microsoft 365 context through Pear MCP.
Pear exposes Microsoft 365 tools through OAuth from the same hosted endpoint used for Apple workflows. AI clients connect through maintained setup guides, while reads, writes, and approvals follow each client’s current plan, role, and permission model.
Live Microsoft 365 context
Bring Microsoft 365 work into the AI-client paths Pear documents.
Outlook Mail, Calendar, Contacts, and To Do from one MCP endpoint.
pear://connectedWhat you can do
- Use Microsoft 365 Calendar, Outlook Mail, Contacts, and To Do through one remote MCP endpoint.
- Let an agent read Outlook mail, prepare a non-sending Pear draft, and send a new message after you review the action.
- Create, update, search, and delete Microsoft 365 calendar events from natural language.
- Capture follow-ups as Microsoft To Do tasks with due dates and context.
- Connect with Microsoft OAuth instead of app passwords or copied credentials.
- Choose a maintained Pear guide for Claude, ChatGPT, Grok, Codex, Hermes, Cursor, Windsurf, or Cline; client capabilities vary.
From setup to your first request
Make the connection. Then make it useful.
Follow your client’s setup guide, then try a request with the accounts you have connected.
Try first
Start with a question.
What is on my Outlook calendar tomorrow and what needs preparation?
Send a short follow-up email from Outlook confirming the meeting time.
Create a Microsoft To Do task for each follow-up in this plan.
Find recent Outlook mail from this client, summarize it, and prepare reply text for review.
Move my 3pm meeting to a free slot on Friday and email the attendees.
Setup path
Connect once. Keep your apps close.
Create a Pear account.
Choose Microsoft 365 during onboarding and complete the OAuth flow.
Add https://pearmcp.com/api/mcp to your AI client and authenticate with Pear.
Why it matters
A little less switching.
Keep Microsoft work data available inside the assistant you already use.
Avoid custom Graph scripts for common calendar, task, contact, and mail workflows.
Use one dashboard to manage provider health, API keys, and MCP routing.
- Microsoft OAuth sign-in, no Microsoft password stored
- Revocable from your Microsoft account or tenant settings
- Encrypted tokens and scoped provider access
A few good questions
Before you connect.
Can an AI agent manage Outlook Mail with Pear?
Pear exposes Microsoft 365 mail workflows through MCP. A configured client can search mail, prepare reply text in a non-sending Pear draft, send a new message, and combine inbox context with calendar or task actions when its current permissions allow those tools. Pear does not store that draft in Outlook or send an in-thread reply.
Can Codex or Claude create Microsoft 365 calendar events?
Pear maintains setup paths for Codex, Claude, and other clients. Once Microsoft 365 is connected, a client can use Pear calendar tools according to its current authentication, plan, role, approval, and write permissions.
Does Pear use my Microsoft password?
No. Pear uses Microsoft OAuth for Microsoft 365, stores encrypted provider tokens, and lets you revoke access from your Microsoft account or tenant settings.
Microsoft 365 MCP server
Ready to connect your apps?
Pear exposes Microsoft 365 tools through OAuth from the same hosted endpoint used for Apple workflows. AI clients connect through maintained setup guides, while reads, writes, and approvals follow each client’s current plan, role, and permission model.