Commonpost MCP for Thunderbird
Related Servers
Alternatives to Commonpost MCP for Thunderbird
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceProvides AI assistants with full access to Thunderbird email, compose, filters, calendar, and contacts via the Model Context Protocol.1MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to access Thunderbird email, contacts, and calendars through the Model Context Protocol, with tools for searching, reading, composing, and managing messages.3MIT
- AlicenseNot gradedqualityDmaintenanceProvides a Model Context Protocol interface for Mozilla Thunderbird, allowing AI assistants to manage emails, filters, calendars, and contacts. It exposes 24 tools for tasks like searching messages, drafting replies, and organizing folders through a local bridge.MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to work directly with a local Thunderbird client, providing roughly 40 tools to search and read mail, compose, reply and forward messages, manage folders, filters, contacts, calendars, events and tasks. Write operations open a review window by default, so nothing is sent or created without the user's confirmation.1MIT
- AlicenseAqualityBmaintenanceEnables AI agents to control Thunderbird directly, including mail, folders, contacts, calendar, filters, and settings, through its own internals.6625MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to search and page through local Thunderbird mbox mail, read message bodies and attachments with SHA-256 verification, open native compose windows, create native drafts, and send explicitly authorized email through existing Thunderbird identities over MCP stdio. Queries stay read-only and never modify the mbox, while account authentication and real delivery remain with Thunderbird.MIT
TDQS
Scored across 41 tools
Tools are grouped by clear resources (accounts, folders, messages, contacts, events, tasks, filters) and the descriptions explicitly disambiguate the risky pairs: getMessage vs getMessages vs getRecentMessages vs searchMessages vs displayMessage, deleteMessages vs emptyTrash vs emptyJunk, and event vs task deletions (which even refuse the wrong id type). A few boundaries remain thin — sendMail vs saveDraft vs replyToMessage/forwardMessage all compose mail with overlapping mode semantics, and updateMessage bundles flags plus move/trash — but overall an agent can pick correctly.
Nearly every tool follows a camelCase verb_noun pattern (listFolders, searchMessages, createEvent, updateFilter, reorderFilters, getAccountAccess), applied uniformly across all five domains. The only deviations (replyToMessage, forwardMessage) still read as verb+object and fit the same style.
41 tools is heavy, but the server spans mail, folders, contacts, calendar events, tasks, filters and account access, so each domain carries only ~6-8 tools. Still, there are several parallel read paths (getMessage, getMessages, getRecentMessages, searchMessages, displayMessage) and a bulky filter-confirmation surface that push it past a comfortably scannable set.
Coverage is broad and lifecycle-complete in most domains: message read/move/tag/delete/empty, folder create/rename/move/delete, contact CRUD, event and task CRUD, and full filter management including reorder and manual run. Gaps remain minor but real: no tool to list address books (only addressBookId surfaced via searchContacts), no way to create/rename calendar categories, and getMessage references a saveAttachments tool that is not present in the surface.