Skill Detail

Read Microsoft 365 attachments with explicit extraction coverage

Hand a selected Microsoft 365 attachment to an approved processor through a fresh download URL, preserving continuation and extraction-coverage evidence.

Data Extraction & TransformationMCP
Data Extraction & Transformation MCP Published
⭐ 1.1k GitHub stars ⬇ 107.8k/wk npm
COPY SKILL INSTRUCTIONS (OPTIONAL)
npx skills add agentskillexchange/skills --skill read-microsoft-365-attachments-explicit-extraction-coverage Copy
Uses the third-party skills CLI, not an ASE-owned installer. Check your agent’s compatibility. This copies instructions; complete the upstream tool setup below separately.
At a glance
Tools required
Node.js 20+; MCP client; authorized M365 HTTP deployment with attachment URLs; explicitly approved compatible document processor; scoped attachment access
Install & setup
The exact project publishes @softeria/ms-365-mcp-server; observed npm latest was 0.184.2. For the pinned guide contract, use a reviewed source build at 385e4c85ffa9f94d9ce04ce574741e1c2f9016e4 and the upstream npm ci / npm run build setup. Configure authorized Microsoft access and its documented HTTP mode with –read-only and –enable-attachment-urls. Filter tools, review –list-permissions and verify list-mail-attachments/get-download-url availability. Separately configure a processor authorized to receive the document. Package-to-development-feature equivalence and runtime behavior were not tested.
Author
Softeria
Publisher
Organization
Last updated
Nov 13, 2026
Quick brief

Invoke this MCP workflow when an agent must answer a bounded question from a Microsoft 365 attachment using an external document processor. The operator specifies the message, attachment, account and relevant content scope. Return extracted evidence, source identity, processor-native completion and coverage fields, warnings and gaps. This makes partial reading accountable when ordinary attachment browsing would conceal omitted content.

How it works

What this skill actually does

The upstream guide specifies list-mail-attachments with id, name, contentType, size and isInline selected, then get-download-url for the chosen attachment’s $value route. Attachment URLs require appropriately configured HTTP mode with --enable-attachment-urls and necessary mail permissions. Give the temporary URL only to an explicitly approved processor that accepts it; Microsoft credentials remain with the integration. Inspect the processor’s real tool schema instead of assuming a universal converter API.

Server-minted URLs are single-use. Mint a fresh ticket for each probe, conversion, continuation or retry, preserving source and account. Pass exact returned continuation values unchanged and retain the complete native result envelope. Exhausted output does not establish full source coverage, especially with page selections, source truncation or OCR omissions. Multi-GET processors need a compatible fresh-ticket strategy.

The scope boundary is one authorized attachment read and evidence handoff. Exclude message classification, moving or sending mail and tenant administration. MCP is central to invocation. The guide is pinned to a development snapshot; verify deployed tool and permission behavior. No converter is supplied, and PDF/OCR fidelity is not guaranteed.