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 |
| add_reactionB | Add an emoji reaction to a message. Accepts an emoji name ("+1", ":tada:") or a common emoji character ("👍") |
| remove_reactionB | Remove your own emoji reaction from a message |
| get_reactionsA | List all emoji reactions on a message |
| 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 |
| mark_channels_readA | Mark all available channels or selected channel IDs as read; this action cannot be undone. The all mode includes public, private, DM, and group channels. Followed threads are excluded; use mark_thread_read for threads. |
| list_channel_categoriesB | List the user's channel sidebar categories for a team, in sidebar order, with their channels. |
| create_channel_categoryC | Create an empty custom channel sidebar category. |
| update_channel_categoryA | Update metadata of a channel sidebar category. Provide at least one of display_name, sorting, muted, collapsed. Only custom categories can be renamed; managed categories cannot be changed. |
| delete_channel_categoryA | Delete a custom channel sidebar category. Its channels return to the default categories. |
| reorder_channel_categoriesB | Set the sidebar order of channel categories. category_ids must list every category of the team exactly once. |
| move_channel_to_categoryB | Move one channel into an existing custom, Channels or Favorites sidebar category. |
| set_channel_favoriteA | Favorite or unfavorite one channel. Unfavoriting returns a channel to Channels, or a direct/group message to Direct Messages. |
| 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 33 tools
Most tools map cleanly to a distinct resource and action, and the descriptions help separate similar operations. The unread/stats cluster (get_teams_unread, get_team_unread, get_thread_stats, get_channel_unread) is closely named and could cause hesitation, but the tools remain functionally separable.
The set uses snake_case with a mostly predictable verb_noun pattern throughout. Minor deviations such as get_me and login_with_mfa, plus the singular/plural split between get_team_unread and get_teams_unread, keep it from being fully consistent.
At 33 tools, the server is well above the borderline 16-25 range and feels heavy for a messenger interface. The breadth of subdomains explains some of the count, but the set still contains enough tools that it should likely be scoped down or more tightly grouped.
Coverage is broad across auth, users, teams, channels, messages, threads, reactions, and sidebar categories. However, core lifecycle operations such as creating/updating/deleting channels and editing/deleting messages are missing, which are notable gaps for a messenger server.