Skolemelding MCP
Related Servers
Alternatives to Skolemelding MCP
No user-submitted related servers found.
Related Servers
- FlicenseAqualityDmaintenanceA lightweight MCP server for personal Microsoft Outlook/Hotmail accounts, enabling email search, reading, attachment management, and folder operations via Microsoft Graph API with OAuth device-code flow.61-
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients to interact with Proton Mail through a self-hosted server that works alongside Proton Mail Bridge. It provides read-only mailbox tools such as listing folders, searching mail, and retrieving messages while keeping Bridge isolated from the network.MIT
- AlicenseNot gradedqualityBmaintenanceMCP server that exposes a Microsoft 365 mailbox via the Model Context Protocol, enabling AI assistants to search, read, and download emails and attachments, and optionally send mail.9 npmMIT
- AlicenseAqualityDmaintenanceDeprecated MCP server wrapper for ms365-email-cli that exposes Microsoft 365 email operations (list, read, send, reply, search, etc.) as MCP tools. Use the main ms365-email-cli package instead, which now includes built-in MCP server support.1018 npmISC
- AlicenseNot gradedqualityCmaintenanceA local, read-only MCP server that lets an AI agent search and read Proton Mail and Proton Drive, connecting to Mail through Proton Mail Bridge over IMAP and to Drive through the desktop app's synced folder. It exposes tools for listing folders, searching messages, reading mail bodies and attachments, and browsing or reading files from Drive, without ever writing, sending, or changing anything.MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that reads, searches, organizes, and deletes Proton Mail through the local Proton Mail Bridge, with read-only mode and sender authentication checks. It cannot send mail.83 npmMIT
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: list_messages returns previews, get_message returns full text and attachment metadata, and get_attachment returns raw bytes. The boundaries between reading a message and fetching its attachment are clear and unlikely to be confused.
All three tools follow a consistent verb_noun snake_case pattern: list_messages, get_message, get_attachment. The naming is predictable and easy to parse.
Three tools is a reasonable minimum for a read-only message client, and each earns its place. However, it is on the low end, and a slightly larger surface for common read workflows could be expected.
The surface covers listing, reading, and downloading attachments, but it lacks any operation to mark messages as read, send/reply, or delete. For a messaging domain, these are notable missing operations that create dead ends for common workflows.