Outlook Mail MCP
Give AI assistants live Outlook Mail context through a hosted MCP endpoint.
Pear uses Microsoft OAuth to expose bounded Outlook Mail reads and a focused set of mailbox writes. A configured client can send a new message, move mail, change read state, or move a message to trash when its permissions and active write policy allow the action.
Hosted Outlook Mail
Move from inbox context to a deliberate next action.
Find the right message, read a bounded body, and act with approval.
outlook://connectedWhat you can do
- List Outlook mail folders and message metadata, then search for the messages relevant to a task.
- Read message bodies in bounded segments rather than returning an unbounded mailbox payload.
- Send a new Outlook message after the exact recipients, subject, and body enter Pear’s approval flow.
- Move messages between folders, mark them read or unread, or move them to trash with mail-write access.
- Use Microsoft OAuth; Pear does not ask for or store your Microsoft password.
- Connect through one hosted endpoint, then follow the maintained setup path for your AI client.
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.
List unread Outlook mail from this week that mentions the Atlas project.
Read the latest message from Morgan and summarize only what is present in the message body.
After I approve the recipients, subject, and body, send a new Outlook message confirming Friday’s meeting.
Move these selected newsletters to Archive and mark them as read after I approve the changes.
Setup path
Connect once. Keep your apps close.
Create a Pear account, choose Microsoft 365, and complete Microsoft OAuth.
Follow the maintained setup guide for your chosen AI client and its documented authentication path.
Start with a read-only inbox query, then approve only the mailbox changes you intend to make.
Why it matters
A little less switching.
Bring relevant Outlook context into planning without copying an entire mailbox into a prompt.
Turn reviewed message details into a new outbound email when a threaded reply is not required.
Keep folder, read-state, and trash changes inside explicit mail-write and approval boundaries.
- Microsoft OAuth sign-in, not your Microsoft password
- Bounded message bodies and permission-scoped mail reads
- Mailbox writes follow Pear permissions and the active policy
A few good questions
Before you connect.
Can Pear read Outlook email bodies?
Yes. Pear can read an Outlook message body in bounded segments and continue from the returned offset when more content remains. Listing and searching mail can stay at metadata level until a body read is needed.
Can Pear reply inside an existing Outlook thread?
No threaded-reply claim is made here. Pear can send a new message, but it does not currently promise an in-thread reply, a saved item in Outlook Drafts, sender-alias selection, or attachment sending.
Can Pear organize an Outlook mailbox?
Pear can move messages, change read state, and move messages to trash when the active permissions and write policy allow it. It does not manage Outlook mailbox rules; Pear’s separate workflow rules do not mutate provider mailbox rules.
Outlook Mail MCP
Ready to connect your apps?
Pear uses Microsoft OAuth to expose bounded Outlook Mail reads and a focused set of mailbox writes. A configured client can send a new message, move mail, change read state, or move a message to trash when its permissions and active write policy allow the action.