Skip to content
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.
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
Hosted Outlook Mail
outlook://connected

Find the right message, read a bounded body, and act with approval.

Ask your assistant

List unread Outlook mail from this week that mentions the Atlas project.

1

List Outlook mail folders and message metadata, then search for the messages relevant to a task.

2

Read message bodies in bounded segments rather than returning an unbounded mailbox payload.

3

Send a new Outlook message after the exact recipients, subject, and body enter Pear’s approval flow.

What Pear unlocks

Move from inbox context to a deliberate next action.

01

List Outlook mail folders and message metadata, then search for the messages relevant to a task.

02

Read message bodies in bounded segments rather than returning an unbounded mailbox payload.

03

Send a new Outlook message after the exact recipients, subject, and body enter Pear’s approval flow.

04

Move messages between folders, mark them read or unread, or move them to trash with mail-write access.

05

Use Microsoft OAuth; Pear does not ask for or store your Microsoft password.

06

Connect through one hosted endpoint, then follow the maintained setup path for your AI client.

Try first

Prompts that prove the connection is working.

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.
Why it matters

Pear turns one-off chats into finished provider workflows.

The connection carries context into action, while you remain in control of what gets changed.
Outcome 01

Bring relevant Outlook context into planning without copying an entire mailbox into a prompt.

Outcome 02

Turn reviewed message details into a new outbound email when a threaded reply is not required.

Outcome 03

Keep folder, read-state, and trash changes inside explicit mail-write and approval boundaries.

FAQ

Answers for agents and search results.

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

Give your assistant a real action layer.

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.