README.md — Mail and Files Connector

# Mail and Files Connector

Version 0.1.0 is a free MIT-licensed Agent Skill containing a Python standard-library stdio server. It exposes seven read-only mail and file tools through Microsoft Graph. It works with Model Context Protocol clients that launch a local command.

See [SETUP.md](SETUP.md) to configure application credentials, [SKILL.md](SKILL.md) for agent use, and [references/protocol.md](references/protocol.md) for protocol and data limits. The full Skills Outpost package includes the server, synthetic tests, and license. No message send, event creation, file upload, or delete tool is present.

Microsoft 365, SharePoint and Microsoft Graph are Microsoft trademarks. This independent product is not affiliated with or endorsed by Microsoft.

The server reads the complete Graph JSON response (at most 2,000,000 bytes) before applying item and body output limits; a 50-item or body limit does not restrict upstream reads. No additional pages are fetched. Stdin is read as bytes, with a 1,000,000-byte line limit including its newline; larger lines receive a clear error and are drained in bounded byte chunks. Strict UTF-8 decoding occurs per request: undecodable lines receive JSON-RPC -32700 and serving continues. JSON output escapes non-ASCII characters so stdout works in UTF-8 and C locales. Test fixtures are read once with a 2,000,000-byte limit; malformed JSON, fixture entries, collection items, pagination metadata and message bodies are rejected explicitly.

login.microsoftonline.com receives the tenant identifier in the token URL and the client ID, client secret, scope and grant type in the request body. graph.microsoft.com receives the bearer token, configured mailbox/site/drive identifiers, search phrases, conversation/message/item IDs and relative folder names. A drive ID returned by the site lookup is sent back to Graph for subsequent requests. Redirects can send their provider-returned URL paths and queries to Graph or a single-label SharePoint host; bearer authorization is not forwarded on redirects. The operating system resolver receives destination hostnames, including hostnames from provider redirects; a configured proxy may resolve them instead. Returned data goes to the local stdio client and may be forwarded by that client.

Configured and fetched identifiers and relative folders reject traversal, encoded forms and backslashes before use in paths. Search phrases are quoted as data, so literal percent signs are accepted. Destination URLs reject raw dot segments and backslashes. The configured test fixture is the only local data file read; there is no configured local root or history store.

By Zero Width Lab (zerowidthlab.com)

License: MIT (read it).

Back to the listing