Microsoft 365
com.proscendiaPublished by proscendia.comOfficial publisherv1.0.0Updated Oct 24, 2026
Permissioned access to Outlook, OneDrive and Teams via the user's own Microsoft account
The publisher's own server: Google Workspace
Overview
Gives an assistant permissioned access to the user's own Microsoft 365 Outlook, OneDrive and Teams data.
- What you can do
- This remote MCP server connects an assistant to Microsoft 365 services through the user's own Microsoft account. According to the registry description, it covers Outlook, OneDrive and Teams, so an assistant can work with mail, files and team content under the permissions the user grants. The manifest does not list individual tools, so the exact operations available are not documented here.
- When to use it
- Worth adding when you want an assistant to work with your own Microsoft 365 mail, files and Teams content rather than generic web data. It suits users who already rely on Outlook, OneDrive and Teams and are comfortable granting an OAuth app access to that account.
- Requirements
- A remote streamable HTTP endpoint at OAuth authentication is required, so a Microsoft account and a consent step are needed. No environment variables, headers or local packages are declared.
Installation
In SourceWeft
- Open Microsoft 365 in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/com.proscendia%2Fmicrosoft-365/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"microsoft-365": {
"type": "http",
"url": "https://microsoft-mcp.proscendia.com/mcp"
}
}
}Tools
0Version history
1- v1.0.0LatestSep 16, 2026
Score
67% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.