time-messenger-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TIME_URL | Yes | URL вашего экземпляра Time Messenger | |
| TIME_TOKEN | No | Personal Access Token (рекомендуется) | |
| TIME_LOGIN_ID | No | Email или логин | |
| TIME_PASSWORD | No | Пароль |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| login_with_mfaA | Login to Time Messenger with MFA code. Use this when regular login requires MFA verification. Enter the 6-digit code from your authenticator app. |
| send_messageA | Send a message to a channel or reply in a thread |
| get_channel_messagesB | Get messages from a channel with pagination |
| get_thread_messagesB | Get all messages in a thread |
| search_messagesB | Search messages in a team |
| list_threadsB | List all threads that the user is following in a team |
| get_thread_statsB | Get unread threads count and mentions for a team |
| get_threadC | Get information about a specific thread |
| follow_threadA | Start following a thread to receive notifications |
| unfollow_threadB | Stop following a thread |
| mark_thread_readB | Mark a thread as read up to a specific timestamp |
| list_channelsA | List all channels for the user in a team |
| get_channelC | Get information about a specific channel |
| search_channelsA | Search channels in a team by name |
| get_channel_unreadA | Get unread message count and mentions for a channel |
| list_teamsA | List all teams for the current user |
| get_teamC | Get information about a specific team |
| get_teams_unreadA | Get unread message counts for all teams |
| get_team_unreadA | Get unread message count for a specific team |
| get_meB | Get information about the current user |
| get_userB | Get information about a specific user |
| search_usersA | Search users by username, email, or name |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 22 tools
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.
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.
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.
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.