io.github.0xka13b/microsoft-outlook-mcp
NPM · MICROSOFT-OUTLOOK-MCP · SCANNED AUG 3
Microsoft Outlook (mail) MCP server — read, search, and send email through Microsoft Graph.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score →
Supply Chain Security87
- No malware found by supply-chain analysis.Pass
- Only part of the dependency tree could be resolved (110 of 111), so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Only part of the dependency tree could be resolved (110 of 111), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 55 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability77
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 992 tokens (~70/item across 14 items; 14 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · microsoft-outlook-mcp
claude mcp add 0xka13b-microsoft-outlook-mcp -- npx -y microsoft-outlook-mcp
codex mcp add 0xka13b-microsoft-outlook-mcp -- npx -y microsoft-outlook-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"0xka13b-microsoft-outlook-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"microsoft-outlook-mcp"
],
"enabled": true
}
}
} openclaw mcp add 0xka13b-microsoft-outlook-mcp --command npx --arg -y --arg microsoft-outlook-mcp
mcp_servers:
0xka13b-microsoft-outlook-mcp:
command: "npx"
args: ["-y", "microsoft-outlook-mcp"] {
"mcpServers": {
"0xka13b-microsoft-outlook-mcp": {
"command": "npx",
"args": [
"-y",
"microsoft-outlook-mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Aug 26 +4
- Stability: unverified → 0.27 ▲ functional
- 2 Aug 26 +40
- Provenance: unverified → fail ▼ security
- Install scripts: unverified → pass ▲ security
- Known CVEs: unverified → partial ▲ security
- Malware scan: unverified → pass ▲ security
- Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
- Capabilities: pass → unverified ▼ functional
- Schema quality: unverified → excellent ▲ functional
- License: unverified → pass ▲ functional
- Dependency health: unverified → partial ▲ functional
- Maintenance: unverified → pass ▲ functional
- Licence: MIT functional
- 1 Aug 26 +5
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- MCP protocol: unverified → pass ▲ functional
- 31 Jul 26 −7
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 −18
- Malware scan: pass → unverified ▼ security
- 27 Jul 26 46
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 3 Aug 2026 · Analysed npm/[email protected]
Provenance none
Ecosystem: npm · Outcome: none
Dependencies 110 packages
110 packages in the resolved dependency tree · 110 deprecated · 39 stale.
The dependency tree was only partially resolved, so these counts may be incomplete.
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.
create_email_draft ~123
Create a new, standalone draft email that can be edited and sent later. Use this only for starting a fresh message — to draft a reply within an existing conversation thread, use create_reply_draft instead.
| Name | Type | Req | Description |
|---|---|---|---|
| attachments | array | — | File attachments |
| bcc | array | — | BCC recipients |
| body | string | yes | Email body |
| body_type | string | — | Body content type. Defaults to text. |
| cc | array | — | CC recipients |
| subject | string | yes | Email subject |
| to | array | yes | Recipient email addresses |
No output schema declared.
No examples provided.
create_reply_draft ~155
Draft a reply to an existing email, kept inside the original conversation thread. Produces an editable draft (in Drafts) that inherits the conversation, the 'RE:' subject, threading headers, and quoted history — review and send it later with send_email or via Outlook. Use this instead of create_email_draft whenever responding to a message.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | Your reply text, inserted above the quoted original message |
| cc | array | — | Additional CC recipients to add to the reply |
| email_id | string | yes | Message ID being replied to |
| reply_all | boolean | — | Reply to all recipients of the original (sender + to + cc) instead of just the sender. Defaults to false. |
No output schema declared.
No examples provided.
delete_email ~27
Permanently delete an email message.
| Name | Type | Req | Description |
|---|---|---|---|
| email_id | string | yes | Message ID to delete |
No output schema declared.
No examples provided.
get_attachment ~43
Get an email attachment's content (returned as base64 in contentBytes).
| Name | Type | Req | Description |
|---|---|---|---|
| attachment_id | string | yes | Attachment ID |
| email_id | string | yes | Message ID |
No output schema declared.
No examples provided.
get_email ~84
Get a single email message by ID with full body and headers.
| Name | Type | Req | Description |
|---|---|---|---|
| body_max_length | integer | — | Max characters of body content to return. Defaults to 50000. |
| email_id | string | yes | Message ID |
| include_attachments | boolean | — | Include attachment metadata. Defaults to true. |
| include_body | boolean | — | Include message body. Defaults to true. |
No output schema declared.
No examples provided.
list_emails ~86
List emails from a mailbox folder ordered by date descending.
| Name | Type | Req | Description |
|---|---|---|---|
| folder | string | — | Folder name: inbox, sent, drafts, deleted, junk, archive, or a folder ID. Defaults to inbox. |
| include_body | boolean | — | Include message body. Defaults to true. |
| limit | integer | — | Number of messages to return (1–100). Defaults to 10. |
No output schema declared.
No examples provided.
me ~21
Get the signed-in user's profile (id, displayName, mail).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
move_email ~56
Move an email to a different folder.
| Name | Type | Req | Description |
|---|---|---|---|
| destination_folder | string | yes | Destination folder name (inbox, sent, drafts, deleted, junk, archive) or folder ID |
| email_id | string | yes | Message ID to move |
No output schema declared.
No examples provided.
reply_all_email ~55
Reply to all recipients of an email.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | Reply body |
| body_type | string | — | Body content type. Defaults to text. |
| email_id | string | yes | Message ID to reply-all to |
No output schema declared.
No examples provided.
reply_to_email ~54
Reply to an email (sender only).
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | Reply body |
| body_type | string | — | Body content type. Defaults to text. |
| email_id | string | yes | Message ID to reply to |
No output schema declared.
No examples provided.
search_emails ~70
Search emails by keyword across all folders or within a specific folder (KQL syntax supported).
| Name | Type | Req | Description |
|---|---|---|---|
| folder | string | — | Limit search to this folder (inbox, sent, etc.) |
| limit | integer | — | Max results. Defaults to 50. |
| query | string | yes | Search query string |
No output schema declared.
No examples provided.
send_email ~85
Send an email immediately.
| Name | Type | Req | Description |
|---|---|---|---|
| attachments | array | — | File attachments |
| bcc | array | — | BCC recipients |
| body | string | yes | Email body |
| body_type | string | — | Body content type. Defaults to text. |
| cc | array | — | CC recipients |
| subject | string | yes | Email subject |
| to | array | yes | Recipient email addresses |
No output schema declared.
No examples provided.
unified_search ~75
Search across multiple Microsoft 365 content types (email, calendar events, files) in one query.
| Name | Type | Req | Description |
|---|---|---|---|
| entity_types | array | — | Entity types to search. Defaults to [message, event, driveItem]. |
| limit | integer | — | Max total results. Defaults to 50. |
| query | string | yes | Search query string |
No output schema declared.
No examples provided.
update_email ~58
Update email properties such as read status, categories, or flag.
| Name | Type | Req | Description |
|---|---|---|---|
| email_id | string | yes | Message ID to update |
| updates | object | yes | Properties to update, e.g. {"isRead": true, "categories": ["work"]} |
No output schema declared.
No examples provided.