Skip to main content
Glama
Sign In
Infomaniak

kChat MCP Server

by Infomaniak
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to kChat MCP Server

No user-submitted related servers found.

    Related Servers

    • Slack MCP Server

      lbeatu
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables interaction with Slack workspaces through comprehensive integration capabilities. Supports channel management, messaging, thread replies, reactions, and message history retrieval through natural language commands.
      62 npm
      MIT

    • Slack User MCP Server

      lars-hagen
      A
      license
      A
      quality
      D
      maintenance
      Enables interaction with Slack workspaces as a user, supporting channel listing, message posting, threading, reactions, and user management via the Slack API.
      8
      11
      MIT

    • Slack MCP Server

      ampcome-mcps
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to interact with Slack workspaces through natural language, supporting channel management, message operations, user profiles, reactions, and threaded conversations.
      -

    • slack-mcp-server

      dudztroyer
      A
      license
      A
      quality
      C
      maintenance
      Enables AI assistants to interact with Slack workspaces, including listing channels, posting messages, replying to threads, adding reactions, and retrieving user information.
      10
      18 npm
      MIT

    • Slack MCP Server

      bcharleson
      A
      license
      A
      quality
      D
      maintenance
      Enables AI assistants to interact with Slack workspaces through comprehensive channel management, messaging, direct messages, search functionality, and user management capabilities.
      30
      8 npm
      2
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.4/5.0

    Scored across 9 tools

    Disambiguation4/5

    Most tools map to distinct resource+action pairs (channels, history, threads, reactions, users). The closest overlaps are post_message vs reply_to_thread vs send_direct_message, and get_users vs get_user_profile, but the descriptions make the distinctions clear enough to select correctly.

    Naming Consistency5/5

    Every tool follows the exact same kchat_ + verb_noun pattern (kchat_list_channels, kchat_post_message, kchat_get_user_profile). Prefixing with the service name is uniform and predictable across all nine tools.

    Tool Count5/5

    Nine tools is well within the sweet spot for a chat/messaging server. Each tool earns its place by covering a distinct messaging primitive (channels, messages, threads, reactions, users, DMs).

    Completeness4/5

    The surface covers the core chat lifecycle: list channels, read history, post, reply, react, DM, and inspect users. Minor gaps remain—no edit/delete message, no remove reaction, no search, and no way to list existing DM conversations—but agents can work around these for most workflows.

    Maintenance

    ActivityActive
    ResponsivenessUnresponsive

    Resources