F
licenseA
qualityD
maintenanceMCP server for Mattermost that enables AI assistants to read posts, search messages, send messages, and manage channels.
9
-
time-messenger-mcp-server
by BarredEwe
Related Servers
Alternatives to time-messenger-mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityFmaintenanceAn MCP server for MAX Messenger (Russia's national messenger by VK) that enables AI clients to send and read messages, manage chats and members, send media, and more through 21 tools.21567-
- FlicenseNot gradedqualityBmaintenanceMCP server for the eXpress corporate messenger, enabling AI agents to list chats, search contacts, send messages, and wait for incoming messages with end-to-end encryption.51-
- AlicenseAqualityAmaintenanceAn MCP server that allows AI assistants to send formatted text, files, and updates to Telegram topics, and to capture incoming messages from work chats into a local inbox for retrieval.10AGPL 3.0
- AlicenseNot gradedqualityBmaintenanceMCP server for Microsoft Teams that lets AI assistants search, message, and manage chats, meetings, files, and contacts using your existing Teams browser login—no app approval or Azure AD registration needed.371MIT
- FlicenseNot gradedqualityCmaintenanceMCP server that connects AI assistants to T-Bank Education, enabling access to courses, timetable, deadlines, and user profile via tools like get_timetable, get_my_courses, and get_deadlines.-
TDQS
A3.5/5.0
Scored across 22 tools
Disambiguation5/5
Each tool has a unique target resource and action (send, get, search, list, follow/unfollow, mark). The getters are clearly differentiated by resource type (channel messages, thread messages, thread info, channel info, team info, user info, unread counts). No two tools appear to perform the same operation.
Naming Consistency5/5
Tool names follow a consistent verb_noun pattern with underscores, using verbs like get, list, search, send, follow, unfollow, mark, and login. The choice of verb is intuitive (list for enumeration, get for specific resources, search for queries). No mixed casing or inconsistent styles.
Tool Count4/5
22 tools is slightly above the typical 3-15 range but is justified by the breadth of messaging domain (teams, channels, threads, users, messages, unread counts). Each tool addresses a distinct part of the workflow, so the count is appropriate for a comprehensive messaging integration.
Completeness3/5
The tool set covers reading/searching messages, sending messages, managing thread subscriptions, and checking unread counts. However, it lacks update/delete operations for messages and create/delete operations for channels/teams, which are notable gaps for a full lifecycle. Agents can work around this but may hit dead ends when needing to modify resources.
Maintenance
ActivityMaintained
ResponsivenessNo issues